The app is not crashing, it just stops recieving data - CPU usage also from the app also drops considerable.
The MQTT server and broker seems to work, as I can see the values are still updating when using MQTT explorer. Homey is connected with Ethernet, and Watts keep updating over MQTT and direct to Watts app, so the problem seem to be isolated to Watts app.
It is all values that stop updating in Watts.
The MQTT server and broker is running on Homey (Menno van Grinsven), and Watts it is the only thing I’m using MQTT for.
It stopped 12 days ago, when my Homey Pro recieved a update.
And I can replicate the fault by restarting Homey. My guess is that Watts app is starting before MQTT server and broker has started, and that the app then doesn’t initialise correctly.
If I restart Watts some minutes after rebooting Homey Pro, everything works.
A easy workaround for me would be to make a flow that restarts Watts 1 minutes after Homey has booted.
Kind regards Bo
