We have moved at community.getvera.com

Author Topic: Status Bouncing  (Read 2829 times)

Offline MaffooClock

  • Newbie
  • *
  • Posts: 4
  • Karma: +1/-0
Status Bouncing
« on: January 26, 2013, 04:41:59 pm »
I'm nervous about posting this topic since there are only two others in this forum -- makes me think I'm doing something wrong, but it doesn't seep appropriate to tack on to an existing, 2-year-old, 39-page thread.

I've been troubleshooting a problem for days.  I've got a Vera Lite v1.5.532 with the v2.45 plugin.  I have configured my AD2USB to use address 23, which has been enabled in my Vista 20P.  Everything works, except when the system is armed, the "Status:" line constantly bounces between "Armed" and "Ready" every few seconds.  I have also noticed that when the system is disarmed, the "Chime Mode" toggles on and off (dark blue and light blue) at the same frequency.

I started poking at the LuaUPnP.log for VistaAlarmPanel messages and found that when the system is armed, I see messages like "ARMED ***STAY***May Exit Now  35", with the number decreasing every second or so (obviously, this is the countdown).  In the middle of these countdowns, I see another message "****DISARMED****  Ready to Arm".

The ARMED messages look like this:
Code: [Select]
50 01/26/13 16:14:46.535 luup_log:46: (VistaAlarmPanel::processIncoming) Incoming data = '[0011000110000000----],010,[f70600871010008028020000000000],"ARMED ***STAY***May Exit Now  10"'. <0x2de51680>
50 01/26/13 16:14:46.535 luup_log:46: (VistaAlarmPanel::getStatusFlags) Active flags: ARMED_STAY, CHIME_MODE <0x2de51680>
50 01/26/13 16:14:46.536 luup_log:46: (VistaAlarmPanel::getPartitionState) Got Alarm='None' for partition 1 (device #47). <0x2de51680>
50 01/26/13 16:14:46.536 luup_log:46: (VistaAlarmPanel::getPartitionState) Got ArmMode='Armed' for partition 1 (device #47). <0x2de51680>
50 01/26/13 16:14:46.537 luup_log:46: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='Stay' for partition 1 (device #47). <0x2de51680>

And the DISARMED messages look like this:
Code: [Select]
50 01/26/13 16:14:42.125 luup_log:46: (VistaAlarmPanel::processIncoming) Incoming data = '[1000000100000000----],008,[f70000080008001c08020000000000],"****DISARMED****  Ready to Arm  "'. <0x2de51680>
50 01/26/13 16:14:42.126 luup_log:46: (VistaAlarmPanel::getStatusFlags) Active flags: READY <0x2de51680>
50 01/26/13 16:14:42.126 luup_log:46: (VistaAlarmPanel::getPartitionState) Got Alarm='None' for partition 1 (device #47). <0x2de51680>
06 01/26/13 16:14:42.126 Device_Variable::m_szValue_set device: 47 service: urn:micasaverde-com:serviceId:VistaAlarmPanel1 variable: ChimeMode was: 1 now: 0 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2de51680>
50 01/26/13 16:14:42.127 luup_log:46: (VistaAlarmPanel::getPartitionState) Got ArmMode='Armed' for partition 1 (device #47). <0x2de51680>
50 01/26/13 16:14:42.127 luup_log:46: (VistaAlarmPanel::getArmMode) current ArmMode = 'Armed', new ArmMode = 'Disarmed' <0x2de51680>
50 01/26/13 16:14:42.128 luup_log:46: (VistaAlarmPanel::setPartitionState) Set ArmMode='Disarmed' for partition 1 (device #47). <0x2de51680>
50 01/26/13 16:14:42.129 luup_log:46: (VistaAlarmPanel::getPartitionState) Got DetailedArmMode='Stay' for partition 1 (device #47). <0x2de51680>
50 01/26/13 16:14:42.129 luup_log:46: (VistaAlarmPanel::getArmMode) current DetailedArmMode = 'Stay', new DetailedArmMode = 'Ready' <0x2de51680>
50 01/26/13 16:14:42.129 luup_log:46: (VistaAlarmPanel::setPartitionState) Set DetailedArmMode='Ready' for partition 1 (device #47). <0x2de51680>

Attached is an excerpt from the log that shows the panel READY, then ARMED STAY until a few seconds after the countdown expires, then DISARMED again.  Arming and disarming for this log was done with the Vera.
« Last Edit: January 26, 2013, 05:28:38 pm by MaffooClock »

Offline MaffooClock

  • Newbie
  • *
  • Posts: 4
  • Karma: +1/-0
Re: Status Bouncing
« Reply #1 on: January 26, 2013, 06:25:26 pm »
Hmm... I think I have solved the issue, although I have no idea what the problem was.

After my discovery in the log, I decided to review the keypad addresses (*190-*196).  I have a Tuxedo keypad (an AUI device), a GSMx for use with Total Connect 2 (also uses an AUI address), and a 5828 wireless keypad (uses the 5883 transceiver, but no keypad address).  Thus, I determined that technically none of the keypad addresses should be in use (except 23, which I have the AD2USB configured to use), so I disabled all of them except 23 (and 16, of course, since it can't be disabled).

Also, the "KeypadAddresses" field for the partition 1 device in Vera has been set to just 23.  The bouncing problem has disappeared, and the logs show consistent and non-conflicting entries on status.

I would still like to learn what's going on here.

Offline MaffooClock

  • Newbie
  • *
  • Posts: 4
  • Karma: +1/-0
[SOLVED] Status Bouncing
« Reply #2 on: January 26, 2013, 07:52:42 pm »
I thought about my discovery and finally realized that the address to which the AD2USB was assigned was configured for common partition (value of 3) instead of partition 1 (value of 1).

So, if you see status bouncing one a single-partition setup in Vera, make sure that the keypad address in the panel is set only for the applicable partition.