We have moved at community.getvera.com

Author Topic: Alarm Event  (Read 1803 times)

maros

  • Guest
Alarm Event
« on: July 31, 2014, 05:46:16 pm »
Hi,
I do have a couple of VISION ZD2102 door sensors and would like to use them for bigger windows that require two reed sensors for complete monitoring. The ZD2102 has extra connect pins for external sensors (see http://www.zipato.com/UserDocsImages/_SHOP/user_manuals/VISION-magnet%20ZD%202102.pdf). However the internal and the external sensors report separately. The internal sensor works just like any other Motion/Door sensor, whereas the external sensor (as far as I understand the manual) only issues alarm reports and the status cannot be viewed in the UI.

How can I catch these alarm reports/events in my scene controller code?

That's what I see in the log files when i open the part of the window that is monitored by the external sensor:
2   07/31/14 23:38:16.585   ZWaveNode::HandlePollUpdate_Alarm node 45 device 110 v1type: 7 v1level: 255 source: 0 status: 255 type: 7 event: 3 parms: 0 code: (null) <0x2b54d680>
02   07/31/14 23:38:36.605   ZWaveNode::HandlePollUpdate_Alarm node 45 device 110 v1type: 7 v1level: 255 source: 0 status: 255 type: 7 event: 3 parms: 0 code: (null) <0x2b54d680>

Is it possible to create a child device that would represent the state of the external reed-sensor?

Cheers
Maros


maros

  • Guest
Re: Alarm Event
« Reply #1 on: August 10, 2014, 04:20:39 am »
Is there really no way to catch an alarm event?

This is what I observe in /var/log/cmh/LuaUPnP.log when I trip one of the reed sensors (internal and external):

Open internal:
ZWaveNode::HandlePollUpdate_Alarm node 45 device 110 v1type: 7 v1level: 255 source: 0 status: 255 type: 7 event: 2 parms: 0 code: (null) <0x2b5c3680>
Additionally Tripped, ArmedTripped and LastTrip variables are updated

Close internal:
ZWaveNode::HandlePollUpdate_Alarm node 45 device 110 v1type: 7 v1level: 0 source: 0 status: 255 type: 7 event: 2 parms: 0 code: (null) <0x2b5c3680>
Same variables are updated

Open external:
ZWaveNode::HandlePollUpdate_Alarm node 45 device 110 v1type: 7 v1level: 255 source: 0 status: 255 type: 7 event: 254 parms: 0 code: (null) <0x2b5c3680>
No variables are updated

Close external:
ZWaveNode::HandlePollUpdate_Alarm node 45 device 110 v1type: 7 v1level: 0 source: 0 status: 255 type: 7 event: 254 parms: 0 code: (null) <0x2b5c3680>
No variables are updated

So basically the main difference between the external and internal sensor is the event type. Can I bind an event handler to this specific event (and eventually update the variables in a child device manually)?
   

Offline Pshomectrl

  • Sr. Newbie
  • *
  • Posts: 24
  • Karma: +0/-0
Re: Alarm Event
« Reply #2 on: August 16, 2014, 07:33:21 am »
Hi Maros
I do have the same questions.
Did you already find a solution?
Or did you hear something from Micasaverde?
Regards, Paul

maros

  • Guest
Re: Alarm Event
« Reply #3 on: September 10, 2014, 04:02:51 pm »
I filed a bug (#48813 -> http://support.mios.com/customer/portal/private/cases/48813) and got this reply:

Quote
I?ve added a feature request to our developers so that it will be added in the future software versions. Typically when the external sensor is used it should update the same Tripped variable, and thus indicating the status of the sensor.
Let me know if you have other questions and I?ll get back to you asap.

Hope it will be fixed soon.

Offline Alpoy

  • Newbie
  • *
  • Posts: 15
  • Karma: +0/-0
Re: Alarm Event
« Reply #4 on: April 13, 2015, 04:32:13 am »
Do you know if this has been fixed ?

Offline dantheman2865

  • Newbie
  • *
  • Posts: 2
  • Karma: +0/-0
Re: Alarm Event
« Reply #5 on: September 15, 2015, 05:21:17 pm »
Would love to see this functionality added. I think it would make the platform a lot more powerful if we could receive raw Z-Wave messages.