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

next_mode and previous_mode should update based on known state #169

Closed
servim opened this issue Nov 25, 2017 · 5 comments
Closed

next_mode and previous_mode should update based on known state #169

servim opened this issue Nov 25, 2017 · 5 comments
Labels

Comments

@servim
Copy link

servim commented Nov 25, 2017

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:
1

Command: previous_mode, changes mode 15,2,1,0,15,2,1,0 etc
2

Is this expected behavior?

@sidoh
Copy link
Owner

sidoh commented Nov 25, 2017

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.

@sidoh sidoh added the bug label Nov 25, 2017
@sidoh sidoh changed the title next_mode and previous_mode next_mode and previous_mode should update based on known state Nov 25, 2017
@servim
Copy link
Author

servim commented Nov 25, 2017

the question is not the topic:
Command: mode_speed_up and mode_speed_down, works, but it is not clear, the current state, what is the range from the minimum to the maximum? mosquito does not return status.

@sidoh
Copy link
Owner

sidoh commented Nov 25, 2017

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.

@servim
Copy link
Author

servim commented Nov 25, 2017

Thank you! I thought so :(

@sidoh sidoh mentioned this issue May 4, 2018
@sidoh
Copy link
Owner

sidoh commented Jul 29, 2018

was added in 1.7

@sidoh sidoh closed this as completed Jul 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants