Weird issues since 2.2.5 update (Zigbee)

jacobgraf · February 9, 2021, 3:57pm

Here is a fresh one while things seem to be working great...

Parent child parameters
EzspGetParentChildParametersResponse [childCount=18, 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]
No information for Child 6
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]

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

Route Table Entry
status:Unused
status:Active, age:64, routeRecordState:0, concentratorType:None, [Garage Door Lisa, 65D1] via [Jacobâ€™s Desk Routing Outlet, 7AB7]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Addisonâ€™s Room Motion Sensor, 16E5] via [Jacobâ€™s Desk Routing Outlet, 7AB7]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Ella's Closet Motion Sensor, DB41] via [Fireplace Fan, 19BD]
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, [Laundry Room Motion Sensor, 7951] via [Fireplace Fan, 19BD]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Upper Hallway Thermostat, 421E] via [Fireplace Fan, 19BD]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Office Desk Motion Sensor, 5DE8] via [Basement Unfinished Workbench Light, F957]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Garage Refrigerator, 8204] via [Jacobâ€™s Desk Routing Outlet, 7AB7]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Master Bedroom Closet Motion Sensor, FC27] via [Jacobâ€™s Desk Routing Outlet, 7AB7]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Garage Light 5, A5AE] via [Fireplace Fan, 19BD]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Ella's Bathroom Motion Sensor, 1B01] via [Upper Hallway Routing Outlet, 235B]
status:Unused
status:Active, age:64, routeRecordState:0, concentratorType:None, [Master Bedroom Dimmer Switch, D786] via [Basement Unfinished Workbench Light, F957]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Back Hallway Light 3, DB29] via [Jacobâ€™s Desk Routing Outlet, 7AB7]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Kitchen Sink Light, EE87] via [Ellaâ€™s Room Routing Outlet, ED24]

Tony · February 9, 2021, 8:39pm

The neighbor lists don't look much different (a couple more routers were being used in the 'before' configuration than the more recent one; a couple less devices are now showing as child devices of the hub meaning they found better parents elsewhere, assuming they aren't MIA). It's probably not possible to get much insight from just single 'before' and 'after' snapshots (a stable neighbor table implies a stable network, so keeping an eye on it periodically is a better way to judge).

Having said that, one thing that seems notable is that according to the previous route table entries, most of the route record requests (which indicate devices that are reachable 'via' a specific router) were handled by a single router (the 235B device) whereas in the later snapshot, three of the routers (19BD, 7AB7, and F957) were 'via's for more than one route entry.

But again, not having any feel for how stable the neighbor tables were before (or are now), there probably isn't too much that can concluded from this.

mpk · February 9, 2021, 8:56pm

Thanks, Ken -- I was afraid it might be a polling thing.

I used to have additional devices set up (especially from when I was initially on Smartthings, and then when I was running a bridged system between Smartthings and HE), but I recently removed them as I'd become tired of constantly re-encountering "duplicate" devices that would confuse Alexa. Seems like I solved that problem at the expense of this one.

I wonder if it might just be worth upping the polling frequency. Do you know where I'd find that?

mpk · February 9, 2021, 8:59pm

Thanks for this, dJOS. Where is this "respond immediately" option?

(Never mind -- found it here)

dJOS · February 9, 2021, 9:05pm

Under Apps, "Amazon Echo Skill" and it's the second option under the list of devices exposed to Alexa.

mpk · February 9, 2021, 9:23pm

Thanks -- checked, and it was already set (and it shouldn't really apply to Alexa-initiated actions anyway, I don't think?)

Can't seem to find "polling interval", though, per @Ken_Fraleigh (here) and @christiansandp (here)...

ogiewon · February 9, 2021, 9:33pm

In the Hubitat "Apps", open the "Hue Bridge Integeration" app, then click OPTIONS.

mpk · February 9, 2021, 9:50pm

Ah, thanks Dan -- had been looking at the device instead of the app.

Just installed CoCoHue, though, and I have to say it seems to be working brilliantly, updating the dashboards, device pages, and VRCZ4 LEDs instantly (even with default 1-minute polling).

bertabcd1234 · February 9, 2021, 9:56pm

Both CoCoHue and the built-in Hue Bridge integration should update device states immediately if the change was made from Hubitat, as long as Hubitat hears back from the Bridge without an HTTP error; it's outside changes, like those made from the Hue app (or other integrations that use it, like Alexa), that may take up to the polling interval to be reflected in Hubitat. Of course, if the built-in app isn't doing one or both of those (I've seen some people mention that the latter doesn't work for them, even when configured appropriately), I can't help with that but could if it's CoCoHue.

mpk · February 9, 2021, 9:59pm

Right -- it was always the Alexa-driven changes that I was trying to address. CoCoHue seems to be updating those immediately on the HE side...although I just noticed that operating the Hue bulbs via the Hue app does not update HE through CoCoHue.

Will have to investigate further, and let you know what I find.

Ken_Fraleigh · February 9, 2021, 10:09pm

I’ve been using CoCoHue since Robert’s first version and it’s been great, especially importing scenes into Hubitat. Instead of increasing the polling frequency and thus the load on the hub, I just share the lights from HE to Alexa.

Ken_Fraleigh · February 9, 2021, 10:12pm

Again this won’t update until polled.

mpk · February 9, 2021, 10:13pm

Understood...although it didn't even seem to update with polling? (Not sure why that would be, but there it is...)

Ken_Fraleigh · February 9, 2021, 10:15pm

Just disconnect the Alexa to Hue integration and use the HE to Alexa integration to share the bulbs with Alexa. Then it will be immediate.
Of course you will need to re add the Hue to the rooms in Alexa.

mpk · February 9, 2021, 10:23pm

I'm with you, Ken -- thanks!

erktrek · February 10, 2021, 8:51pm

So I wanted to report back - I don't know if this had any impact on my C-5 BUT in helping another member I temporarily re-enabled Z-Wave on my C-5 and paired a Z-Stick. Noticed a left over ghost device.

Wondering what impact this would have if the Z-Wave service was disabled... probably no impact but removed it anyway, rebooted and shutdown the ZW service again....

jacobgraf · February 18, 2021, 10:43pm

Well, everything was running smooth on 2.2.4 and I was feeling frisky, so I went back to 2.2.5. Surely it was just a fluke, right? Nope. My Zigbee network is once again trash. Argh!

lewis.heidrick · February 18, 2021, 11:03pm

What zigbee channel are you on currently?

jacobgraf · February 18, 2021, 11:14pm

20 I believe.

lewis.heidrick · February 18, 2021, 11:17pm

Can you bump it up to 25 to get it out of the channel 6 wifi lobe? It'll still be in the channel 11 lobe but not nearly as bad as being bombarded by both. Don't use 26 as it's not supported on all devices and has a restricted power output. The devices should go into panic mode and swap over within about 20 minutes or so.