Multiple Zigbee devices stopped reporting events after late November

I’m running a Hubitat C‑8 Pro on the latest firmware. Up until late November, my Zigbee devices were working fine. Since then, multiple devices across my home have stopped reporting events, including:

  • Philips Hue SML001 motion/temperature/illuminance sensors (several throughout the house)
  • SmartThings motion sensor
  • A 12V Zigbee dimmer used for my bird’s light

Troubleshooting already attempted:

  • Searched the Hubitat Community forums for similar issues and tried suggested fixes
  • Rebooted the hub multiple times
  • Disabled Zigbee for more than 30 seconds, then re‑enabled it
  • Re‑paired devices without deleting them (hub reported “previously joined device reconnected”)
  • Factory reset and clean re‑pair on at least one sensor
  • Replaced batteries in all sensors
  • Switched between built‑in drivers (Hue Motion Sensor, Generic Zigbee Motion Sensor, etc.) and clicked Configure each time
  • Confirmed hub is on the latest firmware

Current behavior:

  • Devices still appear in the Zigbee graph
  • Debug logs show raw “catchall” traffic, so the hub is receiving packets
  • No new motion/illuminance/temperature events appear in the Events tab
  • LEDs on the sensors flash when motion is detected, so the hardware seems fine
  • Only one bathroom sensor continues to report normally — all others stopped around late November

This appears to be a hub‑side Zigbee issue with bindings or driver parsing, since multiple unrelated devices stopped at the same time. Please advise on next steps or provide guidance on resolving this issue.

I’m running a Hubitat C‑8 Pro on the latest firmware. Up until late November, my Zigbee devices were working fine. Since then, multiple devices across my home have stopped reporting events, including:

  • Philips Hue SML001 motion/temperature/illuminance sensors (several throughout the house)
  • SmartThings motion sensor
  • A 12V Zigbee dimmer used for my bird’s light

Troubleshooting already attempted:

  • Searched the Hubitat Community forums for similar issues and tried suggested fixes
  • Rebooted the hub multiple times
  • Disabled Zigbee for more than 30 seconds, then re‑enabled it
  • Re‑paired devices without deleting them (hub reported “previously joined device reconnected”)
  • Factory reset and clean re‑pair on at least one sensor
  • Replaced batteries in all sensors
  • Switched between built‑in drivers (Hue Motion Sensor, Generic Zigbee Motion Sensor, etc.) and clicked Configure each time
  • Confirmed hub is on the latest firmware

Current behavior:

  • Some Devices still appear in the Zigbee graph - but not always
  • Debug logs show raw “catchall” traffic, so the hub is receiving packets
  • No new motion/illuminance/temperature events appear in the Events tab
  • LEDs on the sensors flash when motion is detected, so the hardware seems fine
  • Only one bathroom sensor continues to report normally — all others stopped around late November

This appears to be a hub‑side Zigbee issue with bindings or driver parsing, since multiple unrelated devices stopped at the same time. Please advise on next steps or provide guidance on resolving this issue.

Thank you in advance for your help. I'm so frustrated I'm about to just go all zwave and say forget zigbee. That or just move to a different platform, although up until this, I've liked Hubitat.

Please post a screenshot of these raw “catchall” Zigbee messages; this may give us a clue as to what is going wrong.

1 Like

Please give us the exact firmware, "latest" could be about anything. And for future readers who might have a similar problem, it gives a frame of reference if it turns out to be a bug that gets fixed.

Rebooted, or did a shutdown and power cycle? Pull the plug at the wall and wait a minute or so. The radios don't reset upon reboot, only a full power cycle.

Can you tell us what channel Zigbee is on? Did you try a different channel?

What power level are you on? Did you change it at all?

Did you try a Zigbee rebuild? Did you try a Zigbee Reboot? (both on the Zigbee Settings Page)

Any Zigbee devices that are giving a very high number of messages compared to other devices? (sort the right column to see most to least)

4 Likes

I had a zigbee device fail about a year ago and it caused all kinds of havoc on my zigbee network. I'm gonna guess you have the same issue. The Zigbee Device graph on the Zigbee Details page really helped me track it down. Look for the devices you are having trouble with and see if they are all repeating via the same device. If so that may be your bad one.

2 Likes

Thank you for the help. Attached is the log since I enabled debug logging on one of the devices.

Thanks for pointing that out — I’m on firmware version 2.4.3.167.

Rebooted. I also unplugged, but didn't wait two minutes.

Was on 20, currently is on 24.

Yes. changed it from 20 to 24.

12

