-
-
Notifications
You must be signed in to change notification settings - Fork 71
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] Support for the new Z2M Symfonisk mode #103
Comments
Hi @mvjt Thank you for your question. ControllerX is not affected by the debounce mode from z2m, it just needs the action form the sensor or from the MQTT. This means you can already benefit from the new debounce mode, however, user is the one that will need to change the z2m configuration to make this happen.
The first z2m integration was done with the HA sensors for simplicity. However, ControllerX is now also able to connect to MQTT and skip the HA state machine, I have this in my current setup and I noticed a significant speed difference. You will need to change your integration from z2m to mqtt. You can read more about it in here. Thanks, |
Thanks @xaviml, I believe the action names has changed so I expected Controllerx needed update Single-click -> toggle BR Martin |
Hi @mvjt, Thanks for the information. The code was already updated, but not the documentation, sorry for that. However, could you confirm that the stop rotation is Cheers, |
Hi @xaviml, Sorry it changed again before it hit dev branch. It is brightness_stop, NOT rotating_stop. |
I will change the documentation then, however, the code is updated to that already. Thanks :) |
Thanks @xaviml , I also tested it it works perfectly... Thanks |
Documentation has been updated with this information: https://xaviml.github.io/controllerx/controllers/E1744 |
Question
Your project looks very useful. Thank you!
Are you planning to implement the new Symfonisk debounce mode of Z2M (legacy=false)?
Additional information
https://www.zigbee2mqtt.io/devices/E1744.html#legacy-integration
This new mode (legacy=false) makes debounce work properly without flooding with MQTT messages and would make controllerx more efficient.
Essentially, it sends a message when rotation starts, and one when it stops. Instead of flooding with rotation events during rotation. Also, the debounce functionality did not work properly and this has been fixed with legacy: false...
(Sorry a second question)
Why is the Z2M integration depending on a route through Home Assistant ant not directly through MQTT? Wouldn´t this be quicker/smoother?
z2m
The text was updated successfully, but these errors were encountered: