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

Armed Status #27

Open
djrobinsa opened this issue Jul 23, 2014 · 6 comments
Open

Armed Status #27

djrobinsa opened this issue Jul 23, 2014 · 6 comments

Comments

@djrobinsa
Copy link

Hey guys,

The Armed status still does change when arming the from the page ?

Any ideas ?

Used chrome as well as Safari

@gschrader
Copy link
Collaborator

Sorry can you provide a few more details or a screenshot of the issue.

@autumnwalker
Copy link

Looks like I am having the same issue. I have provided a screenshot below.

I used the API to disarm the alarm (/api/alarm/disarm) and it worked as expected. I tried to use the API to re-arm the alarm (/api/alarm/arm) and it did re-arm according to the Envisalink 3 status page, but as you can see from my screenshot the partition status on the alarm server page is showing "ready" and appears to not receive the "armed mode away" communication from Envisalink.

alarm_status

@autumnwalker
Copy link

Related: #21

@gschrader
Copy link
Collaborator

My memory might be wrong but that image is for the partition status not for the armed status.

@autumnwalker
Copy link

If that is the case, shouldn't it show that the main partition is "not ready" when it is armed? The physical panel does not indicate ready when armed.

@juggie
Copy link
Owner

juggie commented Feb 21, 2016

This was a bug in envisalinkdefs.py such that the handler for code: 652 (which was presented when you changed state from disarmed -> armed) did not properly set ready: False. It's fixed in my new branch (feature/tornado). You'll need python tornado installed, see here http://www.tornadoweb.org/en/stable/ if you are not familiar with how to install python modules.

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

4 participants