You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debug logs from herdsman show no response from the switch.
A local sniff shows that the switch is sending through a Philips Hue bulb which has a direct connection to the coordinator.
The sniff also shows the Hue bulb relaying the message to the coordinator.
Restarting zigbee2mqtt does not fix the issue.
However, reinserting the dongle in the USB extension cable to reset it does fix this issue! A sniff showed the route through the Hue bulb remained the same, and all devices kept the same short network IDs.
This has me thinking that the problem is in the coordinator firmware. It's hearing the message, but is never passing it back up to Herdsman.
This is clearly an issue that doesn't happen often, otherwise I'd expect to be seeing it daily with reports from other users. Is any way to do some sort of debug log from the coordinator itself? A way for it to pass up error information if it hits limits of some kind?
The text was updated successfully, but these errors were encountered:
I've had the following happen twice in the past few weeks that makes me think there is a bug in the 20240710 firmware. But, I'm stuck on next steps.
Environment
Symptoms
Debugging information
This has me thinking that the problem is in the coordinator firmware. It's hearing the message, but is never passing it back up to Herdsman.
This is clearly an issue that doesn't happen often, otherwise I'd expect to be seeing it daily with reports from other users. Is any way to do some sort of debug log from the coordinator itself? A way for it to pass up error information if it hits limits of some kind?
The text was updated successfully, but these errors were encountered: