-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about integration with zigbee2mqtt #17
Comments
so far I have done so: But, I need an independent LED, but I’m silent about the tape :) |
Send "{"led":"toggle"}" (or on/off instead of toggle) to your "set" topic. For the WS2812 tape use {"light_color":"..."} for the "set" topic.
Its compatible with nodered's colorpicker. |
'Error: Cluster 'genOnOff' has no command '{led:on}' Cluster 'genOnOff' -- is right target? |
i'm use "openHAB2" for tests |
Error: Cluster 'genOnOff' has no command ' "{"led":"toggle"}" |
Cluster 'genOnOff' is only used for the relais. |
o lala! wonderwork ... :)
|
It turned out the following:
|
I have the same problem. I want to expose the color picker in zigbee2mqtt by adding e.light_brightness_colorxy(), but when I use it nothing happens. The firmware doesn’t call the “MoveToColor” callback. hope someone can help us. |
So far, all my attempts to manage have not been completely successful. Where can I find out what exactly to send to the topic "mqtt", to control the LED and WS2812 tape.
While I control only the relay, sending to the topic 'zigbee2mqtt/ZigUP1/set' <- ON or OFF.
I see pulses on the oscilloscope at the output of turning the polarized relay on or off. It's good.
But attempts to send to ".../set/led" lead to errors in zigbee2mqtt, but simply to "set" do not give a result.
There is no information and can not find - how to.
I ask for help.
Thanks.
The text was updated successfully, but these errors were encountered: