-
Notifications
You must be signed in to change notification settings - Fork 0
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
Mode widget doesn't always trigger when selecting a mode #112
Comments
@anordvall Can you try this in the new version? I can't reproduce that behavior, but it might have been changed during the latest internal changes |
Hi @igorgladkov. I can still reproduce the same problem on 0.7.58. Anything I can do to help out with finding the root cause? |
@anordvall I'm actually re-reading your original post and I might understood it differently before.
|
|
In my case, when entering the house and the alarm signal tells me the alarm will go off in 20 seconds... I try to disable the alarm and nothing happens... To disable it then I first have to enable it (even though it is already enabled) and then disable it. Not good when you'r stressed because the alarm will go off any second :) |
Got it. Fixed for the next release. |
Many thanks :) |
Verified to work with the latest release. Thanks again! |
If Rotini doesn't know the current state of the Mode widget (happens all the time due to the problems with server updates not reaching the client) nothing happens when clicking on the specific mode in the widget.
For example:
If Rotini thinks AlarmMode == Off, while in fact AlarmMode == Perimeter alarm, then I would expect that when clicking on the Mode widget and selecting Off, Rotini should always trigger an event so the alarm is in fact turned off. It should not depend on some client-side state.
The text was updated successfully, but these errors were encountered: