Hub is inoperable

Sent it to support, but may be somebody knows better here:
My hub started making troubles yesterday.

Control of some of the devices (esp. locks) would take long time and not always happen.

I couldn’t add some new Z-Wave device that was located about 2m from the hub.

Today, it stopped operating most of the other ZWave devices.

I tried rebooting, repaing zwave network, but it didn’t help.

I noticed that new version was available and upgraded the hub, hoping that it would be better.

ZWave Radio devices table showed empty, even though I had about 20 ZWave devices showing properly in the Devices table.

I tried restoring backups, but they fail to restore.

Now my devices page shows error 500 and the hub is officially unusable.

Any ideas how to completely reset it?
Will I have to reconnect all zwave devices if I restore the backup after it?

Something's up. Second person tonight that has reported missing Z-Wave devices. No, a backup won't do anything for Z-Wave, since the way it works is the devices are stored in the radio. Not Hubitat's choice, That's how Z-Wave works.

However, as I learned tonight from the other thread, a shutdown from the Hubitat Web Interface, follow by removing the power cord for 30 seconds before plugging it back in, will (sometimes) fix that issue.

I had the same thing happen when I joined HE (2 months ago) and after pairing multiple zwave devices the issue occurred when I got to pairing the zwave locks, This was amplified by the NUMEROUS repeated attempts because I didn't know with HE you need to NOT pair in place these locks but pair them right next to the hub then put in place (different than the other 2 platforms I was used to)......but after about 30 failed attempts,

I had the same thing happen to where nothing would pair, even devices I already paired but removed to try again, then Like the OP I noticed all zwave paired devices were gone. After contacting @bobbyD he stated to

Do a HubShutdown (NOT Reboot) then when the hub light turns red, pull the power cable for 30 seconds power cycling the hub.....and sure enough the devices returned, but I continued doing the hub shutdown process before pairing each lock as it appeared the zwave radio signal from the hub was it's highest (no other issues with this besides locks)

removing power and waiting for 30 seconds did the trick - it all seems to be fully operable, devices are in place and zwave radio is normal.
I hope it's not something that has to be performed frequently...

1 Like

I only had this trouble with the locks.....they are a known problem but aeotec range extenders help this problem you can search the forum on these for more info.

no Aeotec for me...

Tried to restore the database to the last working backup and I am getting 500 on the devices page and empty zwave radio again.
Restoring 2.0.9.133 backup on 2.1.0.117 firmware officially breaks the database.
power off-30 sec wait, here I come.

I start reconsidering migration from ST.
It was laggish at times, but never had anything like this in almost three years with more than 60 devices...

As long as you have the 2.0.9.133 database backup, you can restore the platform from http://[yourhubip]:8081. Then restore the 2.0.9.133 database from backup.

2.1.0 is a massive change in alot of things and when you updated it updates your database. So when you restore the database you also need to restore the firmware to 2.0.9 version. It says all this in the release information.

I am working with Hubitat support right now (BTW, I am very impressed by their very fast reaction and followups) and will report back into this thread about any learnings, so broader community can benefit.

2 Likes