So I have a flow that reboots Homey once a week (at 04:15 the night between Saturday and Sunday). I have this flow because Homey sometimes is a little buggy such as the 433 MHz system locks up.
However, after this scheduled reboot Homey often loose the 433 MHz, the Zigbee system and flows are missed. This requires a manual reboot to fix.
What can it be that makes Homey so unstable after a flow initiated reboot?
So if I find any apps that are paused, how do I fix that they are not paused after a flow reboot? Should I do a double reboot with a delay in the flow?
If there are apps that are paused then contact the developer to see if anything can be done.
One of my apps asynchronously reconnected to all the devices. At start-up when all the other apps were also loading, it meant my app took up too much CPU time and was therefore paused by Homey. I had to change my app so devices were connected synchronously and that solved the problem.
I not saying that is the case for the apps you are using, but just one possibility.
I do the same, but after a reboot of Homey i also restart a couple of apps synchronously.
For that i use a timer.
30 minutes after the reboot i start with my first app restart and then every 10 minutes after the next.
Perfect! Itâs going to be interesting to see what happens this weekend! Iâll let you know.
I didnât even know about the âRestart appâ or âAn app has crashedâ cards. I did a flow with where I collected all the apps that I have experienced problems with that states When âAn app has chreshedââ>Then âRestart appâ.
I have always rebooted Homey when there has been problems with for example the 433 MHz system. From now on I will try restarting the specific apps insteadâŚif the flow doesnât work that is.