With 2.3.1.135 my Motion and Mode Lighting builtin app stopped working. I went to check the logs and what I find is that it doesn't even show in the logs as doing anything. Then I checked the sensors and they all (I have 5) light up their red lights when they see me which means they lost comms with the hub.
Forgive me if this sounds like a dumb question but have you tried downgrading to the previous version to see if the problem goes away? And I assume the Hue motion sensors are paired with HE directly, not with a Hue hub...?
Well good to know! When reading the release notes for .135 the only thing I see that looks like it might even be vaguely related is this... I don't suppose you saw anything like this? You said there wasn't anything in the logs but just checking.
Fixed 'activator' error. If you experience this error, open Groups and Scenes (parent app) and hit Done. This error occurs with other apps, such as Motion Lighting or RM.
That's curious - I have some hue motion sensors paired directly and am running .135 and haven't seen any issues (mine triggered as recently as 5 minutes ago w/ motion lighting).
It's of course entirely possible that the issue is not with .135 but rather the process of rolling back coincidentally did something that fixed the issue... from the release notes this was a pretty light hotfix.
I have a few Hue indoor motion sensors and an outdoor one and am not seeing any issues with .135. Did you try rebooting the hub again before rolling back the firmware? Before I added more repeaters, my outdoor sensor would sometimes fall off the mesh with firmware updates or power outages. I would just hold the reset down until it started blinking and then have the hub search for it. The hub will recognize it and it doesn’t effect any thing otherwise.
Mmmmm. Something is not ok with my Zigbee mesh. Now some Hue sensors work, others don't. My Ikea plugs are not working correctly, have turned on but won't turn off.
I would go to settings/shut down, unplug the usb cable once the red light is on the hub, wait a minute, plug back in. That’s the only way to power cycle the radios afaik. Then see what problems remain.
This is really weird. I also have a Hue Bridge for Hue lamps and Hue outlets integrated with the C-7. I found it was using channel 25, the same as the C-7 for its Zigbee mesh. I changed the Hue's channel and it selected 20 on its own.
Now all is well. How weird is this? They had been working fine together for more than a month when I bought the Hue Bridge.
In Flight Club, Tyler Durden says "if you start owning things, they'll end up owning you". I guess he's right.
A little add to this. I also use Hue motion sensors and after the update they stopped working. I tried that turn off on/off optimization check box under group settings that's been there forever and mine came back. The only remaining issue seems to be that if I shut off the light in a room at the switch, it will take a few minutes for the motion activation to work again. Just something else to try for anyone having the same issue.
In before Mike comes and says "no changes to zigbee were made in 2.3.1.135"
Maybe it's this:
Summary
Release 2.3.1.135 Available
Changes from 2.3.1.134
Bug Fixes
Fixed missing local dashboard icons and incorrect fan commands on thermostat tile.
Fixed 'activator' error. If you experience this error, open Groups and Scenes (parent app) and hit Done. This error occurs with other apps, such as Motion Lighting or RM.
Well I guess it would depend on whether the device had reported or not. In my case it was connected at the device level, however none of the automations associated with them would work. In my case they were applied at the group level, and only those using the Hue sensors had a problem after the update. The open groups and hit done fix did nothing, but changing that setting did. Although upon looking at the original post, it sounds like OP's devices weren't seeing the hub at all, so I suppose at a base level similar initial symptom, but perhaps not exactly the same if his devices weren't reporting.