alarm not going into armed state properly

hi travis, all,

finally (after maybe 9 years!) migrated from serial bridge to your plugin, very nice work and much appreciated.

everything seems to be working fine, EXCEPT:

when arming, either by direct keypad or by plugin command, the exit delay is properly indicated in the device state (keypad) and in the log, but when the system finishes delay and goes to arm, nothing is logged, and the device state, while it says 'armed' the icon is blank and no triggers that are set for an armed state are fired.

so. what can be the issue here? i've reloaded, etc. i've tried a different keypad with different partition (tried partition 2 even though it says only one partition for now and i am only one partition (1) in my dsc config...)

any thoughts?? this is quite a deal breaker for me on this if i can't get it sorted. one of the main functions of the interface is to communicate an armed/disarmed state... obv.

thanks for any help, and time is of the essence please.


thx,

dylan

log section when remote arming in away mode. all seems to work fine, except triggers that trigger on alarm armed in away don't trigger.

Code: Select all

Dec 21, 2014, 9:12:14 AM
  WebServer                       request to execute "north knoll one" control #2 from 192.168.0.102
  DSC Alarm                       Arming alarm in away mode.
  DSC Alarm Debug                 TX: 0301C4

  DSC Alarm Debug                 RX: 50003028
  DSC Alarm Debug                 ACK for cmd 030.
  DSC Alarm Debug                 RX: 6561D2
  DSC Alarm                       Exit Delay. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to exitDelay.
  DSC Alarm Debug                 ID: speakTextArming

Dec 21, 2014, 9:13:16 AM
  DSC Alarm Debug                 RX: 7011C9
  DSC Alarm Debug                 RX: 6521CE
  DSC Alarm Debug                 Alarm Armed. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to armed.
  DSC Alarm Debug                 RX: 550091212211491
  DSC Alarm Debug                 Alarm time is within 1 minute of actual time, no update necessary.

Code: Select all

Dec 21, 2014, 9:14:55 AM
  WebServer                       request to execute "north knoll one" control #10 from 192.168.0.102
  DSC Alarm                       Disarming alarm
  DSC Alarm Debug                 TX: 0401340600F2

  DSC Alarm Debug                 RX: 50004029
  DSC Alarm Debug                 ACK for cmd 040.
  DSC Alarm Debug                 RX: 750100018E
  DSC Alarm                       Alarm disarmed by user 0001. (Partition 1)
  DSC Alarm Debug                 RX: 6551D1
  DSC Alarm                       Alarm Disarmed. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to disarmed.
  DSC Alarm Debug                 Updating state ArmedState for keypad on partition 1 to disarmed.
  DSC Alarm Debug                 <<-- entering triggerEvent: eventAlarmDisarmed
  Trigger                         alarmcomm partition disarmed (7501004091)
  DSC Alarm Debug                 ID: speakTextDisarmed
  DSC Alarm Debug                 RX: 6501CC
  DSC Alarm Debug                 Partition 1 Ready


and here is arming in stay mode, same results (ignore 'alarm trip' entries, that's a delayed action from previous testing):

Code: Select all

DSC Alarm Debug                 RX: 6561D2
  DSC Alarm                       Exit Delay. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to exitDelay.
  DSC Alarm Debug                 ID: speakTextArming
  DSC Alarm Debug                 RX: 550091612211495
  DSC Alarm Debug                 Alarm time is within 1 minute of actual time, no update necessary.
  Schedule                        alarm TRIP trigger (60110065E) (delayed action)
  Sent INSTEON                    "office/floor lamp" off

Dec 21, 2014, 9:19:04 AM
  Schedule                        alarm TRIP trigger (60110065E) (delayed action)
  Sent INSTEON                    "bedroom/north lamp" off
  DSC Alarm Debug                 RX: 7011C9
  DSC Alarm Debug                 RX: 6521CE
  DSC Alarm Debug                 Alarm Armed. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to armed.

Dec 21, 2014, 9:19:44 AM
  DSC Alarm Debug                 RX: 7501004091
  DSC Alarm                       Alarm disarmed by user 0040. (Partition 1)
  DSC Alarm Debug                 RX: 6551D1
  DSC Alarm                       Alarm Disarmed. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to disarmed.
  DSC Alarm Debug                 Updating state ArmedState for keypad on partition 1 to disarmed.
  DSC Alarm Debug                 <<-- entering triggerEvent: eventAlarmDisarmed
  Trigger                         alarmcomm partition disarmed (7501004091)
  DSC Alarm Debug                 ID: speakTextDisarmed
  DSC Alarm Debug                 RX: 6501CC
  DSC Alarm Debug                 Partition 1 Ready
  DSC Alarm Debug                 RX: 60900635


this actually makes the system unusable for me as i must have the comms on armed and disarmed working perfectly.

is there something in my dsc programming that is tripping up the plugin?? i can't see what. in looking at your debug log i think you are using the exact same command and state codes that i was with the serial bridge script i wrote that has been working insanely rock solid for nearly a decade. so, what can be the thing here???

thanks!!!!!

also can see from the log that the disarm state is communicating and triggering properly.. just neither of the arm states.......

what seems to be not happening in any arming mode (pressing away, stay, or entering code locally or remotely via interface) is this, that IS happening for disarm:

Code: Select all

  DSC Alarm Debug                 Updating state ArmedState for keypad on partition 1 to disarmed.


the only state updated during arm is 'state state'... not 'ArmedState'.

Code: Select all

 DSC Alarm                       Alarm Disarmed. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to disarmed.
  DSC Alarm Debug                 Updating state ArmedState for keypad on partition 1 to disarmed.
  DSC Alarm Debug                 <<-- entering triggerEvent: eventAlarmDisarmed
  Trigger                         alarmcomm partition disarmed (7501004091)


Code: Select all

 DSC Alarm Debug                 RX: 700100408C
  DSC Alarm                       Alarm armed by user 0040. (Partition 1)
  DSC Alarm Debug                 RX: 6521CE
  DSC Alarm Debug                 Alarm Armed. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to armed.


this seems like a bug? is this just the version plugin i have??? do others have this issue, i can't see how they don't? unless my version is not the correct working version.

running v1.5.4 from github.

update says this is the current v.

any thoughts?? helpppp. thx.

the asterisked lines are NOT in my py script currently, i am surmising they. or something like them is missing and causing the trouble i'm having of armed events not triggering. those lines are ones i cobbled together from lines that DO appear in the disarm code command block.... any thoughts??

Code: Select all

elif cmd == '652':
         if len(dat) == 1:
            partition = int(dat)
            self.logger.log(3, u"Alarm Armed. (Partition %d)" % partition)
            self.updateKeypad(partition, u'state', kAlarmStateArmed)
            ****self.triggerEvent(u'eventAlarmArmed’)****
            #TODO: This response does not tell us armed type trigger.  Stay, Away, etc.  :(
         elif len(dat) == 2:
            m = re.search(r'^(.)(.)$', dat)
            if m:
               (partition, mode) = (int(m.group(1)), int(m.group(2)))
               self.logger.log(1, u"Alarm Armed in %s mode. (Partition %d)" % (kArmedModeList[mode], partition))
               if (mode == 0) or (mode == 2):
                  armedEvent = u'armedAway'
                  self.updateKeypad(partition, u'ArmedState', kAlarmArmedStateAway)
                  ****self.triggerEvent(u'eventAlarmArmedAway’)****
               else:
                  armedEvent = u'armedStay'
                  self.updateKeypad(partition, u'ArmedState', kAlarmArmedStateStay)
                  ****self.triggerEvent(u'eventAlarmArmedStay’)****

               self.triggerEvent(armedEvent)
               self.updateKeypad(partition, u'state', kAlarmStateArmed)


OK. well as expected, those lines don't compile. i tried. i guess that's not the var names or something...

what else to try??

I'll have a peek at this tonight.

oh great, thanks much!

'nother small note, it seems that the plugin is checking the alarm system time every four minutes. is this addressable in any way, can a variable be tweaked? i'd say once every 24 hours is often enough for my systems... fwiw.

After going through your log and the code, it appears your panel or interface is not sending the armed state. It's simply saying the alarm was armed.

See below. When your alarm arms, the plugin is sent the following data:

Code: Select all

  DSC Alarm Debug                 RX: 7011C9
  DSC Alarm Debug                 RX: 6521CE
  DSC Alarm Debug                 Alarm Armed. (Partition 1)
  DSC Alarm Debug                 Updating state state for keypad on partition 1 to armed.

The first RX of 7011 simply says partition 1 has been armed. The next RX, 6521, says the same thing. Neither of those commands say wether the alarm was armed in a particular mode. So there's no way for the plugin to know. That's why in your case the plugin falls back to just stating armed or disarmed.

I'm guessing you're using the old PC-5401 interface? The IT-100 and 2/3DS should report the armed state. Or I suppose it's possible the firmware of your alarm is really old and not forwarding that data to the interface.

You may have to fall back to using the Alarm State instead of Armed State. That will let you know for sure if the alarm is armed or disarmed.

Did your previous setup actually report how the alarm was armed? If so, I'd love to know how. The plugin could only know if it was the one to arm the alarm, if it was armed from a keypad I can't see how it would know which mode.

Travis

'nother small note, it seems that the plugin is checking the alarm system time every four minutes. is this addressable in any way, can a variable be tweaked? i'd say once every 24 hours is often enough for my systems... fwiw.

The alarm broadcasts the time every 4 minutes. The plugin is not asking for the time at that frequency, the panel does it for the keypads. When it sees the broadcast the plugin compares it to the actual time to see if it needs an update.

copy that on the time broadcasting.. ok.

on the armed type, yes, i was using armed away and stay. stay received this from the dsc comm board: 6561CE

exit delay was: 6561D2

and i think i used this for away: 6521CE (which may be partition armed)

but, yes, i did have those differentiated.

but to be clear i have not gotten any armed state to fire a trigger since installing the plugin. what am i missing here? yes, i would like to continue using away and stay of course, but at the moment i can't even get a plain old armed to trigger anything. i've tried all three several different ways....

thoughts?

thanks

ok, i see i can use states of the keypad device to trigger, i am trying that now--

Code: Select all

stay received this from the dsc comm board: 6561CE
exit delay was: 6561D2

One of those is invalid, must be a typo. The last two digits are the checksum, you can ignore those. The command 656 with data 1 just means partition 1 is starting an exit delay.

Code: Select all

and i think i used this for away: 6521CE (which may be partition armed)

Right, that just means partition 1 armed, but it does not specify away or stay.

but to be clear i have not gotten any armed state to fire a trigger since installing the plugin. what am i missing here? yes, i would like to continue using away and stay of course, but at the moment i can't even get a plain old armed to trigger anything. i've tried all three several different ways....

Instead of firing of the Armed State trigger, fire off the Alarm State. That one should at least work for armed/disarmed. I don't see any way to get the away/stay state from what I'm seeing in your log.

ok, i'm with you.

but, i definitely was using a stay command trigger. i know it's worked in the past. i can arm in stay and the lights stay on, etc. it works. it's been years since i programmed the boards and the triggers so it's definitely not fresh in my mind... but i know i sorted it somehow. those are the codes that were matched in my old database before updating to the plugin.. so, i'm pretty sure those codes were working as stated.

i am using alarm state instead of armed state to trigger... any more research you can sort on the stay v. away of it all would be terrific.


thanks travis.


ps - can i contribute? is that on your web page?