The only thing I see popping out in the logs is wrong time - the hub thinks that current time is somewhere before 5/25/2015. That prevents hub from connecting to the cloud and figuring out which account it belongs to. If 2.2.2 works, I'd say keep using it for now and let us collect more information on the issues that crop up with 2.2.3. We do our best to reproduce and fix them as they come up. Right now, I can't say for sure what's broken.
2 Likes
Interesting you said that. I noticed this earlier. When I look at the time from Settings page, it's correct.
But when I look at the system time via the diagnostic page, I see this.
Just as a data point, my C5 updated just fine and seems to be working good. It did take a slight bit longer than normal to do the update itself, but I attributed that to the large number of changes. The reboot after the update didn't seem abnormal in any way.
1 Like
I've updated 2 C-4, 1 C-5, and 1 C-7 today. All working. To be fair, though, 1 C-4 and the C-5 have almost no apps on them, they are for development.
1 Like
I too have been battling a extremely slow C5 hub for the past 6+ hours.... I think the update screwed up my db so now I am downgrading everything prior to the update and see if it fixes my issues.
Yup going back to 2.2.2.129 resolved all my problems.... something very wrong with the new version.
I had the unresponsive/slowdown issue with one of C-5 hubs, but not the other C-5 or the C-7. Here's what happened along with what resolved the issue (edited from a PM sent to someone):
I've had a tough time updating my Hubitat C-5 that only has zigbee devices (mostly Xiaomi - admittedly unsupported). The z-wave radio was disabled on this C-5.
- After the update, the hub slowed to a crawl. The Xiaomi devices threw an error. But all my zigbee devices (even the ones on the compatibility list) were unresponsive or very slow to respond. So was the web interface.
- So I rolled back to 2.2.2.119 - everything worked fine again.
- Repeated the process of updating 2.2.3.118. Same problem again. This time, I decided to download the latest backup, do a soft reset and restore the backup. Hub remained excruciatingly slow (device response and web interface).
- So I rolled back to 2.2.2.119 for the second time - everything worked fine again.
- Then I updated to 2.2.3.118 a third time. Same issue again. This time, I used the Diagnostic Menu (8081) to shutdown the hub. Disconnected power. Powered it back up again. Same problem (extremely slow device response and web interface).
- So I rolled back to 2.2.2.119 for a third time - everything worked fine again.
- On a lark, I decided to enable the z-wave radio and then run the update to 2.2.3.118. After the update, everything worked perfectly.
Since then, I've disabled the z-wave radio, removed power, and booted up again. Everything still works fine. So, for whatever reason, this platform update put my zigbee-only C-5 into a funky state if the update was applied when the z-wave radio was off.
3 Likes
Both my C5s updated fine about 14 hours ago and no issues.
Note: my C7 that shipped July 24th still hasn’t arrived !!!
Waiting on mine as well shipped July 25th so you are not alone.
But mine has to come to Canada through regular post so could be awhile.
@aaiyar I have about 20 Z-Wave devices and my Z-Wave radio was ON when I was having my troubles.
1 Like
I have the z-wave radio disabled on one of my C-5 hubs and both hubs updated without issue. I ran Hub Watchdog on both about 15 minutes after the update and the times were .101 and .103 (virtual switches), and both hubs continue to be very responsive.
1 Like
I am a Canuck as well and I just check the CanPost app. Mine is out for delivery today.
Weird. My zigbee-only hub is a C-4 + Nortek stick, so not the same as yours. My two dev hubs (one of which is a C-5) have both radios turned off.
Glad you figured out something that worked! Very strange!
2 Likes
I updated then my C5 server hub became unresponsive. My other C5 hub updated fine, but has much less devices and apps installed. I rolled back the update. Not sure what I should try. I couldn’t access devices or apps menus after the update. Everything else slowed to a crawl, even after multiple reboots.
My advice right now is to wait for the next update or bugfix. It will get sorted out sooner rather than later, no sense of driving yourself crazy if it didn't work right the first time.
Sounds good to me 
thanks
Yeah definitely something going on I noticed huge performance issues after the update and I am on a C4.
What performance hits are you seeing?
I just upgraded my upstairs C4 hub which is mostly Z-Wave with a few Zigbee devices and it appears to be okay.
Have held off on my main C4 hub though.
My control hub - a C5 with radios is working well after the update.
Here you can see the massive spike yesterday after the upgrade, I also noticed automations taking a while to fire.
Late last night I ran a soft reset and fully powered down the hub, which as you can see did help a little, but its still very inconsistent.
Major slow down issues on my hub aswell, bringing everything to a crawl / stop. Rolling back now.
I applied the update to my C-3 yesterday; I've been using virtual switch delay as a criteria to auto-reboot. The udpate to 2.2.3 went smoothly, but it was concerning to see that Hub Watchdog measured delays had easily tripled from their typical range and remained consistently elevated. Shutdown and reboot after power cycling had no effect.
I use .07 for my warn value, and prior to 2.2.3 it was rarely exceeded until a few days of runtime, at which point things would rapidly go down hill-- I'd soon begin to see max delays in the tens of seconds, and my WebCoRE piston would restart the hub. After updating yesterday, delay values consistently exceeded .2 with periodic spikes exceeding 5. The UI seemed very sluggish, yet automations seemed to work well enough. I considered reverting back to prior firmware but figured I'd see what happened after nightly maintenance.
This morning, the story is completely different. Database went from 34 to 4 MB; typical delays are back to their prior update levels (and seem to be averaging lower) and UI is very responsive. I am however seeing periodic spikes exceeding 5 seconds roughly once or twice in a one hour period; I'd never see those delays so soon after reboot on prior firmwares until a couple of days had elapsed. Maybe some previously deferred garbage collection is scheduled more regularly now? At any rate I'm encouraged to see the performance on 2.2.3 has been restored to at least as good as it was prior to the update.
4 Likes
