We have moved at community.getvera.com

Author Topic: Re: Setup  (Read 9121 times)

Offline glaso

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: Re: Setup
« Reply #30 on: January 03, 2011, 04:43:31 pm »
Hi Futzle: Here are the logs for the panic actions

With the RequestPolicePanic action, the siren doesn't trigger, it just activate the Aux 2 relay
Same thing for the RequestFirePanic action
With the RequestMedicalPanic action, nothing happens at all.

This could serve ou needs in case if we connect one zone to the aux outputs. That way when the aux is triggered, the zone is tripped and the alarm gets triggered, but I am no sure if it is a desirable way to do it.

THANKS!!!



Quote
RequestPolicePanic
50      01/03/11 18:17:21.498   luup_log:20: Received good message 0x1d <0x5416>
50      01/03/11 18:17:21.499   luup_log:20: Message: Incoming message body: <0x5416>
50      01/03/11 18:18:23.678   luup_log:20: Job: Partition: RequestPolicePanic 21 job userdata: 0x7ad848 <0x400>
50      01/03/11 18:18:23.679   luup_log:20: Job: Adding job <0x400>
50      01/03/11 18:18:23.680   luup_log:20: Job: Processing send queue <0x400>
50      01/03/11 18:18:23.682   luup_log:20: Message: Outgoing: 0x7e 0x03 0x3e 0x04 0x01 0x46 0xcf <0x400>
50      01/03/11 18:18:23.683   luup_log:20: Job: Done <0x400>
50      01/03/11 18:18:23.728   luup_log:20: Received good message 0x1d <0x5416>
50      01/03/11 18:18:23.728   luup_log:20: Message: Incoming message body: <0x5416>

RequestFirePanic
50      01/03/11 18:19:05.907   luup_log:20: Job: Partition: RequestFirePanic 21 job userdata: 0x7581e0 <0x400>
50      01/03/11 18:19:05.908   luup_log:20: Job: Adding job <0x400>
50      01/03/11 18:19:05.908   luup_log:20: Job: Processing send queue <0x400>
50      01/03/11 18:19:05.910   luup_log:20: Message: Outgoing: 0x7e 0x03 0x3e 0x04 0x01 0x46 0xcf <0x400>
50      01/03/11 18:19:05.912   luup_log:20: Job: Done <0x400>
50      01/03/11 18:19:05.978   luup_log:20: Received good message 0x1d <0x5416>
50      01/03/11 18:19:05.978   luup_log:20: Message: Incoming message body: <0x5416>

RequestMedicalPanic
50      01/03/11 18:19:51.401   luup_log:20: Job: Partition: RequestMedicalPanic 21 job userdata: 0x7ac808 <0x400>
50      01/03/11 18:19:51.402   luup_log:20: Job: Adding job <0x400>
50      01/03/11 18:19:51.403   luup_log:20: Job: Processing send queue <0x400>
50      01/03/11 18:19:51.404   luup_log:20: Message: Outgoing: 0x7e 0x03 0x3e 0x05 0x01 0x47 0xd1 <0x400>
50      01/03/11 18:19:51.406   luup_log:20: Job: Done <0x400>
50      01/03/11 18:19:51.470   luup_log:20: Received good message 0x1d <0x5416>
50      01/03/11 18:19:51.471   luup_log:20: Message: Incoming message body: <0x5416>

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #31 on: January 04, 2011, 03:52:55 pm »
With the RequestPolicePanic action, the siren doesn't trigger, it just activate the Aux 2 relay

My mistake, I programmed PolicePanic to do the same thing as FirePanic.  I've now changed PolicePanic to the "correct" code.  (I say "correct" because I doubt the truth of the documentation I've got.)  Can you please log the RequestPolicePanic again?

Thanks for all the logs.  It will take me a while to go through them, but I do appreciate your effort.

Offline guessed

  • Community Beta
  • Master Member
  • ******
  • Posts: 5301
  • Karma: +92/-22
  • Release compat is not a bolted-on afterthought
