Is this a known bug? Homey app - session expired? Suspicious start screen?

When I open the Homey app on my Android phone (Google Pixel), this message is usually the first thing I see.

A colleague with the newer Homey has the same issue. Reinstalling the Homey app didn’t help.

The only thing that helps is closing the app and restarting it. This has been happening for a few weeks now, ever since the app was updated :frowning:.

App version 9.9.0

I don’t see any error messages in the screenshot. What happens when you click the Homey Pro from the list?

In that case, nothing happens. You have to close the app and restart it before anything responds. After that, the dashboard/device overview will reappear as normal.

When I click “More” in the app and then select Homey Pro under my name, this screen looks the same responds. So I assume a bug or regression here.

It doesn’t make any sense for this menu to appear when you open the app if you only have one Homey. The fact that it doesn’t respond suggests there’s a bug.

Yes, it should only show that on first start when you have multiple Homeys. You should report the issue to Athom:

I submitted it at the end of March and it was confirmed and ticket closed, but there hasn’t been a fix since then :(. That’s why I was hoping for more information.

I’d also be interested to know whether this affects several others as well. At least the people I recommended Homey to, and whom I asked about it, also experience this from time to time. For me, it has recently been happening almost daily.

I’ve been experiencing this for months now… exactly how you’re describing it. Only a force-close and relaunch of the app fixes it.

Very annoying…

App version 10.1.0 and indeed it’s still not fixed.

New recent Homey FW version 13.4 has this in its changelog:

  • Improves stability and performance of fetching system info.

Maybe the mobile app isn’t getting the ‘system info’ correctly or something and this fixes it. Lets hope…

Do the older Homey Pro models just get the updates later for example 13.4? Or are these completely different software versions?

They’re on different branches:
Homey Pro 2016-2019
Homey Pro 2023-2026/Mini

Important features (like the target_power feature for apps) get backported to older models though.

The mobile app changelog is also there.
The current test version (10.1) has a line “Various fixes: Improved reconnect behavior and notifications, plus fixes across Dashboards, search, and device tiles.” But I already was on 10.1 and that didn’t fix it.

I received 13.4 on the Pro this morning… lets see if it did anything.

The problems have persisted for me so far. Today, the update to 13.4.1. Let’s see.

Myeah…

In the meantime… lets check some things. I’m kind of low-key expecting that the app/system is timing out somewhere because of the amount of the devices I have loaded. I’m currently at 69 devices, 8 of them virtual. Also 7 devices that do ‘something’ with the data on the Energy tab.

When opening the Energy tab (in particular, but also when just opening the Home tab), I often notice many of the values/elements are blinking/flickering, like they’re rapidly trying to catch up and/or process old values until they settle on the most recent values. Sometimes the app even hangs during this process and Android throws an “App is not responding” error.

Do you recognize any of this? Do you also have a lot of devices active? Maybe if we can find some correlation we can help find some causation.

New experience, never had this message before. No connection lost.

Overall 49 devices, thereof 8 virtual. I haven’t seen anything flickering or app not responding errors. Only constant alarm messages from Fibaro doorsensor 2.

This is usual (but not normal):
The user authentication expires after two weeks, and if so, Homey needs to check your account online @ Athom Cloud.
Somehow this doesn’t work well sometimes.
I get to see this screen sometimes since 2020 with my Pro 2019 and Pro 2026.

Fix it by just tapping the blue button.

Yes I get it almost every single day, just pressing Try Again fixes it