No - It was working fine before and nothing has changed. Hubitat and sensors are in the same location. Moving the sensor closer to the hubitat does not have it start working. It is receiving data from the sensor, it just is not receiving actual events.

yes

yes

Yes, and that is the only one that is actually working though. It's also not a new device.

The screenshot is unreadable — it’s far too low-resolution (only 176 px wide).
The debug logs also appear to be repetitive, so there’s no need for a full scrolling capture.

Please either take a screenshot of just a single screen of logs, or copy and paste 10–15 consecutive debug log lines as text. That will be enough to analyze the issue.

Also, please add a screenshot of the same device Info tab , where the Zigbee model/manufacturer and the driver used can be seen.

The image I uploaded was originally clear, but I didn’t know the system downgraded resolution. That’s why the text couldn’t be made out. I hope this version works better. It would be ideal if you could just attach the log but they only allow images :frowning:

1 Like

More proof to suggest it is an issue with Hubitat. :frowning: I suspect a firmware upgrade broke me some time back and it took me a while to realize it. I just removed one of the Philips Hue multisensors and then re-added it. That sensor is now working correctly again. :man_facepalming: The others though are still not working correctly. This is rather annoying as I need to remove the device from my apps first, and then add them back in and set them back up with the settings I had. :frowning:

I don't know about that. I think about what @tivomaniac said about a problem device causing their issue.

You answered @neonturbo you have a device with high number of messages.

I would suspect that device, especially if it is old and it is a repeater.

The device you re-paired could have started working because it found a new route that didn't involve your problem device.

2 Likes

I was checking the route when it would appear in the graph. It would always show a route directly to the hub and not to anything else. The device that was working that also had a high number, wasn't an old device. Bought this year in 2025 and installed some time ago, months before everything stopped working.

I went through the hassle of removing my Zigbee devices and re‑adding them. They are all working correctly now. That said, I’ve run into two new issues:

  1. Broken Rule Action I have a rule that referenced one of the Zigbee devices multiple times. After re‑adding, those entries now just show **BrokenAction**. Is there any way to view the original rule info before it broke (maybe in raw XML or another format) so I can recreate the actions?
  2. Philips Hue Multisensor Pairing Problem I have two brand‑new Philips Hue multisensors (the newer style with the button on the back instead of the pinhole). When I try to add them, the hub shows Found a Zigbee device, initializing... but never goes further.
  • I’ve reset the sensors.
  • Tried “Pair while avoiding Zigbee 3.0 repeaters.”
  • Tried “Pair while exchanging keys in clear.”
  • Tried the normal pairing method.
  • Each attempt has been repeated multiple times.

Despite all that, they won’t complete pairing. Any guidance on how to get these new Hue sensors working would be appreciated.

1 Like

Thank you for the logs. These 'ZDO Match Descriptor' broadcasts received once every 30 minutes are usually harmless, they are probably sent from a router/repeater in your Zigbee network. So this is not a problem.

You should not have removed your Zigbee devices, it is enough to pair them again to your hub (without deleting). Unlike Z-wave, there is not need to exclude an already paired device, next time you re-pair it without removing it first it will be recognized as the same device, so there will be no broken rules or other automations.

Use this pairing method for the rest of the devices that won't complete pairing.

I had tried repairing without removing first. That was not working. The only thing that worked was removing the entire device and adding it back.

Thank you for taking the time to look. I tried the steps you outlined for adding the new Philips Hue multi-sensors, but unfortunately they didn’t work. I also tried navigating away from the page and back to it multiple times, but the options remain greyed out. It’s now stuck in this state, so I’m unable to retry (see attached screenshot).

You will need to reboot the C-8 hub, if the Zigbee interface has stuck in join mode

As a last idea for now - try pairing again (avoiding Zigbee repeaters option) immediately after the hub reboot.

Thank you. After it didn’t come back for some time, I went to get the screenshot and make the post. When I returned, the options were no longer greyed out. I tried again using the Pair while exchanging keys in clear option, but that didn’t work. I then repeated the process with the normal Start Zigbee pairing button, and to my surprise it worked. I was even able to add the second one the same way. Thank you!!!

1 Like

You also may want to add more Zigbee repeaters if your Hue motion sensors flash a light when they detect motion. The light only flashes when they aren’t connected to the hub. I very rarely see this happen with one of mine, and it always recovers without intervention, but way back before I had a solid zigbee mesh, this wasn’t the case, and was a bit maddening having to frequently rejoin the sensor.
The Zigbee Map app (by @dandanache) is much more informative than the built-in app, and will show you what signal quality your devices are actually receiving as reported by each device.

1 Like