Homey Pro crashing to red LED ring when making a backup

Do you have a cloud backup subscription?

In any case, there are no logfiles.

Yes, but that would be my last resort as I have been updating and adding flows lately, mainly around the dashboard feature.

There must be some way to debug :frowning:

And does the backups are performed successfully ? You can debug-confirm it with installing sysinternals app and monitor free mem during update.

Workaround is to disable some apps prior to the backup timeframe or restart at midnight, so that there is enough free memory.

2 Likes

The reason I’m asking is because cloud backups are made between 1 and 3AM, which coincides with your crashes.

1 Like

Interesting point, maybe i should disable it and see…

Well well, missing backups match perfectly with the crashes!

Great clue!

I guess it’s time to contact Athom: https://support.homey.app/hc/en-us/articles/360015784034-Submitting-a-support-request

There’s a user on Slack that’s also having crashing issues related to backups: Slack

1 Like

During more one year, Homey Pro 2023 has well worked without any big issues. Since now about 6 months, Homey crashes (cannot access Homey via the mobile App and the ring led is red). In the begining it was only occasionnaly, but since 1 month, it occurs more often.

Analyzing the log, it seems occuring during the night, between 1 am up 5 am. What I discover is that most of time before it occurs, I get log about CPU overload (the sysinternal app is installed and I print a log when CPU AVG 15 min is over 80%). Sometimes I see CPU overload of more than 100% (the max I saw if I’m not wrong was 202%).

This CPU overload seems happen during the automatic online backup process which is activated (each day around 1.15am and 2.15 am a Homey backup is done).
I saw that these last weeks, I got message about the automatic was failed. Today, I run manually the backup after a fail the previous night and Homey crashes (I got a CPU overload into the log too).

Any idea what happen because it was well working before. Please note that I don’t add new devices or flow or homeyscript since about 1 year. Of course Homey firmaware and the App are regulary updated.

In meantime, I’ll try to disable the automatic backup to see if the crash still happen.

Thanks for your help.

The cloud backup might be causing Homey to crash, it’s posted several times now.

I’d recommend to report to homey.app/support

2 Likes

I noticed the same on my homey 2019, however i am not running backups. It looses wifi connectivity now and then, this was with older firmwares not the case. It seems that the homey firmware itself is still running, so i made a workaround by configuring 2 flows and a simple timer, when it cannot ping its router, then it reboots automatically. It then connects again . Also send notifications that it auto reboots. A safeguard is implemented that prevents a bootloop, max 4 restarts per day. Might be an app causing the disconnect, but have not found it.

My Homey Pro crashed/locked up last night, first time this has ever happened and trying to understand why.

Apologies if this has already been answered but a quick search didn’t bring up any recent results. Is there a system log or something I can look at to see whether a specific app/flow/device caused this?

All I have so far is, no updates happened at this time, no backups as they usually run an hour later. Looks to have happened at 01:05am and I have this from the CPU insights. A few individual apps spiked on CPU also, but no more that 10%.

The 300% usage spike is concerning, and I couldn’t get anything from it until I PTP.

Assume this is an isolated incident and nobody else had an issue, or has anyone seen this before?

Let me guess: you have a cloud backup subscription?

Yes, is there an issue I’m unaware of?

Let’s just say that this is at least the third crash issue that I’m reading about that’s probably related to nightly backups (which take place between 1 and 3AM).

Also, let’s just hope that Athom reads this forum… :face_with_peeking_eye:

2 Likes

Odd when no recent updates, unless it’s an issue at their side.

I’ll report it to them.

Cheers

3 Likes

After reading some posts, I disabled the backup and MQTT Hub for some days. No more crashes.
Then I enabled again backup and MQTT Hub but I set the log filter on MQTT Hub to Errors and Warnings. It seems working, no more crashes up now.

I have a Homey Pro 2023, which has crashed twice in the last two weeks with a red ring error. The first time, I unplugged it, and the issue disappeared. However, the same error has occurred again, and I no longer have access to the hub. How can I restart it from the local network? It responds to ping locally on both Wi-Fi and cable. If I restart my local Wi-Fi/network, it reconnects. Does anyone have instructions on how to restart it remotely? It shows as offline in both the Homey app and the developer portal. It looks like the fault appears when it tyres to autobackup like many have pointed out here.

[HowTo] PtP on Homey Pro

So use a WiFi Socket that can be used Remote in a direct App Like fe KASA / TP-Link of Tuya or any other of the many brands providing direct Remote control over Internet.

Or ask a Local person to do it.

Recently mine has again started to crash over the night around the time for the backup. It is most likely, that if the backup runs out of memory the system crashes. If I remove a memory hungry app like the MQTT Hub, then it my Homey is stable for a longer period of time.

I wish there was a supported upgrade path to increase the memory.

@David_Bjaland @OH2TH I would suggest to keep monitoring available free memory and restart Homey after it reaches certain level (it depends on the free mem, total amount of app etc.) so I would not advice on any specific level.

Or - simply start doing preventive restarts on daily basis… this is what I do basically, despite of having 4GB of RAM. On top of that, I know that Athom is aware of those issues and hopefully will find way to improve it.