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

Second Area always in a ready State #13

Open
halldave opened this issue Feb 10, 2021 · 6 comments
Open

Second Area always in a ready State #13

halldave opened this issue Feb 10, 2021 · 6 comments
Labels
bug Something isn't working

Comments

@halldave
Copy link

Hi Chris,

I have been doing extensive testing of the Ultrasync app and I'm very happy with the whole experience. All states report correctly for each Zone,

Issue: Second Area always in a ready State

however I have two Zones that are associated with area2, (eg Large and Small Garage door reeds), and Area 2 is always showing a status of "Ready".

I opened either or both of the zones, and in the app state is "Ready"

However if I log directly into the web server, this shows Area 2 "Not Ready"

I also use UltraConnect as an APP on the Phone and that shows Area 2 not ready as well.

regards
David

@caronc caronc transferred this issue from caronc/ha-ultrasync Feb 10, 2021
@caronc
Copy link
Owner

caronc commented Feb 10, 2021

Thanks for the report. You're not the first one to bring this to my attention, but making an GitHub issue was a good idea so I won't forget this time to look deeper into the matter.

Would you be able to trip one of your Area 2 Sensors (keep it tripped... so maybe you could prop a door or stay in front of a motion sensor). During this state (When you know Area 2 should not be in a Ready state, can you capture a --debug-dump?

Are you familiar with the command line tool at all? Let me know if you need some more detailed instructions on how to do this.

Keep me posted

Chris

@halldave
Copy link
Author

halldave commented Feb 10, 2021 via email

@caronc
Copy link
Owner

caronc commented Feb 10, 2021

There is no rush, I may not be able to have a look at it until the weekend anyway. 🙂

@caronc caronc added the bug Something isn't working label Feb 28, 2021
@caronc
Copy link
Owner

caronc commented Sep 20, 2021

I just wanted to follow up on this issue as it's been some time. Would you be able to capture me a --debug-dump of your Area 2 status... it would be really good if you could capture me 2 dumps...:

  1. when everything is working great (Alarm panel is in a Ready state
  2. when at least one sensor is tripped (in Area 2) putting your Panel in a Not Ready state

it would allow me to debug your issue

@halldave
Copy link
Author

halldave commented Sep 20, 2021 via email

@tsuite
Copy link

tsuite commented Apr 29, 2023

I think I have some more information on this, I got here via https://github.com/flareman/homebridge-caddx-interlogix and was also having issues with Area 2 on my Hills R12 ComNav (CN_0.106-j).

After some digging, I think it's related this: https://github.com/caronc/ultrasync/blob/master/ultrasync/main.py#L753

Basically, I'm seeing a single areaSequence byte and the chunk of 17 bank states represents areas 1-8. _areas() and process_areas() appears to decode this correctly but in https://github.com/caronc/ultrasync/blob/master/ultrasync/main.py#L2398 , since a_seq contains a single byte, area_status_update() is executed on Area 1 (which updates) but not on Area 2.

user/area.htm (Area 2 armed, Area 1 and Area 2 ready; both Areas decoded correctly):

var areaStates = new Array("Armed Away", "Armed Stay", "Ready","Fire Alarm","Burg Alarm","Panic Alarm","Medical Alarm","Exit Delay"
		,"Exit Delay 2","Entry Delay","Zone Bypass","Zone Trouble","Zone Tamper","Zone Low Battery","Zone Supervision","");

	var areaNames = new Array("","","!","!","!","!","!","!");
	var areaSequence = new Array(38);
	var areaStatus = new Array(2,0,3,0,0,0,0,0,0,0,0,0,0,0,0,0,0); 

status.xml (Area 2 armed, Area 1 and Area 2 ready; only Area 1 gets updated):

<response>
  <abank>0</abank>
  <aseq>91</aseq>
  <stat0>2</stat0>
  <stat1>0</stat1>
  <stat2>3</stat2>
  <stat3>0</stat3>
  <stat4>0</stat4>
  <stat5>0</stat5>
  <stat6>0</stat6>
  <stat7>0</stat7>
  <stat8>0</stat8>
  <stat9>0</stat9>
  <stat10>0</stat10>
  <stat11>0</stat11>
  <stat12>0</stat12>
  <stat13>0</stat13>
  <stat14>0</stat14>
  <stat15>0</stat15>
  <stat16>0</stat16>
  <sysflt>No System Faults</sysflt>
 </response>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants