This is indicative of the sensor not receiving an ack from the hub for the event that it just submitted, so its a bit out of range of the hub or another repeater.
3 Likes
My Hue bulbs are all connected through HA with the HADB enabled. My zigbee mesh has been SO much happier since moving the Hue bulbs to HA and controlled via the bridge. If the Hue bridge integration is 1/2 has good as the HA bridge, then it would also be an awesome option.
I did the HA just to avoid having to buy a Hue bridge since the HA was already on hand.
I did leave the Hue motion sensors (indoor and outdoor) on Hubitat. They seem to all be fine now, including the outside ones once they got a firmware update...
1 Like
If your setup is working for you, there's no need to change it. I had my Hue bridge long before adding HA into the mix. No sense in my moving anything off of it, and I prefer to keep my bulbs on their own network. I use Z2M for a lot of Xiaomi and some IKEA Zigbee devices, which has been working perfectly. I wouldn't want to mess with around by adding bulbs that would potentially end up being poor repeaters for my other Zigbee devices on HA.
There are also a couple of handy apps I own that only work on the Hue bridge, so that's another benefit for me personallly.
3 Likes
Not that it's been an issue, but would booting the Zigbee power help? I am more invested in Z Wave, so my Zigbee mesh is small (and getting smaller) The outdoor, is well, outdoor, about 30 feet from the hub (C8) on a brick wall, next to a plate glass window. I would need to look, but I believe the zigbee power is currently set on 4
I realise this thread is way old but @wiegout did you ever resolve this? I'm having what I think is the exact same issue (I posted a few hours ago). It pairs fine and sends some initial values - lux, temp, motion active then that's it - nothing, no reports of any kind. I'm also on the C-8 hub with Hue Outdoor Motion model SML004 just feet from the hub (C-8) so there should be no issues...
No. I finally gave up and sent it back to Amazon. Couldn't get it to work reliably with the latest firmware.
1 Like
In fairness that was back in November. Maybe they've fixed the problems since then. I do think that there are issues with the Zigbee implementation on HE. They are working on another issue that may/may not be related. See: https://community.hubitat.com/t/unable-to-pair-zigbee-3-0-device/137315/32
1 Like
Thanks I'll do the same - I've just updated my other post with one of my finest limericks (I won't give up the day job :rofl)
Cross posting here and your other thread but this is still an issue. I have multiple SML002 (older) and multiple newer SML004. Nothing suggested works reliably. It is isolated to SML004 The SML002 work great connected directly. Will likely move back to these devices integrated w/ CoCoHue as everything worked well.
Curious, are the SML004's working for anyone? Or is the problem universal with this version of the Hue Outdoor Motion sensors and Hubitat?
1 Like
I see you are in the beta group. There is a fix in a version released today that may help, depending on what your problem was--check the release notes there for more.
1 Like
@mike.maxwell responded to my post querying this potential fix. Apparently it only fixes devices that are unresponsive for a few minutes after inclusion. The newer Hue Outdoor motion sensors include but are completely unresponsive permanently (at least for myself and several others on the forum)
I got two to fully include and be responsive by rebuilding zigbee network twice in succession and then pairing without 3.0 repeaters, with no other steps or activities in between. It then caused instability with other, older SML002 devices no longer responding.
I thought I had a SLM003, but I don't, I'll get one ordered.
