-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Сhanges in the control structure of switch topics Xiaomi QBKG03LM and QBKG04LM #2356
Comments
I'm not aware of any changes regarding this in 1.7, at least it wss not covered by the tests or documented. However when publishing to |
I would like to change the parameter that is returned in json response format from the device. This greatly simplifies the work of setting up and integrating equipment. Now we change one parameter, and in the answer we get another I propose to make it possible to control through {"state_left": "OFF"} {"state_right": "OFF"} in addition to the existing one |
AFAIK if you publish |
Yes this would indeed be more logical but for now it has not been implemented. |
Сan you expect in the near future? It seems there’s nothing much to add to the need :-) everything is simple. |
Implemented! (in latest dev branch). |
Thanks, similar problem with LLKZMK11LM relay. |
Hey. QBKG03LM switches could previously be controlled through the topics
zigbee2mqtt/0x00158d00022bc3ab/left/set by sending the payload {"state_left": "OFF"} and zigbee2mqtt/0x00158d00022bc3ab/right/set by sending the payload {"state_left": "OFF"}.
Everything worked well. But after updating to version 1.7.0 the management topics changed. Now you can control it only by sending zigbee2mqtt/0x00158d00022bc3ab/right/set by sending the payload {"state": "OFF"}. I have already adapted the code and control methods when the result of the command corresponds to the command being sent. I do not like that sending the state parameter I see the result in the state_right topic. Can I add an old control option in addition to the existing one?
The text was updated successfully, but these errors were encountered: