Running pretty much smoothly for years. Last night we had a power flicker ( off- back on, clocks now blinking ). Woke up to all the zigbee lights on in the house and the hub with no cloud connect ( Alexa not connecting ). Log in and reboot hub. Alexa reconnects. Some lights working. Figure I’ll turn off zigbee for an hour to panic the devices and get them back online. I’ve been on CH26 for over a year. When I turned zigbee back on, it’s now on ch11 and when I attempt to change it to 26 it just goes back to 11. So now all my devices are sitting on 26 with the hub on 11. I know eventually the devices will find ch11, but I want 26 back eventually ( because it worked perfectly for so long )
Latest FW, Any ideas?
Sounds to me like you might have a bit of database corruption. Either wait it out until tonight and see if the db clean up does anything for it, or do a soft reset and restore from back up. Have you ever done that?
IMHO channel 26 is the edge of the channels and can cause some flaky responses. But if it works for you. Just thought I'd mention.
1 Like
I had pretty much the same thing happen over the weekend. I restored my last backup of the hub, from the day before, and everything started working again. Most likely database corruption.
1 Like
Thank for the replies, I shut all power down for 45 min then repowered everything and waited 15min and all seems to be now working. Our power is so reliable, I haven’t has a Power blip like this in prob 5 years, I have an extra UPS, so ill probably throw the hub and modem on it in case this becomes more frequent.
3 Likes
I just want to add a freindly reminder that your meshes are rebuilding, so let it stabilize for 24-48 hours before you decide if something is still wrong. things might be intermittent with zigbee and some plus devices while this works out. Just be patient with it. I know you've been around for quite a while, so you know that, but just wanted to reiterate for newcomers that might see this thread. Sometimes we expect it to be instantaneous. Especially since you've not had any real trouble in quite some time.
Glad that it was an easy solution for you.
1 Like
That's a good idea even if power outages do not become more frequent. Abrupt power interruptions can corrupt Hubitat's H2 database (for eg. if it is in the middle of a write operation).
