Homey stability issues since 9-1-2024 probably caused by HomeyScript app
Opened this issue · 6 comments
Since a few days (since 9-1-2024 13:00 to be exact) my HomeyPro 2023 runs very unstable. I think Homey was updated to version 10.2.1. After some research I think it is HomeyScript being unstable and crashing with a high frequency causing a lot of smart scenarios not to work. Remarkable is the CPU usage since that time. Although the CPU% might not seem high with around 4% on averga, but it used to be way below 1%. No new scripts were deployed.
I hope you can supply a solution to that.
As I own 3 HomeyPro's (1x 2019, 2x 2023) I also checked HomeyScript app on them. I see no changing pattern on the HP2019, but I do see the exact same change on my other HomeyPro 2023 (also version 10.2.1). This can't be a coincidence...
@jeroenwienk Is there any update for this issue already?
To further investigate the problem, I wrote a flow that runs every 1 minute and executes a very simple script ("return true;") through a HomeyScript Run Script flow card. If it errors (red line) it will 1. check if HomeyScript is enabled (and re-enable if not) and restart the HomeyScript app. Also it sends me a notification. See below screenshot.
The HomeyScript app turns out to have crashed every 10-20 mins. See below notifications:
Now the problems (there are many, including the HomeyScript app) could also be caused be some Homey core update included in version 10.2.1 as deployed on 9-1-2024, and not by HomeyScript specifically. The RAM and CPU usage of many apps increased dramatically from that moment. In below screenshots from Homey Insights you can see that the pattern of RAM and/or CPU usage changed exactly from that point.
Now the problems (there are many, including the HomeyScript app) could also be caused be some Homey core update included in version 10.2.1 as deployed on 9-1-2024, and not by HomeyScript specifically. The RAM and CPU usage of many apps increased dramatically from that moment. In below screenshots from Homey Insights you can see that the pattern of RAM and/or CPU usage changed exactly from that point.
Is this still an issue?
@jeroenwienk Yes, this is absolutely still an issue!