I’ve successfully connected my new VeraLite to the CADDX NX-8/NX584 and the CADDX plugin installation went smoothly.
In testing the micasaverde alarm notifications by text message, I was thrilled to see a text message alert appear in 1 second after the alarm tripped. What I’m concerned about though is the alert message omits which specific ZONE was tripped. (I have 1 partition with 23 zones).
Currently my system is self-monitored, so it is obviously very important to know if it was fire/smoke or a window/door zone that tripped. Is there a configuration option I am missing to display the zone in the alert?
The CADDX NX plugin was installed from the micasaverde app store, but it appears this has been removed recently. Should I start over and delete it and install the plugin found in the wiki instead? Maybe it won’t have this problem.
The versions on apps.mios.com and code.mios.com are identical. If you install a plugin from apps.mios.com, it no longer appears in search results, giving the false impression that it has been removed from the store.
I’m not certain that the serial protocol includes the information you want, to identify the cause of a partition entering the alarm state. I will take another look. Even if the information is there, it may not be easy to create a notification that includes the guilty zone name; notifications don’t have this kind of flexibility.
In the mean time you may have to come up with a workaround that performs notifications on the zones themselves if they trip.
Edit:
I’ve looked again at the serial protocol document. There’s nothing in the Partition Status message that can identify which zone caused the partition to enter the alarm state (indeed, given that there are handoff and entry zones in advanced configurations I’m not convinced that there is a concept of “which zone (singular)”).
Two leads which you can follow for me:
There is a boolean field “Alarm Memory” on the zone status info. There’s no documentation on what it means but the name sounds promising. I’ll need you to capture a Luup log with debugging turned on, starting after you arm the partition, containing that partition entering the alarm state and ending before you cancel the alarm with a PIN. Make sure that the log doesn’t include your PIN. Then I can see if the bit turns on or off in any useful way.
Also I see there is an event log entry called “Alarm” on zones. Take a look in the event log tab and see if that event is reported in any useful way.
Futzle - thanks very much for your advice and for your time looking into this.
Before I saw your followup edit, I had already implemented your workaround advice and configured independent alarm notifications for each of the 23 zones. It was a bit time consuming to set up compared to just a single alert configured for the master Partition 1 device, but I now have the full zone description in the alerts, so I am good now.
However, I would be happy to assist with obtaining more data that can improve the Partition alerts. The event log for the main CADDX NX-8 device does show the zone that was tripped…
15-9 7:25 Alarm (Zone 2 Partition 1)
Here’s the actual alert that was sent via SMS -
[size=8pt]Your trigger “Lake Home Alarm Breach!” occurred. The originating device ID:25 Partition 1 in room: NetworX Security System The ID is: xxxxxxxxx Code: Alarm Value:Active Serial #xxxxxxxx[/size]
I’ll followup with the detailed luup log info you asked for as soon as I can.
Attached is the Luup debug data you asked for, which starts right before the Alarm for Zone 4 (Master BR Balcony Door) was triggered. The debug log was disabled just before the alarm was manually cleared.
I should point out that I am only getting alert notifications from Partition 1 which are the generic alarm-triggered and cleared events. The individual alerts I configured today for each zone are NOT sending notifications! Not clear what the difference is between the two notification name options “A sensor (window/door) is tripped” versus “An Armed sensor is tripped”, but I’ve tried both (see AlarmNotification.jpg attachment). Any idea why I’m not getting notifications from individual zones?
At about 12:03 in the log file is when the Door (zone 4) alarm was triggered.
[quote=“GaryOkie, post:4, topic:174800”]The individual alerts I configured today for each zone are NOT sending notifications!
[…]
Any idea why I’m not getting notifications from individual zones? [/quote]
Thanks for the log capture. It corroborates your statement that zones aren’t reporting status. Probably you haven’t configured the panel interface to send asynchronous zone status messages. See here for a previous discussion I had with another user; it should apply equally to you.
Not clear what the difference is between the two notification name options "A sensor (window/door) is tripped" versus "An Armed sensor is tripped", but I've tried both (see AlarmNotification.jpg attachment).
They differ in terms of whether the event fires any time it trips (the former) or only when the sensor is not in Bypass mode (the latter). Neither takes into account whether the matching partition is armed.
Apparently some of the panel configurations I had made when I first set this up were not saved. I may have missed entering * to save location 3 segment 1. Don’t know why else this isn’t set.
Thanks a bunch for looking at that log file and pointing out this critical omission. I will go through all settings on the panel again to make sure they are set.
Gary
Best Home Automation shopping experience. Shop at Ezlo!