Weird issues since 2.2.5 update (Zigbee)

🛎️ Get Help
41

Parent child parameters
EzspGetParentChildParametersResponse [childCount=19, parentEui64=0000000000000000, parentNodeId=65535]

Child Data
child:[Kitchen Light 3, B84F, type:EMBER_END_DEVICE]
child:[Dining Room Hutch Light Left, 59EF, type:EMBER_END_DEVICE]
child:[Backyard Light, 2777, type:EMBER_END_DEVICE]
child:[Master Bathroom Sink Light Jacob 2, 0A5B, type:EMBER_END_DEVICE]
child:[Upper Hallway Light 1, 6617, type:EMBER_END_DEVICE]
child:[Master Bathroom Button, 82DD, type:EMBER_SLEEPY_END_DEVICE]
child:[Master Bedroom Dimmer Switch, D786, type:EMBER_SLEEPY_END_DEVICE]
child:[Dining Room Table Light 3, 3EDC, type:EMBER_END_DEVICE]
child:[Dining Room Table Light 1, 3C8E, type:EMBER_END_DEVICE]
child:[Dining Room Table Light 4, BA0D, type:EMBER_END_DEVICE]
child:[Master Bathroom Sink Light Lisa 2, 5CC2, type:EMBER_END_DEVICE]
child:[Kitchen Button, 6628, type:EMBER_SLEEPY_END_DEVICE]
child:[Dining Room Table Light 5, 5BF3, type:EMBER_END_DEVICE]
child:[Dining Room Table Light 2, 69E2, type:EMBER_END_DEVICE]
child:[Dining Room Hallway Light 2, 07E6, type:EMBER_END_DEVICE]
child:[Dining Room Hallway Light 1, EC2A, type:EMBER_END_DEVICE]
child:[Dining Room Hutch Light Right, 2579, type:EMBER_END_DEVICE]
child:[Master Bathroom Sink Light Lisa 1, 96ED, type:EMBER_END_DEVICE]
child:[Upper Hallway Light 4, F8AD, type:EMBER_END_DEVICE]

Neighbor Table Entry
[Basement Hallway Routing Outlet, 0184], LQI:255, age:4, inCost:1, outCost:0
[Brennan’s Room Light Strip, 0720], LQI:249, age:3, inCost:3, outCost:1
[Fireplace Fan, 19BD], LQI:254, age:4, inCost:1, outCost:1
[Connor’s Room Christmas Lights, 1CA0], LQI:254, age:4, inCost:1, outCost:1
[Upper Hallway Routing Outlet, 235B], LQI:254, age:4, inCost:1, outCost:1
[Garage Front Routing Outlet, 635C], LQI:254, age:3, inCost:1, outCost:1
[Jacob’s Desk Routing Outlet, 7AB7], LQI:255, age:4, inCost:1, outCost:1
[Kitchen Routing Outlet, 968B], LQI:254, age:4, inCost:1, outCost:0
[Living Room Routing Outlet, 9869], LQI:255, age:3, inCost:1, outCost:0
[Garage Side Routing Outlet, CAAC], LQI:251, age:3, inCost:3, outCost:3
[Master Bedroom Heated Lotion, D13B], LQI:255, age:4, inCost:1, outCost:0
[Brennan’s Room Routing Outlet, D416], LQI:255, age:4, inCost:1, outCost:0
[Master Bedroom Routing Outlet, E1E0], LQI:255, age:3, inCost:1, outCost:1
[Ella’s Room Routing Outlet, ED24], LQI:253, age:3, inCost:3, outCost:1
[Basement Unfinished Workbench Light, F957], LQI:254, age:3, inCost:1, outCost:1

Route Table Entry
status:Unused
status:Unused
status:Unused
status:Active, age:64, routeRecordState:0, concentratorType:None, [Ella’s Room Routing Outlet, ED24] via [Fireplace Fan, 19BD]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Garage Light 4, 7B7A] via [Garage Front Routing Outlet, 635C]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Upper Hallway Thermostat, 421E] via [Upper Hallway Routing Outlet, 235B]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Connor’s Room Christmas Lights, 1CA0] via [Connor’s Room Christmas Lights, 1CA0]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Upper Hallway Motion Sensor, 752F] via [Upper Hallway Routing Outlet, 235B]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Master Bathroom Humidity Sensor, F6A3] via [Upper Hallway Routing Outlet, 235B]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Laundry Room Motion Sensor, 7951] via [Garage Side Routing Outlet, CAAC]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Basement Kitchen Stairs Motion Sensor, BD32] via [Connor’s Room Christmas Lights, 1CA0]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Garage Refrigerator, 8204] via [Garage Front Routing Outlet, 635C]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Living Room Dimmer Switch, 973C] via [Basement Unfinished Workbench Light, F957]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Addison’s Room Motion Sensor, 16E5] via [Upper Hallway Routing Outlet, 235B]
status:Unused
status:Unused

