2nd Corrupt Database recently - Device dropped off

I have a C7 with firmware 2.2.8.152. As with others that have reported a 500 error I first became aware of a problem when I noticed that none of my automations were working this morning.

I went to the logs and only saw this:

I tried going to other pages, such as apps, etc,, but they all had just the 500 error.

I was able to get to the diagnostic page:

I did a reboot, waited for the light to turn red and pulled the plug (from the outlet, not from the hub). I then waited for 30 seconds before plugging it back in. I saw it took about 45 seconds for the light to turn green.

I then waited about 18 minutes and went to the logs, but still was getting the same 500 error.

I first tried to find my hub here:

When that didn't work I then went to the Advanced Discovery and entered my MAC address to try to find the hub

When I did I got a database error:

I clicked the database repair link as I was thinking I needed to load in a previous backup, but when I looked up how to do that I only found this:

Which, of course I couldn't do as that page was also just giving me the 500 error. So I went and did the Soft Reset from the Diagnostic page and was able to restart the hub that way and restore from a backup.

However, this is the 2nd time I've had to do this in the past couple of months. I never had to do this before. I have not added any new hardware. The only software changes I did was to associate 2 sets of Inovelli red dimmers that are in 3-way situations instead of trying to sync them via apps (and that was several weeks ago).

I then went to the Z-Wave details page (BTW, I wish it was always on the Settings page, not just if Advanced Options are on) and saw one of my devices had no information in the route details. This is an Inovelli Fan+LIght 7. This is what I noticed last time I had a corrupt database (i.e. a device, but not this one, suddenly dropped off the list). I have no idea what would cause this. It is fairly far from the hub, but I do have an Aeotec 7 range extender between it and my hub and I've never had problems with this device before.

I tried to repair just this device but that failed.

Then I didn't have the Repair option anymore. I tried "refresh" but that just said Pending. I then pulled the air gap and waited 30 seconds before pushing it back in. When I tried Refresh this time, it stayed pushed in for about 5-10 seconds, but then the button popped back out and was still showing Pending.

I then tried throwing the breaker for the whole room. When I went off the Z-Wave logs page and then came back to it I found I had the Repair button again for this device, so I tried that again. It said it is repining the node, but then failed saying it is unreachable.

Screen Shot 2021-10-30 at 9.43.57 AM

So, instead of getting better and better over time, I'm finding I'm having more and more problems over time. I have no idea when the network seems to be degrading. Any ideas on this?

Any ideas on how to get this device back into Hubitat?

@Stu_The_K Download your current database to your PC. Do a soft reset and then apply the database from the pc you backed it up to. Once that is done, immediately update to the latest firmware. Then see how things are.

1 Like

I tried Repair one more time just for the heck of it and it worked.

My wild guess is that your DB was corrupted and the Hub went back a couple of internally saved backups... to one before your latest Z-Device add. Thus the DB didn't know anything about it, yet the Join was still valid out on the ZWave Radio.

Ultimately you did the right thing randomly :smiley:

2 Likes