Hi io_guy,

 

Thanks for the update!  I'm seeing zones that get tripped never resetting their status in ISY - they continue to show as 'open' indefinitely.  I turned on verbose ISY and device logging, and (hopefully) grabbed the relevant part below.  In this case, I see z21 getting set to 1, but never getting reset to 0 after the partition returns to 'ready to arm'.  Let me know if you need more.  

 

Thanks as always for all your work!!

Chris

2016-09-07 09:39:27 - TCP: Data Received - 76 Bytes [hwalrm1]
2016-09-07 09:39:27 - TCP: %02,0301000000000000$[C][L]%00,01,0008,21,00,FAULT 21 LIVING ROOM MOTION     $[C][L] [hwalrm1]
2016-09-07 09:39:27 - Alarm: Partition State Change [hwalrm1]
2016-09-07 09:39:27 - Alarm: Virtual Keypad Update (01,0008,21,00,FAULT 21 LIVING ROOM MOTION     $) [hwalrm1]
2016-09-07 09:39:27 - Alarm/ISY: Zone 21 (Zone 21) Open [hwalrm1]
2016-09-07 09:39:27 - ISY: Variable hwalrm1_z21-ST added to queue (Val: 1, QS: 1)
2016-09-07 09:39:27 - ISY: Variable hwalrm1_part1-GV6 added to queue (Val: 0, QS: 2)
2016-09-07 09:39:27 - ISY: Variable hwalrm1_part1-GV2 added to queue (Val: 0, QS: 3)
2016-09-07 09:39:27 - ISY: Variable hwalrm1_part1-GV5 added to queue (Val: 0, QS: 4)
2016-09-07 09:39:27 - ISY:  (ns/1/nodes/n001_hwalrm1_z21/report/status/ST/1/25)
2016-09-07 09:39:27 - ISY: Variable hwalrm1_part1-GV4 added to queue (Val: 0, QS: 4)
2016-09-07 09:39:27 - ISY: Variable hwalrm1_part1-GV1 added to queue (Val: 0, QS: 5)
2016-09-07 09:39:27 - ISY: Variable hwalrm1_part1-ST added to queue (Val: 0, QS: 6)
2016-09-07 09:39:27 - ISY: Variable hwalrm1_part1-GV3 added to queue (Val: 0, QS: 7)
2016-09-07 09:39:27 - ISY: Variable hwalrm1-ST added to queue (Val: -1, QS: 
2016-09-07 09:39:27 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV6/0/25)
2016-09-07 09:39:27 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV2/0/25)
2016-09-07 09:39:27 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV5/0/25)
2016-09-07 09:39:27 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV4/0/25)
2016-09-07 09:39:27 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV1/0/25)
2016-09-07 09:39:27 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/ST/0/25)
2016-09-07 09:39:28 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV3/0/25)
2016-09-07 09:39:28 - ISY:  (ns/1/nodes/n001_hwalrm1/report/status/ST/-1/25)
2016-09-07 09:39:31 - TCP: Data Received - 76 Bytes [hwalrm1]
2016-09-07 09:39:31 - TCP: %02,0101000000000000$[C][L]%00,01,1C08,08,00,LOWER             Ready to Arm  $[C][L] [hwalrm1]
2016-09-07 09:39:31 - Alarm: Partition State Change [hwalrm1]
2016-09-07 09:39:31 - Alarm: Virtual Keypad Update (01,1C08,08,00,LOWER             Ready to Arm  $) [hwalrm1]
2016-09-07 09:39:31 - ISY: Variable hwalrm1_part1-GV6 added to queue (Val: 0, QS: 1)
2016-09-07 09:39:31 - ISY: Variable hwalrm1_part1-GV2 added to queue (Val: 1, QS: 2)
2016-09-07 09:39:31 - ISY: Variable hwalrm1_part1-GV5 added to queue (Val: 0, QS: 3)
2016-09-07 09:39:31 - ISY: Variable hwalrm1_part1-GV4 added to queue (Val: 0, QS: 4)
2016-09-07 09:39:31 - ISY: Variable hwalrm1_part1-GV1 added to queue (Val: 0, QS: 5)
2016-09-07 09:39:31 - ISY: Variable hwalrm1_part1-ST added to queue (Val: 0, QS: 6)
2016-09-07 09:39:31 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV6/0/25)
2016-09-07 09:39:31 - ISY: Variable hwalrm1_part1-GV3 added to queue (Val: 0, QS: 6)
2016-09-07 09:39:31 - ISY: Variable hwalrm1-ST added to queue (Val: 1, QS: 7)
2016-09-07 09:39:31 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV2/1/25)
2016-09-07 09:39:31 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV5/0/25)
2016-09-07 09:39:31 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV4/0/25)
2016-09-07 09:39:31 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV1/0/25)
2016-09-07 09:39:31 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/ST/0/25)
2016-09-07 09:39:32 - ISY:  (ns/1/nodes/n001_hwalrm1_part1/report/status/GV3/0/25)
2016-09-07 09:39:32 - ISY:  (ns/1/nodes/n001_hwalrm1/report/status/ST/1/25)
2016-09-07 09:39:33 - Web Request: /index.htm

Can you open your system back up - compared code to HonLink and don't see an obvious difference.

 

----------------------

 

Looking a little more...  I'm guessing you have multiple partitions, and in HonLink you had configured which zones belong to which partitions?

Edited September 8, 20169 yr by io_guy

I'm not at home at the moment, but you are correct - I have two partitions on the system, and had configured which zones were in each.

OK,

Missed moving over some code for that.  New version should fix it (you'll have to configure zones similar to HonLink).

Great, thanks!