Do you guys have the binary sensor named binary_sensor.zigbee2mqtt_bridge_connection_state …?
And if so, does the status change when the adapter getting wonky??
Because if so, you can use that to trigger an automation, to restart zigbee2mqtt using the restart addon action.
I have tried that. It doesn’t work. I guess that when the bridge state changes, it’s too late. The only thing that works is PoE out/in.
Why not try to use the EFR32 radio for zigbee? The linked thread suggests that it’s more stable.
I guess that might be a solution. but the guide for moving it (16 point list, with plenty of room for failure) has scared me off so far.
Can you share a link to the guide for moving it? I’m at the end of my rope with this device, it is truly terrible. I’ve found that it fails 100% of the time when I try to do OTA updates of Zigbee device firmware. SMLight told me that it was a known issue with the chip that it chokes with a high message rate. They attributed that to something on my network and - as others have said - take no responsibility for the issue. But firmware updates are basically a high data rate stream and this makes the device fall over.
I’m using ZHA and I have scheduled reboots of the device but it isn’t enough to cope with the problem. I would not recommend anyone start using one of these devices if you aren’t already.
Here’s the link
Let me know if you can make it work.
I have been in contact with their support for weeks/months. I have also sent them a fairly extensive log from z2m documenting that there is not much traffic in my zigbee network.
I agree with you: users who hasn’t yet started using one of their (MR) adapters; Don’t do it.
I selected the MR4U mainly because it’s PoE and it combines Zigbee and Matter in one device. I guess I will have to look elsewhere.
Smlight’s support has been useless
