Up until February my Hue motion sensor was working beautifully via the CoCoHue app, returning temperature and motion data. I didn't notice it until now, but since February there hasn't been a single event generated for this device. The hue plug I have configured via CoCoHue is still working as expected. I am on the latest version of the app and drivers according to package manager and I can see motion activity in the hue app (so I know the sensor is working). Has anyone else experienced this? Any idea what I can do to try to resolve the issue?
Why not pair it directly to hubitat itself? That way you can use device watchdog on it..
Also, the Hue plugs work very well as repeaters on Hubitat.
Do you have the "Enable 'push' updates (Server-Sent Events/EventStream) from Bridge" option eanbled in the CoCoHue app? If not, you'll only get motion events on polling, and even then only if it's different from the last time it was polled. So if not, then your polling interval also matters. What are both of these set to? If you enable the eventstream option, you should get instant updates as long as the connection to the Bridge is there (this is technically still experimental on the Hue side and I think Hubitat's interface still has some issues, or perhaps Hue's implementation does, but it works most of the time).
Beyond that, to troubleshoot, I would need debug logging enabled for the CoCoHue app, CoCoHue Bridge device, and the motion sensor in question, and ideally also the DNI of the device in question. These can be PMed to me if you do not want to post them here.
If you upgraded (via HPM or manual) and never went into the app and hit "Done," that was also necessary for the last major version change--but that's probably not it, since you'd get other errors, too.
Finally, I'd second the suggestion to just use the sensor directly on Hubitat if that works for you; however, if you want to use it in the Hue app, this isn't an option, and you should still be able to get it into Hubitat this way.
The built in hue integration doesn't support motion sensors, and I'd have to disconnect it from the hue hub in order to connect it directly to the hubitat. There are integrations I keep local to the hue hub so they don't burden the hubitat hub.
@bertabcd1234 I do not have the push updates enabled, but for my purposes the polling was sufficient in the past (the integrations using this are not time sensitive). The polling interval is set to 1 minute. I'll enable the debug logs and post back when they have populated with some data.
I'm not sure what the default "inactive" period is on Hue before it sends an "inactive" event to the hub, but I seem to recall users reporting it was less than 1 minute. If you're moving around a room for longer than this and the sensors takes longer, then this shouldn't be a problem, but if you're just quickly walking by (e..g, a hallway), then it may totally miss the event, depending on when the polling happens. I'd recommend enabling the push/eventstream option unless you have a reason not to (e.g., you're on old firmware or have a v1 Bridge), or you may wish to increase the polling interval to reduce the likelihood of this.
But the logs would give an idea for sure of what the Bridge "sees" for the sensor, which is all the app should be doing--polling from that--as-is.
1 Like
I just enabled the push updates and I'm seeing active/inactive events now, but nothing for the temperature yet (which is the primary use for this device). I'll take a look at the logs and see what I can discern from those.
Looks like enabling the push events did the trick. Temperature data appears to be flowing through along with illuminance now. I left it off because I've historically had problems with anything labeled "experimental" and didn't want to risk it, but this will work better for me anyway. Thanks for the help!
If you really don't want to risk the "experimental" thing, a quicker polling interval would likely do it too (for motion, at least; I'm not sure why temperature wouldn't be there--it should get something). But instant updates are what I use on my own setup, and I'll remove that label once Hue's API stabilizes. 
1 Like
