On one of my C-4 hubs, the hub ground to a halt after the update. I logged in and there was a warning about high hub load. I tried to do a reboot from the web interface, it wouldn't reboot. I had to do a manual power cycle. I am not sure if it is related to a Hue error I am seeing or something else. I rolled back to F/W 133. Things seem to work, but still have the Hue error in logs, so I'm not sure if it's related or not?
Here is one of the errors in the log files: app:692025-11-06 07:02:46.616 AM
error
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: hueIntegration.ssdpBridgeHandler() is applicable for argument types: (com.hubitat.hub.domain.Event) values: [Event[archivable=true,data=,dataString=,date=Thu Nov 06 07:02:45 CST 2025,description=mac:001788679E39, networkAddress:C0A81E10, deviceAddress:50, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-001788679e39, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:,descriptionText=,device=,deviceId=,displayName=,displayed=true,forceAttributeUpdate=false,hubId=1,id=3630885,installedAppId=,isStateChange=,location=,locationId=1,name=ssdpTerm,producedBy=,source=HUB,subscriptionData=,translatable=false,triggeredListeners=,type=,unit=,value=urn:schemas-upnp-org:device:basic:1]] (ssdpBridgeHandler)
Even on my C8, I see high hub load sometimes after an update, and always after a full power cycle. It calms itself down in five or ten minutes and goes away. The issue after a full reset I assume is something to do with the Zigbee and Zwave radios restarting.
I believe for me, it is compounded by having so many custom apps and drivers that initialize all at once. I'm probably living on the edge now of needing a C8 Pro given how hard I drive my hub. Still, the hub is working great once things settle down. I rarely reboot anyway.
So, I can see where a C4 might be stumbling a bit at boot up trying to initialize everything. Have you tried just letting the hub sit for five to ten minutes before trying to use the UI? It could be caused by something related to the latest release for you.
That's a great point. I updated, didn't think anything of it until my evening bedroom blinds didn't work. The next morning is when I ended up having to unplug the hub. I did NOT wait 10 minutes for things to settle down before I got annoyed and downgraded to 133. So plenty of time after the initial firmware upgrade but not after my morning reboot.
