Unreliable Zigbee Mesh on C-5 hub

Below is the data you requested. What does all this mean?

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

Child Data

Neighbor Table Entry
[Attic Light, 092C], LQI:249, age:1, inCost:3, outCost:1
[Master Bedroom Chandelier , 2AC3], LQI:254, age:4, inCost:1, outCost:1
[Second Bathroom Recessed Light, 2B09], LQI:253, age:4, inCost:3, outCost:1
[Sink Light, 4AE0], LQI:255, age:0, inCost:1, outCost:0
[Fireplace Lights, 677F], LQI:255, age:4, inCost:1, outCost:1
[Christmas Tree, A267], LQI:255, age:4, inCost:1, outCost:1
[Front Bedroom Light, A34C], LQI:255, age:4, inCost:1, outCost:1
[Master Bathroom Toilet Exhaust, A7B6], LQI:255, age:0, inCost:1, outCost:0
[Second Bathroom Exhaust Fan, AE2E], LQI:255, age:4, inCost:1, outCost:0
[Andy’s Owlet Plug, C5FB], LQI:255, age:1, inCost:1, outCost:0
[Outdoor Patio Light, D284], LQI:255, age:4, inCost:1, outCost:1
[Master Bedroom Recessed Light, D95E], LQI:253, age:4, inCost:3, outCost:1
[Hallway Light, F61A], LQI:255, age:4, inCost:1, outCost:1
[Kitchen Under Cabinet Lights, F6AE], LQI:254, age:4, inCost:1, outCost:1
[Kitchen Lights, FB09], LQI:254, age:4, inCost:1, outCost:1
[Hallway Nook, FCE4], LQI:255, age:1, inCost:1, outCost:0

Route Table Entry
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Second Bathroom Recessed Light, 2B09] via [Christmas Tree, A267]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Hallway Nook, FCE4] via [Hallway Light, F61A]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Kitchen Cabinet Light, B494] via [Attic Light, 092C]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Guest Bathroom Exhaust, 955B] via [Fireplace Lights, 677F]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Laundry Exhaust, EC42] via [Kitchen Under Cabinet Lights, F6AE]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Master Bedroom Chandelier , 2AC3] via [Master Bedroom Chandelier , 2AC3]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Kitchen Lights, FB09] via [Kitchen Lights, FB09]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Front Door Light, 79F7] via [Fireplace Lights, 677F]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Fireplace Lights, 677F] via [Fireplace Lights, 677F]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Guest Bathroom Light, 8E7F] via [Front Bedroom Light, A34C]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Second Bathroom Exhaust Fan, AE2E] via [Second Bathroom Exhaust Fan, AE2E]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Master Bedroom Recessed Light, D95E] via [Master Bedroom Recessed Light, D95E]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Laundry Light, 81B5] via [Kitchen Lights, FB09]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Outdoor Patio Light, D284] via [Outdoor Patio Light, D284]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Office Light, 616E] via [Kitchen Lights, FB09]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Dining Lights, C8A6] via [Outdoor Patio Light, D284]

From my understanding they are devices connected directly to the hub, and the devices that are connected to them. The LQI is what we're looking at. LQI of 255 is great signal. As that goes down, the signal strength is weaker.

I'm not sure what the route record state and concentrator type indicate though. I've never seen anything but 0, and concentratortype none in mine.

I have only seen this not be “0” with the Enbrighten dimmer I have. Mine also says “2” and “low ram” I find it interesting that none of the motion sensors show up in the table. I’m assuming it’s because his table is constantly changing as evidenced by the age 0 entries. It looks dominated by all the Enbrighten devices.

2 Likes

From my googlefu, a high ram concentrator stores all the routing information for the mesh to save on traffic. Low ram only stores some routing information.

I'm guessing my "none" are just that, dumb repeaters. Most of mine that show none are battery devices, but there are a couple outlets in the mix.

1 Like

Any other ideas to try?

@bobbyD any ideas?

I am still having issues. I noticed something odd. The parent and child is the same in the devices that are delayed. See Hallway Light, CC08

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

Child Data

Neighbor Table Entry
[Sink Light, 4AE0], LQI:254, age:3, inCost:1, outCost:1
[Guest Bathroom Light, 5083], LQI:254, age:4, inCost:1, outCost:1
[Christmas Tree, A267], LQI:255, age:4, inCost:1, outCost:1
[Front Door Light, ADEF], LQI:254, age:1, inCost:1, outCost:0
[Master Bedroom Recessed Light, B20A], LQI:255, age:2, inCost:1, outCost:0
[Second Bathroom Recessed Light, BF71], LQI:254, age:4, inCost:1, outCost:1
[Living Room Lights, BFB8], LQI:254, age:4, inCost:1, outCost:1
[Laundry Exhaust, C6B0], LQI:254, age:2, inCost:1, outCost:0
[Hallway Light, CC08], LQI:255, age:4, inCost:1, outCost:1
[Attic Light, D5D8], LQI:255, age:4, inCost:1, outCost:1
[Second Bathroom Exhaust Fan, DB45], LQI:255, age:3, inCost:1, outCost:1
[Kitchen Lights, ED13], LQI:255, age:4, inCost:1, outCost:1
[Front Bedroom Light, F402], LQI:254, age:4, inCost:1, outCost:1
[Kitchen Under Cabinet Lights, F6AE], LQI:255, age:3, inCost:1, outCost:1
[Outdoor Patio Light, F790], LQI:254, age:2, inCost:1, outCost:0
[Hallway Nook, FCE4], LQI:254, age:4, inCost:1, outCost:1

