Skip to content
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

Closed
mvjt opened this issue Jul 23, 2020 · 7 comments
Closed

[QUESTION] Support for the new Z2M Symfonisk mode #103

mvjt opened this issue Jul 23, 2020 · 7 comments
Assignees
Labels
question Further information is requested

Comments

@mvjt
Copy link

mvjt commented Jul 23, 2020

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?

  • Devices involved:
    • IKEA Symfonisk E1744
    • Integration: Choose from z2m
@mvjt mvjt added the question Further information is requested label Jul 23, 2020
@xaviml
Copy link
Owner

xaviml commented Jul 27, 2020

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.

Why is the Z2M integration depending on a route through Home Assistant ant not directly through MQTT? Wouldn´t this be quicker/smoother?

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,

@mvjt
Copy link
Author

mvjt commented Jul 31, 2020

Thanks @xaviml, I believe the action names has changed so I expected Controllerx needed update

Single-click -> toggle
Double-click -> brightness_step_up
Triple-click -> brightness_step_down
Rotate-left -> brighness_move_down and when stop rotating rotating_stop
Rotate-right -> brightness_move_up and when stop rotating rotating_stop

BR

Martin

@xaviml
Copy link
Owner

xaviml commented Aug 2, 2020

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 rotating_stop and not brightness_stop as I have in the code?

Cheers,
Xavi M.

@mvjt
Copy link
Author

mvjt commented Aug 2, 2020

Hi @xaviml,

Sorry it changed again before it hit dev branch. It is brightness_stop, NOT rotating_stop.

@xaviml
Copy link
Owner

xaviml commented Aug 2, 2020

I will change the documentation then, however, the code is updated to that already.

Thanks :)

@mvjt
Copy link
Author

mvjt commented Aug 2, 2020

Thanks @xaviml , I also tested it it works perfectly...

Thanks

@xaviml
Copy link
Owner

xaviml commented Aug 17, 2020

Documentation has been updated with this information: https://xaviml.github.io/controllerx/controllers/E1744

@xaviml xaviml closed this as completed Aug 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants