Things have been somewhat slow on my C8 with v2.4.3.177 the last several days. I looked at the cpu load within Hub Information driver and it was hovering around 20%. The logs/device stats showed that the Hue integration was responsible for 62% of that cpu load. No idea if that has anything to do with the slow responses but I disconnected the Hue hub and my cpu load dropped to 4-8%. So my question is....
I have a "spare" c8 I have been using for testing. Will moving the Hue hub to this spare then enabling Hub mesh help reduce the cpu issues?
Looks like a Hue reboot helped a lot for now. from 20% down to 2%. I have had this before though and over time the hue starts eating more and more cpu. I really like to have it off my main hub but not sure the alternative will be any improvement
Well there is definitely something going on here. Initially suspected Hue as all the motion sensors seemed slow if at all in responding. I would walk in an area with such sensor which should cause a light to go on but was left in the dark. I knew the sensor triggered by the red LED flash. I checked the hubitat log and it did not show an active state it did however shortly there after an inactive state. Looking further into the log I noticed that same sensor logged an active state an hour or so earlier. This was happening to at least 3-4 other hue sensors. Once it logs inactive these sensors behaves normally for a while until it doesnt
All that said, I am not convinced it it Hue related. Door zwave contact sensor and/or switched have been super slow to respond over the last few days.
Interesting. I thought it was a setting for the sensor. I have several sensors that flash red when detecting motion.
In any case, the motions sensors are giving huge grief (wont trigger, stay active for ever, etc) which reminds of the time when I first got the C8. I then removed them all from Hubitat and integrated them into HA. About a year ago I decided to retry the Hubitat integration and they worked fine until about a week ago.
Are all of your physical Hue devices (i.e. Hue Lights & Hue Motion Detectors) connected directly to a Hue Bridge, and then that Hue Bridge is connected to Hubitat via Hubitat's built-in Hue Bridge integration?
When you originally had your Hue Motion sensors connected to Hubitat (i.e. when you first got the C8), were they connected directly via Hubitat's Zigbee radio?
Are your Hue bulbs receiving constant power at all times? The Hue bulbs on the Hue bridge are the only Zigbee repeaters on that particular Zigbee mesh network. Thus, turning them off via a wall switch or lamp/fixture switch will take them offline from the Hue Zigbee network, which could lead to disruptions in communications for the Hue motion sensors (assuming they are also paired to the Hue bridge.)
What model Hue Bridge are you using?
Have you updated the firmware on all of your Hue Lights and Motion sensors via the Hue bridge and Hue App on your mobile phone?
What Zigbee channel is your Hue bridge using?
What Zigbee channel is your Hubitat hub using?
What 2.4GHz WiFi Channel and channel width is your home WiFi network using?
Just trying to cover all of the typical Zigbee troubleshooting steps.
1 & 2 - connected directly via Hubitat's Zigbee radio
3 - Bulbs always powered
4 - V2
5. Up to date for lights. No motion sensors on the Hue hub (well... They are now)
6 & 7 . Ch 20 Hubitat zigbee. Ch25 Hue zigbee
8. Using Asus Routers AI mesh setup. The channel is set to auto. Current channel is 8 but that could change I think
BTW: I have removed all motions sensors from Hubitat Zigbee. They are now connected to the Hue hub -> HA -> HA/Hubitat bridge. Been less tha 24 hours but each sensor so far appear more reliable. Time will tell
The above response seems to contradict the following from the original post, which refers to Hubitat's Hue Bridge integration.
If all of the Hue devices (lights and motion sensors) were directly paired to Hubitat's Zigbee radio, why would you even be running the Hubitat Hue Bridge integration?
Nice - we can eliminate that possibility.
If the Hue Bridge is offering firmware updates for the motion detectors, I would go ahead and perform the update.
Great, no conflict there.
You mention you're running a instance of Home Assistant as well. Does it have its own Zigbee radio? If so, what Zigbee channel is it using?
Asus routers typically allow the user to control the WiFi channels and channel width. I would recommend taking manual control of the 2.4GHz radios on each Asus device, and changing the 2.4GHx WiFi to use channel 1, 6, and/or 11 on each of your Asus wireless access points/router. Set one of them to 1, the next to 6, and the next to 11. Use a 20MHz channel width. This will avoid conflicts with Zigbee channels 15, 20, & 25.
So, this is where I am confused again... When testing without Home Assistant in the loop, did you ever have all Hue Lights and Motion Sensors connected directly to the Hue Bridge v2, and then use Hubitat's Hue Bridge integration to bring those devices into Hubitat? I thought that was the original configuration that started this thread? Your response to my earlier list of questions (1 & 2) seemed to contradict my original assumption...
I have all of my Hue lights connected to a Hue Bridge and then connected to Hubitat via the built-in Hue Bridge integration. This has worked great with no noticeable impact on overall system CPU usage. I will say that the Hue Bridge integration is device that has the highest Device CPU usage, but it is pretty trivial in the grand scheme of things. My C8 Pro's device's use about 2.7% total system CPU. The Hue Bridge integration is 63% of that, but it is not slowing anything down. The one big difference is that my Iris v2 Zigbee motion sensors are all paired directly to my HE hub's Zigbee radio, not the Hue bridge.
Didnt read your question correctly. The motion sensors are connected to the zigbee radio. Bulbs are on the Hue hub integrated onto Hubitat with the Hue Integration app. If I had the sensor on the Hue hub (as I do now) I would not be able add them using the Hue Integration app which offers only Lights, Groups and scenes.
I have never been certain that the Hue hub was causing my issues and now I am (almost) certain it did not. Since removing the motion sensors my hub cpu load is at its worst 50% of what I had with the sensors on the Hubitat zigbee. Most of the time is is aroun 6%
As for the wifi channel, my routers are setup using AI mesh. Unlike in my old setup using AP I can not set a separate channel for each router in the mesh
Actually, things have changed pretty dramatically over the last year with respect to Hubitat's built-in Hue Bridge integration. @bertabcd1234 expanded its capabilities dramatically, utilizing Hue's new API.
Huh. Never seen this. Is this another version of the app?
NVM: Just installed the integration on my "test" hub. I don't know how I missed this. Oh well, leaving for vacation in 3 days. Probably not a good time to implement something new. Thnaks for the info, though.
A year or so (maybe 2?) ago, the native Hue integration was refreshed and now looks much like CoCoHue. Not surprising, as bertabcd1234 created (and still manages) both integrations.
