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
next_mode and previous_mode should update based on known state #169
Comments
Ah, yes. This is not how it should work, but I see why it's doing this. Should be able to fix this in a future version. Thanks for reporting. |
the question is not the topic: |
There isn't a way to directly set speed. It can only be controlled with increase/decrease commands. Because of this it's tricky to know what speed the bulb is at. espMH doesn't currently track speed, but I believe the range is [0, 10]. It's possible to know what the state is by, for example, sending the maximum number of decrease commands. Then you know the device is at speed 0. |
Thank you! I thought so :( |
was added in 1.7 |
Hello! I'm not sure I can explain, my English is quite bad.
I have a light bulb RGBW, firmware 1.6.0
Command: next_mode it works, the mode changes from 0 to 8. But if the mode is changed through the mode: {"state":"ON","mode":"0"}, then this command will continue from the place where it finished, and not from the last mode. Eg:
Command: previous_mode, changes mode 15,2,1,0,15,2,1,0 etc
Is this expected behavior?
The text was updated successfully, but these errors were encountered: