I update the firmware on my C7 From 2.3.4.130 to 2.3.9.201. The UI became irresponsive after the update. The IP also changed (i had a static IP set) but was able to fine it using the tool on the web. I was able to use the diagnostics tool to revert back to 2.3.4.130 and the hub worked fine after that.
So at a second attempt, it update to 2.3.9.201 but still very unresponsive. Was able to go back in the diagnostics tool and did a soft reset. It completed that but still no stable connection.
The hub has a green LED and occasionally flashes blue.
I did update the Zwave driver prior to updating the firmware.
i did power cycle it (30 seconds) and now I can't connect at all but the "find my hub" still finds the IP address and when I try to log in it shows to HUB name but just never connects.
I can connect to the Diagnostic tool now.
At this point I'm ready to start from scratch if that what it takes.
Update: I used to diagnostics tool to go back to 2.3.4.130 but When I finished that i was surprised with this:
That resulted unto this:
But thes was still unresponsive so I tried the diagnostics tool and found this:
I got brave and did a Full Reset. It took 2 tries but it said that it completed it. Still at 2.3.9.201 and still unresponsive UI. Trying safe mode next.
Went back to 2.3.4.130 and the UI works great. Just need to re-add all my (6) Z wave devices.
Question is: Will my C7 every work well with 2.3.9. What am I missing here. At 2.3.4 everything works as you would expect. At 2.3.9 it will take many minutes to load any screen.
The only reason to ever do a full reset is if you are selling the hub. In fact at one point they even removed that option, but users complained they couldn't wreck reset their hub, so support went and put the option back in.
For future readers, Soft reset does everything you need and won't wipe out radios. Full reset is ill-advised to ever use.
Yes. I suspect that nearly every user is on 2.3.9, except for some holdouts that either forgot to update, or purposely don't update because they don't want the hub to go online for whatever reason.
Either way there have been very few complaints of this symptom in 2.3.9. This is probably the point where you should have engaged the community or the support team and awaited further instructions.
I suspect that maybe you should try to change the connection speed in the Settings menu, Networking. If you are at 100M change it to Auto, or vise-versa. If you haven't tried that, it would be the easiest thing to do.
On 2.3.4 I can surf through the UI without any delay.
On 2.3.9 It sometimes connect but takes minutes to change between screens, otherv times it just sits there with a spinning wheel.
Thanks for that. It was at 100M fixed. Set it now to auto. Do you think it will that big of a difference? On 2.3.4 it surfs through screens fast (as soon as you click) on 2.3.9 it takes minutes or sometimes doesn't change screens at all.
Yes there is a known issue with the connection speeds that causes the exact symptoms you describe. Often times just switching it to the opposite setting will fix it.
I'm rebuilding my (small) network now and remove some apps that I don't use anymore. I will make a backup before trying again. Next is waiting for another rainy day to try again and will reach out sooner next time.
Thanks for your help on this topic. I was finally able to update to 2.3.9.201 but not without some issues. Here is a summary just in case someone else has this issue:
verified the network speed setting. It was at 100 Mbps fixed and stable (still on 2.3.4)
I changed to "auto negotiate" and the LAN connection became unstable so I changed it back to 100 Fixed and it went stable again.
Created and download a backup of the database to my computer
Update to 2.3.9.201
After the reboot screen appeared, wait 15 minutes and still see this:
Use the "find my Hubitat tool" and see that the IP address is still the same (Reserved in router) but still can't connect to the UI
Did a ping test from CMD and found connection unstable:
Was able to connect to the diag tool (:8081) and rebooted the hub.
then the "find my hub" tool came with a weird result. It found 2 hubs (I only have one) and the 2nd one had an IP thats nowhere within anything that my router would assign:
Used a paperclip to reset the communication port. After a few minutes my normal IP appeared again in "find my hub"
Now I could connect to the UI but still VERY slow
went to settings, LAN speed and noticed it was set to the default setting of "auto"
Changed that setting to 100 Mb fixed and connection stabilized.
clicked on devices and found no devices in hub.
Restored using the backup made at the start of this adventure.
I find it strange that you changed to auto and the hub became unstable (in what way). What is the hub plugged into? Directly to your router or a switch or some kind of mesh device?
Some routers do not play nice with the auto setting, that is why the 100mb option was originally added. I had that issue with my first c7 on my old router.
That shouldn't happen though to a standard interface.... Auto is much better at correction than fixed full is. It's rare to actually need it. "Usually" issues only happen on older equipment. Though sometimes someone has inadvertently set a backbone device to fixed (switch, router etc) and anything else plugged in set to auto will get dumped to a lower speed because auto can't negotiate.
I connected it to a managed (TP Link Omada) switch and assigned that port to the Hubitat. Used DHCP Reservation, then switch to Auto on the hub. It did connect to the switch at 100 Mb.
Now Hubitat is responsive at 100 Mb fixed and Auto negotiate.
and put the option back in.
