I don't know what parameter this is, I'd have to pair it to the Hue bridge and sniff away at it, in any event mine is being cantankerous ATM and refuses to pair and I just don't have the time right now to poke at it...
@mike.maxwell - after a bit of sniffing I think that the parameter for config.ledindication on the hue bridge is in cluster 0x0000, and it's attribute 0x0033 (not part of the ZCL spec, appears to be manufacturer specific). Hope this helps!
1 Like
I've kind of warmed to the light, it lets me know its seen me, and if the lights don't trigger, there's a problem Houston 
I am having this exact same issue but when I try to use that custom DH I get
"unable to resolve class physicalgraph.device.HubAction @ line 57, column 28."
Change “physicalgraph” to “hubitat”.
Thanks
@mike.maxwell I've been playing around writing a custom DH for the Hue motion sensor and I've been looking at the example ZigBee code in the GitHub repo. Can you tell me what the syntax is for the "he rattr" "he cr" "zdo bind" commands? And to write an attribute ("he wattr"??).
I too, am unable to get anything more than Philips Hue Motion sensor connected. Temp, motion does not work. Will try workaround in this thread.
I've just added 2 Hue Motion Sensors and had the exact same issue. Paired fine and identified as Hue Motion Sensor, but no data at all was being received. I switched to the custom DTH here and they then started sending data OK. Switched back to standard driver and continues to work OK.
@mike.maxwell Looks like there is still an issue with the standard driver for the Hue Sensors. I'm running 2.0.4.116
Yes, there will be an update to this driver in 2.0.5 which will resolve the configuration issues.
5 Likes
I just received my Hubitat hub today and I've been busy adding devices to it. I have just tried one Hue Motion Sensor so far but I'm getting the same Unkown status as the others in this thread.
When will version 2.0.5 be released?
If it's very soon I won't bother with adding the custom driver but I'll wait for 2.0.5 instead to resolve the issue.
I'm curious if those having issues with Hue motion, have a hue hub setup at home. I do not and 2 2older sensors moved from ST work perfectly and paired well. Even the 2 brand new ones from Amazon also paired and all 4 sensors are working amazing. The battery life is so outstanding, with my original 2 sensors in a very busy area, close to 2 years, and same dang batteries.
It is possible that those with a hue hub at home, is interfering with the sensor pairing, as the sensor is seeing the "phone home" signal from the hue hub? Or did I start drinking way too early today ??
I have a Hue hub here with a sensor connected to HE, rather than Hue. I’ve also got 5 dimmers on Hue and two on HE. I don’t know how, but all are working fine.
It would seem that version 2.0.5 indeed fixes this issue. I added a second motion detector today which had previously been paired to the Hue bridge. I was detected fine and detects all data available from the sensor.
Thanks for fixing this issue guys!
1 Like
