puijken

Rolling back to zigbee2mqtt 1.34 fixes the issue .. so it's for sure related to the new release. Support was added for "unsupported" devices to have basic functionality working even...

> > Rolling back to zigbee2mqtt 1.34 fixes the issue .. so it's for sure related to the new release. Support was added for "unsupported" devices to have basic functionality...

> Hey, > > same issue for me. I was on v1.9 and upgraded to 1.9.2. Why are you on 1.34? I can even select this in the child bridge...

You can remove it from the "cached accessories" Homebridge GUI -> 3 dots at the top right -> Homebridge Settings -> Remove Single Cached Accessory (almost at the bottom of...

For me the "workaround" of @Veldkornet seemed to work -> https://github.com/itavero/homebridge-z2m/issues/794#issuecomment-1873518037  I'm back on Z2M 1.35.0 but with the "Coordinator" device exluded in the homebridge-z2m plugin in homebridge. EDIT:...

Was just able to update a HUE DIMMER (324131092621) via zigbee2mqtt. Steps followed: 1. Force remove device from z2m 2. Reset device with paper clip 3. Rejoin device to z2m...

> Unrealistic to me because I have > 10 of those remotes and it would take days, and I would have to remap every automation, group, etc...that these entities belong...

No .. did not work .. same error again: _MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"id":"0x0017880108f1bcce","transaction":"21m3s-4"},"meta":{"device":"0x0017880108f1bcce","from":{"dateCode":"20160302","softwareBuildID":"5.45.1.17846"},"status":"update_succeeded","to":{"dateCode":"20160302","softwareBuildID":"5.45.1.17846"}},"type":"ota_update"}'_ Guess I was lucky the first time. Message of the first dimmer: _Zigbee2MQTT:info 2022-01-03 14:44:40:...

Same issue on Debian 12 when trying to build a snapraid package.