42

You would need to change them back to the original driver.

I suggest reverting to 2.2.4 to confirm that it really is 2.2.5 that has caused the issue - as opposed to something else that coincided with the update.

3 Likes
43

@jacobgraf

What are these devices?

Brennan’s Room Light Strip
Connor’s Room Christmas Lights
Basement Unfinished Workbench Light

44

Jepp, zigbee bulb drivers been F d up.

45

Sylvania Light Strip and 2 Innr Outlets.

46

There were no changes to the zigbee hub code in 2.2.5.
Any changes to drivers will not effect zigbee device network routing.
Having to pull batteries on zigbee devices to get them back on line is indicitave of existing routes back to the hub failing or are non existant.

2 Likes
47

The single most helpfull issue report to date...

12 Likes
48

Ok but outside of having to pull batteries on those devices. For example, I have fans with 3 bulbs in them. Since 2.2.5, a random bulb out of the 3 won’t turn on or sometimes won’t turn off. Also, if I cut power to some of my Sengled bulbs and then restore power later, the bulb comes on and then goes off immediately. If I do it again, it stays on. This behavior never happened before. Something is definitely up. No clue what though. I just noticed it all happening immediately after 2.2.5.

49

No known zigbee issues. C4 on 2.2.5.131. NO bulbs. No Zigbee 3.0 devices. (Jasco, Iris, Third Reality, & Ledvance, mostly)

50

This is why I think it would be useful if you reverted to 2.2.4 - something else could have coincided with the update. Eliminating (or implicating) 2.2.5 as the underlying cause would help fixing this.

3 Likes
51

The power restore section of the sengled drivers was updated in 2.2.5, we also included the 2.2.4 versions of the drivers in the latest hot fix for users wishing to have the old functionality.
The singled behaviour isn't related to the mesh issues you're having.

I agree to reverting to 2.2.4 as a test.

4 Likes
52

Ok just reverted back to 2.2.4.158. I'll keep you guys updated on how things are working.

5 Likes
53

2 posts were split to a new topic: Severe hub CPU load detected

55

Had exactly this behavior w/a Sengled bulb after changing to the new Advanced Zigbee drivers. Fixed it by setting the power restore behavior to "On" in the driver. Quick, simple fix for my case.

image

1 Like
56

With so many child devices, I would bet that it was the restarting of the zigbee radio that caused your issues. This could have caused devices to select new routes that aren’t compatible with having so many end devices and so few repeaters. I have some Sengled color plus bulbs in addition to 50 ish Sylvania rgbws on a C-5 hub with no issues using the Advanced Zigbee driver.

57

Hmm. I guess I thought 13 routing outlets was enough for my setup. How many do you propose I have in order to have the best chances of a reliable Zigbee network? Yes, I have been over the "How to setup a reliable Zigbee network" article. :slight_smile:

58

FYI - you have 15 routing devices. Not 13. As shown by the /hub/zigbee/getChildAndRouteInfo output that you posted above. One of them, the strip may not be a good router.

My rule of thumb has been one router/repeater for every 6-8 end-devices. So 15 routers should support between 90-120 end-devices.

Obviously if a particular router's routing table can only hold 2-3 devices that throws everything off.

Now, here's the kicker - I know everyone thinks highly of the Innr SP224 plug - that's why I bought four of them recently. The crazy thing is that my 4 plugs put together route for just 2 devices in a zigbee network with ~75 devices. In contrast my Tradfri repeaters and outlets serve as routers for 2-6 devices each.

59

Has anyone else noticed an issue with laggy updates from Alexa/Hue activity to HE?

I'm on 2.2.5.131 now, and I've only just noticed this behavior -- although I can't be sure it started with the update. Mainly curious if anyone has else has seen something like this:

I can operate my Hue bulbs perfectly from the HE dashboards, device pages, and/or any other HE-connected devices (like my z-wave VRCZ4s). But when I instead ask Alexa to turn them on or off, it does so quickly, yet HE doesn't "see" this activity for some period of time -- upwards of a minute or more, in some cases, though sometimes within a few seconds.

If I watch the logs while talking to Alexa, I can see that the activity doesn't appear until some indeterminate/random period elapses:

                         image

And of course, until it does, the whole rest of my HE/z-wave network is oblivious -- and then once it does, everything "resyncs" (including dashboards, the device pages, and the LEDs on the VRCZ4 buttons).

Anyone else?

60

Good to know, and may explain why he has so many child devices. I have 70ish end devices on my second hub with 5 Samsung and 3 Sylvania outlets and have 2 child devices.

61

That’s because Hue doesn’t push state changes to HE. HE has to poll for changes and I believe the default polling interval is 1 minute. Depending on where in the interval a change takes place will determine how long until devices on HE are updated. This is one of the reasons I disconnected Hue from Alexa and just have the bridge devices connected from HE to Alexa.