Nothing works after latest firmware update 12.11.0

I’m using the Homey Pro 2019 model and it updated automatically to firmware 12.11.0 yesterday morning. Since then I can’t access a single device I’ve installed. If I try to restart any app it shows error code “invalid_state_has_process”, I’ve tried unistalling and installing the apps again and adding the device once more but it can’t find anything and times out. I’ve tried PTP and I have changed the power supply so that should not be an issue.

Am I the only one where this new firmware totally broke my Homey? :sweat_smile:

It seems that the configuration got corrupted. Do you have the backup subscription? In that case, you can factory reset your Homey and restore from a backup afterwards

Sadly I don’t have the backup subsciption. It’s looking like I have to do a factory reset and start adding all devices once again.

You should first contact Athom before performing a reset

Thanks, I just did :+1:

No reset needed now imho, and without a backup (order it now) a reset destroys all of your work.

You can first perform this possible fix:

  • start Homey in recovery mode (turn it up-side-down a minute after power up),
  • per mobile app, go to “Add new Homey”
    (sounds odd, but that’s just the only way to connect to your Homey in recovery mode)
    and follow instructions to connect it to wifi
  • then navigate to “Full software download” and select it →
    This installs the firmware from scratch, and shouldn’t touch your data.

I’ve read about one case of issues after Pro 2016-2019 v12.11.0 update, it killed zigbee.
My preference, as you now might understand, is to install firmware updates myself.

I can recommend the backup subscription by 100%! It’s only €10/y.
It has saved my ass for several times now, either due to VSFU (Very stupid fuck up) or hardware failure.

1 Like

Thanks, I will definitely try this out. Doing a reset is the last resort.

If you perform it exactly as Peter wrote, you will not loose anything, naturally backup is a very good thing to have as safety measure.

Update:

After trying out the recovery mode and reinstalling the update the issue has now been resolved and will not have to perform a reset. Everything is working perfectly now!

Special thanks to @Peter_Kawa for your help :clap: Thank you also to Sharky and Sven!

2 Likes