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
describe the problem in Detail. What do you expect to happen ? What does happen ?
Hello,
i updated the Zigbee Adapter from 1.10.3 to 1.10.13.
Then my devices, recognized as PTM 215.z stopped working. They are shown as available, but no acrtons are transmitted.
The devices are: https://www.led-trading.de/zigbee-unterputz-modul-fuer-friends-of-hue
I think that the Problem is described here, too: Koenkk/zigbee2mqtt#23814
So it could be fixed by the setting: legacy_triggers: true
But i dont know where to find it.
Best regards
Crabang
Adapter version
1.10.13
Coordinator firmware version
0-0.38.114.0
Coordinator
Conbee 2
Setup
Docker on Unraid
Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections
No response
The text was updated successfully, but these errors were encountered:
I am afraid that at this moment there is no access to the legacy_triggers settings. This will be a bigger change which will take time to get introduced.
describe the problem in Detail. What do you expect to happen ? What does happen ?
Hello,
i updated the Zigbee Adapter from 1.10.3 to 1.10.13.
Then my devices, recognized as PTM 215.z stopped working. They are shown as available, but no acrtons are transmitted.
The devices are: https://www.led-trading.de/zigbee-unterputz-modul-fuer-friends-of-hue
I think that the Problem is described here, too: Koenkk/zigbee2mqtt#23814
So it could be fixed by the setting: legacy_triggers: true
But i dont know where to find it.
Best regards
Crabang
Adapter version
1.10.13
Coordinator firmware version
0-0.38.114.0
Coordinator
Conbee 2
Setup
Docker on Unraid
Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections
No response
The text was updated successfully, but these errors were encountered: