Closed L2jLiga closed 4 months ago
Hi, thank you for your message. Can you please tell me what version of Matterbridge and what version of matterbridge-zigbee2mqtt and z2m are you using? This issue showed up when in z2m you have Legacy option active but of course it should cause any problem here. I thought the bag has been solved months ago... Maybe something new but I need the versions I asked you.
Hi, I'm using latest versions available as of now:
matterbridge: 1.2.12, matterbridge-zigbee2mqtt: 2.0.12 Zigbee2mqtt: 1.37.0 commit: 46f34c8
This issue showed up when in z2m you have Legacy option active
Hmm, you mean this one? I didn't even touch this settings, will try to disable
I've unchecked both and restart Z2M, error message still appearing =(
Ok thank you for your message. We found the bug! Will be fixed in the next release. If you want not to see it anymore now is easy: remove all retained messages from your MQTT broker for devices you don't have anymore. z2m doesn't remove retained messages when you remove a device. So they stay there forever and are sent every connections.
Thanks for your help.
Ok thank you for your message. We found the bug! Will be fixed in the next release. If you want not to see it anymore now is easy: remove all retained messages from your MQTT broker for devices you don't have anymore. z2m doesn't remove retained messages when you remove a device. So they stay there forever and are sent every connections.
Thanks, will try 🙂
I'm not really sure if it somehow related to availability feature in Z2M, but I see in logs:
stacktrace: