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

Splitting dimmers into two mqtt objects #20

Open
labanx opened this issue Feb 25, 2017 · 3 comments
Open

Splitting dimmers into two mqtt objects #20

labanx opened this issue Feb 25, 2017 · 3 comments

Comments

@labanx
Copy link

labanx commented Feb 25, 2017

Currently dimmers are exposed with both on/off and dimmer level on the same attribute.
Looking at other solutions they split these two objects into two groups.

Example
server/room/Dimmer/switch (on/off)
server/room/Dimmer/level (dim level)

Might it be beneficial to use an similar approach? Making the mqtt plugin more friendly for other systems.

@Edubits
Copy link
Owner

Edubits commented Feb 25, 2017

Thanks for your feedback @labanx. Could you give some examples of the other systems you are referring to?

@labanx
Copy link
Author

labanx commented Feb 25, 2017

Example on platforms that expects this behaviour.
https://home-assistant.io/components/light.mqtt/

Not directly an an dimmer example, but RGB uses the same approach
https://github.com/mertenats/open-home-automation/tree/master/ha_mqtt_rgb_light

https://github.com/cblomart/zwaymqtt
Seems to expose both switch and dimmer

Again not dimmer, but two datapoints
http://wetwa.re/?p=154

Exposes both binary and "dimming" on z-wave wallmote

@Edubits thanks for the quick response

@pastukhov
Copy link
Contributor

There is more complex convention about home automation and mqtt https://github.com/homieiot/convention

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants