Fixed fls-m from dresden-elektronik #11078
Conversation
| const e = exposes.presets; | ||
|
|
||
| const tzLocal = { | ||
| flsm_color_hs: { |
There was a problem hiding this comment.
Why not use
instead?There was a problem hiding this comment.
Because when using tz.light_color the device did not change color. I had to build this custom solution for the device to accept color changes.
There was a problem hiding this comment.
I think because it doesn't support x/y, can you try with just h/s: m.light({endpointNames: ["l1", "l2", "l3", "l4", "l5"], color: {modes: ["hs"]}})
There was a problem hiding this comment.
The challenge with this product is that the endpoints are dynamic. The device has DIP switches that configure which endpoint is exposed. As far as I understand, the extend field and the m.light function are static, so I had to work around this using the exposes and configure fields. In the end, this worked perfectly and corrected the previous “simple” implementation, which was incomplete (it only exposed five static lights, but the actual behavior depends on the DIP switch configuration).
There was a problem hiding this comment.
Maybe there is a different way to implement this? I am new to zigbee2MQTT.
There was a problem hiding this comment.
Yes we can identify using fingerprint (so a different definition is used for every mode): example:
2 participants
No description provided.