You are welcome, I will release it for the public tomorrow so nothing unexpected will happen. So switch over to the official sharp version sometime tomorrow 
Great effort here @Windy - really appreciate the possibility to get the Arlo devices into Homey - pretty much the last piece of the smart home puzzle here!
I just miss one little thing - in the conditions to execute, if you could add location mode? As in “WHEN , AND mode is/isn’t THEN ” - if that’s possible - and if so, I guess it could also be a trigger - location mode changed?
Thanks! That makes perfect sense, and it fits nicely with the location mode support already in the app.
A new Arlo Connect version is currently waiting for Homey approval. Once that version has been approved and released, I’ll include this in the following update:
- a condition for checking whether the Arlo location is in Standby / Arm Home / Arm Away
- a trigger for when the location mode changes
Great suggestion — thanks for the feedback!
Mikael
@Windy Thanks for the updates. The app has become a lot more stable after recent updates. Im currently on 1.0.35 and have not needed to restart the app since this update.
Thanks, that’s great to hear!
I’m glad 1.0.35 has been much more stable for you and that you haven’t needed to restart the app.
I’m continuing to monitor the diagnostics and have already prepared one small additional stability fix for the next test version.
Thanks again for testing and reporting back — it really helps.
Hi, today the app was not working again. Camera stream and trying to access the app settings times out. Report: 8e0c6d2d-e5fb-4994-b296-2f61cca5ed13
Restarting the app after sending the report fixes the issue.
Hi!
Thanks for your feedback! Press diagnostics in the app. This way I get the log and will see what happened and will try to solve it.
Thanks!
lör 12 sep. 2026 kl. 08:25 skrev cscheiene <notifications@athom.discoursemail.com>:
The app stopped working again yesterday. I have left it over night to see if it could recover itself. Its still not working. I have not restarted it yet, but I guess that will get it working again.
Diagnostics report:
b9df983e-1d16-4bd2-a0e5-cce49920a7d7
Thanks — I saw the diagnostics report and replied to it directly as well.
It showed the app getting stuck on repeated expired-token/session failures instead of fully recovering. I’ve already changed the recovery logic for the next test version so those failures can trigger a full session rebuild automatically.
Until that version is available, restarting the app should get it working again.
sön 13 sep. 2026 kl. 08:47 skrev cscheiene <notifications@athom.discoursemail.com>:
