C7 Zigbee Devices non-responsive after 2.2.3.148 to 2.2.4.148 update

🛎️ Get Help
1

I have just over a dozen or so ZigBee controllable items (Switch's, outlets, fan controllers, plugs). Everything was working fine yesterday on 2.2.3.148, yesterday evening I updated to 2.2.4.148 and everything appeared to work fine.

Went to bed, everything seemed fine. Woke up this morning and headed to work, came home, and none of my zigbee devices seem to be working. Nothing has changed with my setup, hub is in a decently vented area.

I've tried the basics:
Zigbee radio is enabled.
Toggled radio enabled/disabled/enabled.
Rebooted hub
Shutdown hub for 15 min, rebooted

Still non functional. I went to ZigBee and viewed the logs while trying to turn on/off. Of a dozen devices, the only reports I got was:

Porch sofa peanut2020-11-28 21:11:05.855 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-65
Porch sofa peanut2020-11-28 21:11:05.851 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-65
Porch sofa peanut2020-11-28 21:11:05.749 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-65
Peanut Kitchen2020-11-28 21:10:50.451 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-52
Peanut Kitchen2020-11-28 21:10:48.816 profileId:0x0, clusterId:0x8004, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-52

3

Curious, all your listed devices are Peanuts. Do you have non Peanuts not working as well?

You also might try:

Basically,  **Peanut**  Plug is a  **ZigBee**  device and if it stops working, it needs to be  **reset** . 
Please unplug and plug the  **Peanut**  device back. Once it is done, press and hold the pairing 
button (which is right next to on/off button) for 8-10 seconds.
4

I have some motion sensors, contact sensors, and hampton fan controllers that are Zigbee, that are also not responsive, its just that the Peanut's are some of the devices that I can "Control" remotely and see if it shows up in the logs with anything.

I've tested the contact sensors and motion and they all seem "stuck" on whatever their last status was. Its as if the entirety of my zigbee network has imploded.

Just for kicks, I grabbed two peanut plugs, 1 currently in use, and one still in box. I reset the one in use and tried to join it to hubitat, and no results from the hub.

Tried the same with the BNIB one, and nothing, zigbee still cant find the device.

5

That's not fun :frowning:
I've had good luck with Zigbee but I didn't jump from 2.2.3 to 2.2.4. Its my understanding you cannot go back from 2.2.4 so you should contact @bobbyd for support.

John

6

So, the plot thickens. It looks like basically anything that's hardwired zigbee has come back online, late last night / early this morning. I woke up to find my ceiling fan light on, and that's zigbee.

Still nothing from battery operated motion or contact sensors.

I've DM'd @bobbyd but haven't heard back yet.

7

Sorry for the delays. Long weekends bring an influx of inquiries because folks have time to set up new apps and devices. I do have a reminder set up for your PM and I hope to review it as soon as possible.

1 Like
8

No worries, that's what I figured. I've actually got an update to my post today. Looks like I was mistaken on the stability of my wired zigbee, there not back to working normally. They are working better, but not normal by far.

Looks like the instability continues, I sent commands to some devices and it looks like zigbee has died again. Most of my hardwired devices are no longer responding. The ones that are it takes 3-4 send of the same command to respond, and their states never update.

Part of me thinks this is the "peanut" issue that's been covered before, but why would it pop up now, on a firmware update when everything has been rock solid stable for the last several months.

I've turned on debugging for my peanut plugs, and see an entry like this occasionally, but not continuously.

descMap:[raw:catchall: 0000 8038 00 00 0040 00 7AFD 00 00 0000 00 00 000000F8FF0716000F0010B4B6B3BEDABABDD8DDDED3B7B7BBBAB3, profileId:0000, clusterId:8038, clusterInt:32824, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7AFD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00, 00, F8, FF, 07, 16, 00, 0F, 00, 10, B4, B6, B3, BE, DA, BA, BD, D8, DD, DE, D3, B7, B7, BB, BA, B3]]

1 Like