Re: Re: Setup
« Reply #32 on: January 05, 2011, 11:41:42 am »
Quote
3. I have my garage door connected to the aux outs on my alarm to open my garage. Is there a way to control the 4 aux outs on the panel through Vera?

It seems no.  There might be a more hackish way to do it.  I'll ruminate and see if one occurs to me.

Can we break this part out to the separate discussion thread on Alarm standardization.  My panel can do that also, but there are limits, and I'd like to see if we can have a common method between the panels that can do this type of thing.

Once we work out a common pattern, I'll gut the legacy code I had for this, since mine was incomplete and I've never gotten around to using it.


PS: My ultimate "use case" for that feature is to enable Solenoid-based Door-jam lock kits, since each of my Control Panels has an output associated with it that can be triggered.  @drew's garage door one is another useful one.

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #33 on: January 13, 2011, 03:46:23 am »
I wan't to know when the alarm is ringing. During my tests, when the alarm is tripped, the "breached" variable never gets to 1.

I've just uploaded revision 26 of I_CaddxNX584Security.xml to code.mios.com.  This should hopefully fix the "Breached" variable problem.  The logs were very helpful in pinpointing the problem.

I've opted to make Breached latch on until you disarm the system.  I figure that's slightly more useful than having it reset back to off when the siren switches off.


Offline glaso

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: Re: Setup
« Reply #34 on: January 14, 2011, 05:22:00 pm »
Hi Fuztle very tanks for your efforts on this !!

Ive downloaded the r26 of the I_CaddxNX584Security.xml and the following are happening:

1.- After gets the alarm triggered when armed, the variable "breached" never gets to "1" and
2.- i cant get the alarm disarmed via Dashboard anymore or any other action to the NX-8E, it just lost communication between the Vera and the NX-8E.

Ive to gets the alarm disarmed via the phisical keypad, and the dashboard reloaded in order to get  communication between the vera and the NX-8E again.

Ive attached the log of the test: ARMING, TRIGGERING(activating a zone sensor), and trying to gets disarmed (three times) via the dashboard.


Regards.-

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #35 on: January 15, 2011, 12:04:33 am »
1.- After gets the alarm triggered when armed, the variable "breached" never gets to "1" and

Yes, looks like I've introduced a logic error and the setter is never being set.  I will fix this.

Edit: Try revision 27, it's got extra brackets and I think it was the cause of this, and may also have broken disarming.

Quote
2.- i cant get the alarm disarmed via Dashboard anymore or any other action to the NX-8E, it just lost communication between the Vera and the NX-8E.

Not at all sure about this.  I hope that the log explains what's happening.  I will look at this soon.
« Last Edit: January 15, 2011, 12:20:51 am by futzle »

Offline glaso

  • Jr. Member
  • **
  • Posts: 59
  • Karma: +0/-0
Re: Re: Setup
« Reply #36 on: January 24, 2011, 01:16:20 pm »
Well done in your update Fuztle !! Rev.27 does the job !! now it reports the "breached" variable = 1, and all works fine after the operation. I attach the log of the operation for your analysis.

The operation was: Arm, trigger a sensor, leave the alarm to siren for a while, then disarm.

Thanks Fuztle !!

Offline futzle

  • Moderator
  • Master Member
  • *****
  • Posts: 3260
  • Karma: +192/-9
Re: Re: Setup
« Reply #37 on: January 24, 2011, 03:42:17 pm »
Great, I'm glad it works.  Now please go join the discussion on Alarm panel standardization so we can tell what features real users want from their alarm panel plugins.

Offline eddie

  • Beta Testers
  • Jr. Member
  • *****
  • Posts: 51
  • Karma: +0/-0
Re: Re: Setup
« Reply #38 on: January 26, 2011, 09:38:00 pm »

@glaso
Check your NX8e configuration,  mine did not have Quick Arm enabled.
Once I enabled quick arm the buttons worked fine.



[quote author=glaso link=topic=4060.msg28916#msg28916 date=1293627850

Quick arm and quick stay buttons doesn't seem to show consistently the status of the alarm. Sometimes they do, but sometimes don't. This buttons doesn't seem to do anything when pressed with my config.


[/quote]