Ubisys C4 - Commands not correctly sent to coordinator #7669
Comments
chris-1243
added a commit
to chris-1243/zigbee-herdsman-converters
that referenced
this issue
Sep 10, 2024
It is a following of Koenkk#7669. I did not want to modify legacy.fz.ubisys_c4. It seems something is not working and I have the feeling it would be better to use what is already created.
Merged
Koenkk
added a commit
that referenced
this issue
Sep 11, 2024
* Update ubisys.ts It is a following of #7669. I did not want to modify legacy.fz.ubisys_c4. It seems something is not working and I have the feeling it would be better to use what is already created. * Update ubisys.ts * Update ubisys.ts * Update ubisys.ts * lint --------- Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some commands like
brightness_move_down_s_orbrightness_stop_s_are not read by the coordinator. After spending some time in the converter, the C4 is the only device from Ubisys using thelegacy.fz.ubisys.infromZigbee. All other devices are using the "standard"fromZigbeelikefz.command_moveorfz.command_stop.I played with an external converter and the
brightness_movecommands are correctly read by the coordinator while using the nonlegacy.fz.ubisys.The text was updated successfully, but these errors were encountered: