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

Mode widget doesn't always trigger when selecting a mode #112

Closed
anordvall opened this issue May 21, 2016 · 8 comments
Closed

Mode widget doesn't always trigger when selecting a mode #112

anordvall opened this issue May 21, 2016 · 8 comments
Labels
Milestone

Comments

@anordvall
Copy link

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:

        Frame label="{widget:mode}" {
            Text label="{item:pin} [FtbrnEv2SK635YTnuTs1232oRZb+Jb0P3EOL1fLlVOc]"
            Selection item=AlarmMode mappings=[
                0="Off {icon:unsecure}",
                1="Perimeter alarm {icon:secure}"
            ]
        }

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.

@igorgladkov
Copy link
Owner

@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

@anordvall
Copy link
Author

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?

@igorgladkov
Copy link
Owner

@anordvall I'm actually re-reading your original post and I might understood it differently before.
Is this only a problem when in the app you tap on already highlighted mode?
So for example do you still have a problem in this case:

  • server has state "mode1"
  • the app has state "mode2"
    Then, either:
  • you select "mode3" in the popup - does this work for you?
  • you select "mode2" in the popup - this does not work, correct?

@anordvall
Copy link
Author

•you select "mode3" in the popup - does this work for you?

  • Yes that works

•you select "mode2" in the popup - this does not work, correct?

  • You'r right. This does not work.

@anordvall
Copy link
Author

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

@igorgladkov igorgladkov added this to the 0.7.59 milestone Jun 12, 2016
@igorgladkov
Copy link
Owner

Got it. Fixed for the next release.

@anordvall
Copy link
Author

Many thanks :)

@anordvall
Copy link
Author

Verified to work with the latest release. Thanks again!

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