Offline is reported from the cloud itself, so when Homey is not even connected to internet, it will be reported as offline.
Get the IP of Homey (you shall have two, one for Wifi and one of Ethernet) and keep pinging those… if you will lose the ping, it means that not only Cloud connection is gone but also local connectivity. Which is very strange, considering Homey is still operational. You can maybe also setup local access to Homey to exclude any cloud part, in case the ping will be still responding.
No idea, it shall be either all or none, not only partiall… that could be indicating also some other, possibly HW related problem.
Well, you can create flows with triggers and write it to the Timeline = so even after restart, you shall see the events. You can even automate the restarts, eg. :
Based on those triggers, you can eg. force Homey to restart (eg. having controlled restart vs cold-uncrontrolled reboot)…
Or you can simply check the device timeline, it will be written there without any triggers…
eg.
Also since you have now added sysinternal devices, track-share the insights after restart or when you will loose connectivity…eg. check for temperature, free ram etc.
First I want to say thanks for giving your valued input!!
I removed 2 or 3 unused apps 2-3 days ago and since then…no more offline messages, no more unreachable Homey.
I think it has something to do with used memory, system overload… A general problem of the HP2023 when using several apps and flows.
Are you sure? I think you do… But my experience is that whenever I get this message, my Homey can’t be reached by the Homey app and my Homey disappeared from my router.
Good idea of pinging the IP addresses.
To my opinion local connectivity is gone or at least not fully functional nor reliable.
I do have local connection (secure) turned on, but I’m not sure if that’s what you mean. Tell me how to do ao, “to excluse any cloud part”.
Exactly! That’s why I’m not sure whether Homey is still running.
I’ll read the part of flows or writing to the timeline, based on sysinternals. It’ll be of great help.
Conditional restarting the Homey, in case of critical circumstances off the memory, etc. Sounds good.
So it might be just your Homey running out of the free memory. Based on my experience, “stable” minimum is about 250MB with 4GB configuration (you have 2GB standard setup), if you were below that, Homey might behave unpredictable. Sysinternals and insights of free memory might tell you more then. Check uptime together with minim. free RAM observed.
Appearance or disappearance to unknown (to me) section on your router tells unfortunately nothing, the network connectivity does. Try to ping homey on its IP, assuming you don’t have Dynamic IP assignment. If you do, then first you need to check current IP and then ping it.
I’ve had quite some times Homey seems offline. I just remembered your advise to ping it.
Ethernet: several error messages, see attached picture.
Wireless: only time out.
I made a local user. Homey can’t be reached on its local IP-address.
As I suggested before, Homey closes all of its network connectivity. But why???
Today no flow is functioning in case Homey reports offline.
It happens at least once a day. I’m glad I’m not the only user where this happens.
I don’t really know what you mean with those triggers. In case no flow is functioning on the Homey I won’t get any information. Only when the flows keep on running I will get any info. But the last days flows aren’t doing their things.
It happens in the morning, it happens during the day, in the evening, at random. The WAF is keeps getting down. To be honest, I loved my Homey, but it’s getting lower and lower. Suddenly, apps that used to function without any problems, suddenly crash. I get the feeling it’s hardware related.
What to do: buy a HomeyPro 2026, so memory won’t be any problem. Switching to Home Assistant (learn, create flows, etc.), jailbreak the current HP2023 (has nothing to do with antennas etc).
I installed a new HP2026. Worked fine, no “connection lost” errors. I hoped the memory is the cause of this issue.
Until last night, 03:00. “Homey Pro seems to be offline”. But contrary to previous times, this time I got a “Homey Pro is connected again” message af 03:15. Without restarting it myself.
Why? How?
I’m glad I’m not the only one where this really, really annoying thing happens. But it’s really irritating, frustrating, and so on that we can not find the cause.
I’ll write a mesage at Athom to inform them about this issue. I’m looking for a way to research the size of this problem, how many users are dealing with it.
Just to clarify: has your Homey crashed (red LED ring) or do you get a message that it is offline (Homey’s cloud services cannot connect to your Homey)?