Route Table Entry
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Hallway Light, CC08] via [Hallway Light, CC08]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Guest Bathroom Light, 5083] via [Guest Bathroom Light, 5083]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Laundry Light, C698] via [Second Bathroom Recessed Light, BF71]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Kitchen Lights, ED13] via [Kitchen Lights, ED13]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Front Bedroom Light, F402] via [Front Bedroom Light, F402]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Outdoor Patio Light, F790] via [Kitchen Lights, ED13]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Garage Light, 8899] via [Hallway Light, CC08]
status:Active, age:32, routeRecordState:0, concentratorType:None, [Garage Motion Sensor New, 568D] via [Attic Light, D5D8]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Master Bedroom Chandelier , F653] via [Second Bathroom Recessed Light, BF71]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Office Light, 616E] via [Hallway Light, CC08]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Hallway Nook, FCE4] via [Hallway Nook, FCE4]
status:Active, age:0, routeRecordState:2, concentratorType:Low Ram, [Guest Bathroom Exhaust, 955B] via [Attic Light, D5D8]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Front Door Light, ADEF] via [Kitchen Lights, ED13]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Island Lights, A9C8] via [Guest Bathroom Light, 5083]
status:Active, age:32, routeRecordState:2, concentratorType:Low Ram, [Fireplace Lights, BF09] via [Sink Light, 4AE0]
status:Active, age:64, routeRecordState:2, concentratorType:Low Ram, [Living Room Lights, BFB8] via [Living Room Lights, BFB8]

@bobbyD any ideas? I did a reset of the Zigbee and re-added the devices, yet the problem persists.

It's always hard to troubleshoot mesh instability from afar without actually capturing data between the controller and respective devices. Narrowing down if the problem is related to device(s) going bad, weak mesh or radio interference is always challenging. At least you know that is not the controller (hub) because some devices are working. The issue could be with the hub if no devices are working.

1 Like

@bobbyD are there any tools I can use to do that? I’m not sure relocating the hub would fix anything since I’m getting slow responses from close devices as well as far. Is it possible that the hub is having issues?

Something (bad/misconfigured device) is spamming your mesh ......

this could also be an interference issue from wifi or another zigbee network using the same channel.

1 Like

I would check the Logs >> Hub Events tab to see if Zigbee radio goes offline. If it does, that may be indicative of a radio problem. If not, then I would screen your environment for 2.4 GHz band interference and/or individual devices going bad (I wouldn't worry about tools to sniff your network, the cost and effort doing so far exceeds the benefits. Eliminating bad/weak devices from the network is far more effective in the long run)

1 Like

I was fighting issues with one of my Zigbee thermostats becoming totally unresponsive even though it showed as connected to my C8 hub and that my hub showed it as connected. Other than it being unresponsive to device page commands and dashboard commands sent to it, nothing showed/indicated that it was offline.

On a hunch, I looked into WiFi and Zigbee interference and changed to a different Zigbee channel. Like magic, the thermostat instantly started working again. For the record I went from channel 25 to 15, so as not to conflict with WiFi access points on channels 6 and 11.

This may not be your issue, but you should seriously consider checking and possibly changing your Zigbee channel on your hub.

4 Likes

I don't see any errors in the hub and I don't see it going offline. I tried switching the channels. I've gone through a few channels: 11, 15, 20, 25 and none of them seem to make a difference. I'm not sure what else to try at this point.

For reference, I'm on channel 25 now.

Any other thoughts?

You have a very similar mix of Zigbee devices as I have on my production hub with the exception of the peanut plugs. I never had good experience running Zigbee on channel 25. I would bump it down to channel 20-24. Also, can you remove the peanut plug(s) from your environment at least temporarily, then Shut down your hub and unplug it for 30 min before plugging it back on?

Last but not least, one of your APs is on top of your Zigbee, any way you can change them to channel 1 & 6?

Ironically I did those:

  1. I removed all of my peanut plugs and replaced them with Innr Zigbee Smart Plugs. This was a few months ago.

  2. Yesterday I moved my Wifi APs to channel 1 and 6 so they're as far away as possible from channel 25. Here's what the wifi layout looks like. There's a lot of overlaps everywhere so I'm not sure what the ideal channel would be. I'll try changing the channel to 24.

ZigBee 15 would probably be your best bet, but I believe there are devices that may have issues there.

I don't have experience with those either, but assuming the lack of Zigbee incidents in environments that run those outlets, is a good indicator that they should be fine. However, your symptoms as described, point to weak devices/mesh, thus taking those out all together might be your next step.

What are the best ways to debug this mesh?

Thoughts? I posted some details here: