06-22-2022, 10:49 PM
Hello,
When I use the momentary switch of a relay in combination with Mqtt, I am able to make the kincony ethernet "hang".
It seems to occur when the Kincony had to process commands during the momentary switch.
- Note: while I do not receive the state on mqtt, the relay have well-executed the momentary switch
- When a bug occurs:
- the ethernet is completely stuck; no ping, no HTTP server, no mqtt
- HTTP UI for wifi (on another IP is still working)
- Only possible recovery is a Hard reboot (reset of wifi is not working)
My reproduction method:
- Put Relay1 with momentary switch 1 seconds
- send 2 mqtt command:
- `mosquitto_pub -t "relay32/dddd/set` -m "{\"relay1\":1}"
- `sleep 0.5`
- `mosquitto_pub -t "relay32/dddd/set` -m "{\"relay1\":1}"
I also reproduced it with the embedded HTTP page just by insisting when relay state is "wrong".
I tried to update to the latest version (44) but it does not seem to help.
Have you any idea on how to mitigate that?
When I use the momentary switch of a relay in combination with Mqtt, I am able to make the kincony ethernet "hang".
It seems to occur when the Kincony had to process commands during the momentary switch.
- Note: while I do not receive the state on mqtt, the relay have well-executed the momentary switch
- When a bug occurs:
- the ethernet is completely stuck; no ping, no HTTP server, no mqtt
- HTTP UI for wifi (on another IP is still working)
- Only possible recovery is a Hard reboot (reset of wifi is not working)
My reproduction method:
- Put Relay1 with momentary switch 1 seconds
- send 2 mqtt command:
- `mosquitto_pub -t "relay32/dddd/set` -m "{\"relay1\":1}"
- `sleep 0.5`
- `mosquitto_pub -t "relay32/dddd/set` -m "{\"relay1\":1}"
I also reproduced it with the embedded HTTP page just by insisting when relay state is "wrong".
I tried to update to the latest version (44) but it does not seem to help.
Have you any idea on how to mitigate that?