11-19-2024, 04:08 PM
Unfortunately, no such luck. We're still getting intermittent behaviour on both units. Probably still some cleaning on the connectors, but at the moment I'm most concerned about being able to detect that it's gone wrong.
I've been watching the unit happily clicking in and out, and keeping the temperature as it should be after giving it a power off and power on at 8AM today.
Now 15:30ish we're back to the state where I don't seem to be able to recover remotely:
Connecting to ws:<ipaddress>:80 and nothing else on the web front end.
Telnet seems alive however. Is there a way to do a full reset this way? I've tried using debug -> ! to test the software watchdog, but the websocket never seems to recover.
Nothing in the logging in telnet screams "I'm broken" to me, and it appears to be publishing to mqtt fine. According to MQTT it's E-00 OK but according to the virtual console (which works it seems), it's E-07 Comms fault.
Rebooting via the virtual console seems to reboot according to the log via telnet, but doesn't cause the error state to be published by MQTT or reset the comms fault, the only thing that seems to bring it back to life is removing the three pin plug for a while.
This is all on v 3.5.2
After the reboot I did find:
Start Request!
Start denied - no heater data
in the telnet log. But according to the MQTT broker, it's all E-00 OK still.
I've been watching the unit happily clicking in and out, and keeping the temperature as it should be after giving it a power off and power on at 8AM today.
Now 15:30ish we're back to the state where I don't seem to be able to recover remotely:
Connecting to ws:<ipaddress>:80 and nothing else on the web front end.
Telnet seems alive however. Is there a way to do a full reset this way? I've tried using debug -> ! to test the software watchdog, but the websocket never seems to recover.
Nothing in the logging in telnet screams "I'm broken" to me, and it appears to be publishing to mqtt fine. According to MQTT it's E-00 OK but according to the virtual console (which works it seems), it's E-07 Comms fault.
Rebooting via the virtual console seems to reboot according to the log via telnet, but doesn't cause the error state to be published by MQTT or reset the comms fault, the only thing that seems to bring it back to life is removing the three pin plug for a while.
This is all on v 3.5.2
After the reboot I did find:
Start Request!
Start denied - no heater data
in the telnet log. But according to the MQTT broker, it's all E-00 OK still.