I'm having more and more difficulty getting Hue Outdoor Motion Sensors to stay connected and reliably report motion/light to Hubitat with a direct Zigbee connection to HE. I have a C-8 pro. Seems the Zigbee pairing is just not as great or reliable, and I'm tired of constantly troubleshooting and pairing these over and over just to get motion sensing to reliably work.
My question is - I already have 3 Phillips Hue hubs with over 100 lights all connected through the HUE Bridge instead of directly to HE, and I use the Hue integration with HE to control the bulbs through the Hue Hub. Could I do the same with the HUE Motion Sensors? ie: instead of paring them directly to Hubitat, which seems problematic, I suspect I'll get a more reliable connection pairing them to the Hue Hub since there are a hundred lights around them for them to repeat their signal through.
Can I find and use the sensors through the HUE hub integration in HE (like I do with the lights) instead of a Zigbee direct connection, and use that connection to read the motion and light and control what I want to control?
Not with the current built-in integration, no. There are two currently maintained community integrations I am aware of (one of which I wrote) that work with them, assuming you have a V2 (square) Hue bridge, among other ways you might be able to do the same thing.
Thanks for the response but I'm not quite understanding your answer...
Are you saying there ARE two other integrations (including yours) that DO work? Could you provide a link? Yes, I have the V2 square HUB.
Would like to just finally get these to work reliably, and I imagine they are going to work much more reliably talking to their own HUE hub where they can use all the light bulbs as repeaters than talking directly to the Hubitat... thoughts?
Looks like I may already be using a community HUE integration, the one I have installed is "Advanced Hue Bridge" and it has a "find sensors" button, so I'm assuming I can use that.
And really that was my basic question, I wasn't really asking specifically what driver/integration to use, but more that I can use SOMETHING in Hubitat -> Hue Bridge -> Outdoor Motion Sensor, to take advantage of the better response with the HUE bridge, rather than Zigbee Hubitat -> Outdoor Motion Sensor.
Seems the answer is yes, if I use one of the community 'advanced' integrations.
And @bertabcd1234 - I've added the Hue Outdoor Motion Sensors to the HUE Bridge now, then found them through the Advanced Hue Integration, when I poll them with 'refresh' they returned one set of values, but they haven't updated since (over 15 minutes), even after multiple 'refresh' requests.
So I'm confused if I still have an issue, or if these won't behave like I want. Basically I'm looking for the most reliable way for HUE Outdoor Motion Sensors to detect motion and trigger lights (somewhat quickly, with little delay), through Hubitat... using Rules that when motion is detected, turn on lights.
Would there be some kind of delay with the MOTION SENSOR - > HUE BRIDGE - > ADVANCED HUE INTEGRATION - > HUBITAT? I'm confused on if the motion will trigger somewhat quickly with this integration to HUE or if it has to be 'polled'? I know with the direct Zigbee integration it can be quite quick to trigger a rule, but my problem is the size of the house and where these are located I'm having difficulty getting direct Zigbee connection to be reliable, so that's why I was going to see if going through the Hue Hub would be a better connection.
That one is not my integration, and I am not familiar with it, so I cannot help much. I would suggest asking in the topic that developers tend to create for their app and driver releases.
However, in general: they should not need to be polled if you have a v2 (square) bridge with relatively recent firmware (last few years, available for all v2 bridges) and your integration is configured to use the new API, which I assume that integration supports. Polling is necessary with the v1 Hue API. And note that a "refresh" from Hubitat is likely to just fetch the current values as reported by the Bridge in any case, not force the sensor to send a new value (e.g., re-read current lux, etc.).
