I have a similar issue as mentioned here. The device (BHT-002 GALW) (i.e. display, buttons, MCU-functionality) - but not the ESP/Fashberg-Firmware itself - sporadically get unresponsive on multiple devices.
Figuring out the issue's source or changing the ESP-Firmware was not yet successful for me (tried the 1.23-beta1 and 1.22 so far).
As I was not able to determine the reason yet, my workaround is to switch off the thermostates power supply with a remote controlled relay, which works, but unfortunately I'm not able to automatically realize, that this is necessary.
The MQTT-state of the devices does not hold the information that there's an issue, but I can see it on the thermostates webpage: when reinitializing the thermostate it says "MCU initialized: No".
So would it be possible to bring an MQTT command to reinitialize the thermostate and show the "MCU Initialized" info somewhere in the state?
I have a similar issue as mentioned here. The device (BHT-002 GALW) (i.e. display, buttons, MCU-functionality) - but not the ESP/Fashberg-Firmware itself - sporadically get unresponsive on multiple devices. Figuring out the issue's source or changing the ESP-Firmware was not yet successful for me (tried the 1.23-beta1 and 1.22 so far). As I was not able to determine the reason yet, my workaround is to switch off the thermostates power supply with a remote controlled relay, which works, but unfortunately I'm not able to automatically realize, that this is necessary. The MQTT-state of the devices does not hold the information that there's an issue, but I can see it on the thermostates webpage: when reinitializing the thermostate it says "MCU initialized: No". So would it be possible to bring an MQTT command to reinitialize the thermostate and show the "MCU Initialized" info somewhere in the state?
BR