This is the (ādiskā)storage overview, this doesnāt impact anything.
The memory overview is shown below this overview, probably called āArbeitsspeicherā in German.
Iāve noticed the same, also, when i restart that app my homey reboots. I think this is since it switched to python but unfortunately I have no time to look into it to make a proper report for Bas.
Well, I disabled the app and have no time to troubleshoot so I wonāt unable the app until I have time. If you can disable it for 24 hours and itās stable and next enable it and reboots start again I definitely advise to report it in the appās topic.
I also had the Homey Pro rebooting constantly last sunday.
i was running the āApple TV & Homepodā app and used the latest versions that Bas switched to python and i looks like switching off this app made Homey stable again.
I will test some more this weekend with his latest version and report to him if indeed it makes Homey reboot constantly again.
Itās only the Python version right? How is the production TypeScript version?
Iām aware that the Python version uses a lot of ram, and 99% of that is just the PyATV library and Python runtime. Not sure if I can improve it any further to be honest, but actively searching for solutions and improvements.
That said, itās an experimental release for a reason, these things can happen. If youāre not comfortable with living on the edge, donāt.
I have a new observation. I think itās tied to automatic updates of the app. I have a similar issue when I run the app during development and asked Athom about it.
Just released 1.6.17, so it could happen again, but maybe another thing that everyone having this issue could try is turning off automatic updates for a while and see how the app runs then.
No one is blaming you here; we were just trying to figure out what might be causing the issue. If I had been 100% sure that it was your app, I would have posted in the relevant thread.
But since others have now reported the same issue, and the problems stopped for everyone once the app was disabled, it must be the appās fault.
Yes, for me itās the Python version.
As I said, no one is blaming you, and I also know that this is a test versionāin other words, Iām aware of the circumstances.