@hughheaves
I have a Vera2 running UI4 and I uploaded your two new files but I keep getting a “Startup Lua Failed” error. I grabbed them from Branches/UI4…
[quote=“Thinkfire, post:399, topic:168766”]Hi,
First off, THANK YOU for this plugin. What a lifesaver. 
One issue I am having and can’t figure out. I’ve read at least 3/4s of this thread and not seeing a solution.
I have a zone called Slider. I set up a scene, whenever slider is faulted, the back porch light is triggered and it sends a notification to my email. I set a notification in the actual slider zone.
What happens:
Slider is opened, back porch light comes on, I get a notification.
Great!
Except…
I close the slider.
I try to turn the back porch light off, it turns back on instantly. I wait 2 minutes. Try again. I wait 5 minutes, try again.
The only way I can get my back porch light to stay off is by disabling the scene that turns it on when the slider sensor is faulted.
It’s like the system still thinks my slider door is open…even though my alarm shows a ready state, so…it knows the zone is no longer faulted…
Hmmm? Ideas?[/quote]
Some additional information:
The Slider Zone tile still has a red guy on it. All my zones that have been trpiped since installing this are red and not resetting back to normal. I also noticed that under all of the tripped ones, under the advanced tab, there is this:
Variables
Armed 1
Tripped 1
LastTrip random number (assuming its a time stamp)
and the ones that have not been tripped yet, don’t have a lasttrip setting and
Variables
Armed 1
Tripped 0
My alarm system recognizes these zones as no longer being faulted and displays a ready state in my UI4 tile for the alarm partition…so…it would appear that it’s not resetting the zones once they are tripped. How do I fix this?
I’ve also noticed that it’s not reporting the zone thats faulted. It’s only saying Ready or NotReady. I have tried to store the PIN, but that doesn’t seem to help. The PIN works when I Arm, Disarm, Stay etc the alarm…so…it’s not storing the PIN or its not using it to retrieving the zone that is at fault?
EDIT: Zones are resetting now. For some reason the TTL was set to 1200000, lol…
I am still not able to get it to show the faulted zone when its in a NotReady state. When you store the PIN, is there any indicator that it is actually storing the PIN successfully?
I’ve created several test scenes for zones to trigger another event (outdoor lighting when a door is opened).
I also setup notifications so that I could see if it was triggering.
I got things working properly so I decided to remove the notifications.
Saved.
Notification was back in there again. This time twice.
Deleted.
Saved.
Back in there 3 times.
Deleted.
Saved.
Back in there 4 times.
So I decided to also delete the scenes that was testing to see if that would help.
Deleted the scene.
Saved.
Now the scene is back in there twice.
Deleted the scene.
Saved.
Now the scene is back 3 times.
…
I deleted the other test scene I had setup.
Same thing. Keeps replicating.
HALP! I got many copies of scenes and notifications. And they are all related/linked to the zones in some form or shape. I don’t know how to get rid of them.
EDIT: ACK! Every time I click to save a change (even on stuff totally different) it creates another instance of those 2 scenes. I have like 13 duplicates of 2 different scenes now. I can’t work on anything unless I want more duplicates to pop up. facepalm
Getting 42 text messages everytime someone opens that slider…agggghhhhhhH!!! lol
EDIT: The only way to fix it was to delete the entire partition and alarm panel module. Ill have to re-add everything and see how it goes this time.
EDIT:
I added the alarm panel back and all those dang scenes came back…ugh, I am so stuck…now they won’t even go away after deleting the alarm panel again.
@shep29, thanks for trying it out. I believe I’ve fixed the issue (when merging my UI5 changes into the UI4 branch, I accidentally copied the UI5 init function name). If you have a minute, download it and give it a try.
@mcvflorin, Does MCV have any Internet accessible UI4 devices that I could use for testing UI4 code? I haven’t been around long enough to aquire a collection of Vera’s (yet) like most of the other developers. If I had SSH access, it wouldn’t even need an AD2USB as I could just redirect ser2net over an SSH TCP tunnel back to the one I have here.
Hugh
@hugheaves Downloaded (although there was no option for downloading as a zip file) and seemed to install OK. Version now says 2.45. Can’t open Cheat Sheet tab though. Says “Opening Cheat Sheet…” Normally, I would have to click on the Cheat Sheet tab twice to get it to open but that’s not working anymore.
[quote=“Thinkfire, post:402, topic:168766”]I’ve also noticed that it’s not reporting the zone thats faulted. It’s only saying Ready or NotReady. I have tried to store the PIN, but that doesn’t seem to help. The PIN works when I Arm, Disarm, Stay etc the alarm…so…it’s not storing the PIN or its not using it to retrieving the zone that is at fault?
EDIT: Zones are resetting now. For some reason the TTL was set to 1200000, lol…[/quote]
The plugin displays only the partition status. Zones have their own device, so to see which zone is faulted just look at its device. If it’s a red running man then this means the zone is faulted/tripped.
If the zone hasn’t been faulted for at least 20 minutes (1200 seconds) then it is reset (it is set as not faulted/tripped). 20 minutes is the default OnTime value for the 3-in-1 sensors, so I decided to use the same value for this plugin’s sensors.
The PIN code is used for getting the faulted zones only if you have more than 1 partition.
As for your other issues, I don’t think they are caused by the plugin. Please enable Tech Support and submit a trouble ticket so I can investigate. I will check it out on Monday.
Thanks for trying (again!). Seems like a little improvement, at least it didn’t blow up right away. You mentioned that you’d copied my two new files from branches/UI4… Did you perchance copy the other files from branches/UI4 as well?
I’m asking because you may not have known there were actually other modified (future 2.45+) files in branch/UI4 that were there before I made my changes. If you didn’t grab all the files, you may now have an “out of sync” mix of code from the released 2.44 and (the yet to be released) 2.45+.
If that’s not the problem, I’m going to have to find a way to run my code on UI4. (I see that MCV’s selling some super cheap refurb Vera 2’s on ebay, so that might be an option
Hugh
@hugheaves
OK, I uploaded all files and can now get the Cheat Sheet with the new Address/Serial# and Channel/Loop # columns. Looking good!
Do I have to remove each of my 21 wireless zones and add them back in with the Serial #/Loop # in order for this to work? I don’t see an “edit” button
[quote=“shep29, post:408, topic:168766”]@hugheaves
Do I have to remove each of my 21 wireless zones and add them back in with the Serial #/Loop # in order for this to work? I don’t see an “edit” button :)[/quote]
Yeah, unfortunately, I didn’t try to add any edit functionality to the GUI. It probably makes sense to do so now that there’s more places to make a typo in the settings.
A work around is that if you add another device with the same zone number and click “Add”, the new settings will replace the existing settings for that zone. That way, you can at least cut and paste your existing zone name into the name field, add the serial no/channel info, and then just click “Add” to add the new settings.
The other way (much more risky, but useful is you have a lot of zones), is to manually edit the “Zone” variable itself. You can cut and paste the entire zone variable value into a text editor, make your changes and then paste it back into the Zone variable value. Beware that there is not much (if any) validation on the raw zone variable, so if you mess something up (add invalid chars, newlines, extra or missing delimiters, etc.) you’ll probably have to wipe the entire plugin and start over.
The format of the variable is:
ZoneNumber1-AddressOrSerialNumber1-ChannelOrLoopNumber1-ZoneName1;ZoneNumber2-AddressOrSerialNumber2-ChannelOrLoopNumber2-ZoneName2;ZoneNumber3-AddressOrSerialNumber3-ChannelOrLoopNumber3-ZoneName3
etc… Notice there is no semicolon after the last zone, and there are no line breaks.
Hugh
[quote=“mcvflorin, post:406, topic:168766”][quote=“Thinkfire, post:402, topic:168766”]I’ve also noticed that it’s not reporting the zone thats faulted. It’s only saying Ready or NotReady. I have tried to store the PIN, but that doesn’t seem to help. The PIN works when I Arm, Disarm, Stay etc the alarm…so…it’s not storing the PIN or its not using it to retrieving the zone that is at fault?
EDIT: Zones are resetting now. For some reason the TTL was set to 1200000, lol…[/quote]
The plugin displays only the partition status. Zones have their own device, so to see which zone is faulted just look at its device. If it’s a red running man then this means the zone is faulted/tripped.
If the zone hasn’t been faulted for at least 20 minutes (1200 seconds) then it is reset (it is set as not faulted/tripped). 20 minutes is the default OnTime value for the 3-in-1 sensors, so I decided to use the same value for this plugin’s sensors.
Also, I noticed the red guy in individual zones. Thats working.
The PIN code is used for getting the faulted zones only if you have more than 1 partition.
As for your other issues, I don’t think they are caused by the plugin. Please enable Tech Support and submit a trouble ticket so I can investigate. I will check it out on Monday.[/quote]
OK. Well I finally got them to go away permanently. I deleted the Alarm System altogether, readded it, the scenes all came back with it, but this time manually deleting them worked and they didn’t replicate like they were before. Recreated my zones. All seems fine, they haven’t come back. If you still want to take a peek, I would be more than happy to submit a ticket. Otherwise, I am good to go…for now.
I just thought I remembered the actual alarm panel box showing the faulted zone as well, I kind of liked that. As I have my zones scattered in different categories based on their locations, so I have to scrolled around to see which zone is currently faulted. That and each zone stays faulted for 20 minutes (per your default setting) so I can see multiple zones faulted even though they aren’t anymore. Any chance you can put the faulted zone back in the same back with the Ready/NotReady box where it shows the status?
@hugheaves
This update you did sounds great and was wondering where i can find it, or do i need to wait for the official release?
Thanks.
@hugheaves
OK, I installed all files and everything seems to be working properly. I added the serial/loop #'s for all my wireless zones. Now I guess the question is, what can I do with this new functionality? Ideally, I’d like to be able to get alerts from my motion sensors but only when my alarm is armed in Stay mode.
I’m agree with ThinkFire. I liked that the faulted zones showed, but it has since disappeared from the previous major release 
any chance it can be added back in?
@SteveZ, the latest code can be downloaded from code.mios.com:
UI5: trunk – Honeywell Ademco Vista Alarm Panels via AD2USB
UI4: UI4 in branches – Honeywell Ademco Vista Alarm Panels via AD2USB
If you decide to install, make sure you grab the latest versions of all the files, not just the ones I had modified. There are various ways to upload them. In UI5, you can upload the code using the Vera “Apps” tab. (Select “Apps” → “Develop Apps” → “Luup files”).
Before you jump in, keep in mind that:
[ul][li]MCV is unlikely to provide any support for problems you have with your Vera after you install this code (you would probably need to downgrade to the official release to get support)[/li]
[li]Once you upgrade, downgrading would probably require you to delete and reinstall the plugin, which would wipe any settings / config you have for the alarm panel[/li]
[li]There may be no upgrade path from this test version to the next official release. (unlikely, but theoretically possible if the internal data format changes between now and release)[/li][/ul]
I don’t want to scare you off, but want to make sure you understand the implications.
On the plus side, it would be nice to have a few more people trying out the new code.
Hugh
@shep29, glad you got it working. As you know, with the new code, Vera will see your motion sensors being triggered regardless of the arming mode of the actual partition. However, you can tell Vera whether to respond to these triggers using the arm/disarm mode of the individual motion sensor devices.
If you only want to see alerts in stay mode, I’d create two scenes: One that arms all the individual motion sensors with a trigger of the actual partition being armed in “stay” mode. And another that disarms the individual sensors when the partition is put in a mode other than stay. Then, you can use the triggers of the individual motion sensors to create your alerts, but specify that the triggers are only activated when the motion sensor is in the "armed’ mode.
Does that answer your question?
Hugh
@hugheaves
Ok, I set up two scenes. One triggers as an event when the alarm is armed in Stay mode and one triggers as an event when the alarm is in Ready mode (off). Then I set the command tabs for each scene to Arm and Disarm each motion depending on which event triggered (Arm for Stay and Off for Ready). Then I set up the notifications tab of each individual motion to alert me when an Armed motion is tripped. To test, I set my alarm to Stay, walked around the house to trigger the motions and the alerts started coming in! I hit my SMS alert quota quickly though so can’t test the Ready scene until tomorrow. Very cool! Thanks!
One thing I forgot to add is that I’m unsure of the addresses/channels of my hard wired zones # 1-8 so can’t set those up. Any insight on that? Just realized those need to be set up in the panel programming from one of your older posts where you reference one of the Nutech forums here http://www.nutech.com/index.php?option=com_fireboard&Itemid=74&func=view&id=656&catid=4#656
Update OK I tried programming the relays for my hardwired motion detector zones # 5-8 according to the instructions in my Vista 20P manual and using the Nutech site but no dice. I keep getting a “Check 112 Error Relay Module”. From what I can tell, 112 refers to the Address/Channel I put in, which was 12/1, 12/2, 12/3 and 12/4. Seems like it is looking for the physical relay wired to my panel. Do you have to do something to special to tell the panel that these are virtual relays?
Would it be OK if the status of the zones were shown in the Cheat Sheet?
Did you turn on the virtual relay support in the AD2USB itself? I believe it’s turned off by default. If you haven’t already, you’ll need to use a terminal emulator to access the AD2USB USB serial port directly, and use the “!” menu command to turn on the virtual relay devices in the AD2USB.
No I didn’t and my PC crashed yesterday so I can’t hook up to the AD2USB to change settings! I hijacked my wife’s Mac Book Pro but having trouble getting the virtual keypad GUI to recognize the AD2USB in the USB slot. Scanning the Nutech forums now for a solution…
You can also program the AD2USB while it’s still connected to your Vera from the Vera command line. (via SSH). The commands are:
-
Connect to Vera via SSH:
[tt]ssh root@Your.Vera.IP.Address[/tt]
-
Stop the Luup stack: (command may be different on UI4)
[tt]/usr/bin/Stop_cmh.sh[/tt]
-
Start ser2net to connect to the AD2USB and listen on TCP port 4444 in telnet mode
[tt]ser2net -C “4444:telnet:0:/dev/ttyUSB0:115200 1STOPBIT NONE”[/tt]
-
Telnet to port 4444 (i.e. connect to ser2net / AD2USB):
[tt]telnet localhost 4444[/tt]
-
Configure AD2USB with the “!” command. When done press “Ctrl-]” and then “e” to exit telnet
-
Reboot:
[tt]reboot[/tt]
On UI5, here’s what it looks like:
[code]razor:~ hugh$ ssh root@veralite
root@MiOS_35002000:~# /usr/bin/Stop_cmh.sh
OK
root@MiOS_35002000:~# ser2net -C “4444:telnet:0:/dev/ttyUSB0:115200 1STOPBIT NONE”
root@MiOS_35002000:~# telnet localhost 4444
Entering character mode
Escape character is ‘^]’.
!REL:13,03,01
[0000000100000000----],007,[f70000051007000008020000000000],"FAULT 07 "
!REL:13,03,00
[1000000100000000----],008,[f70000051008001c08020000000000],"DISARMED Ready to Arm "
!>Keypad Address (18) :>
!>Code (0000) :>
!Zone Expanders Y/N Max allowed: 02
!>expander module #01 ZN 09-16 (N) :>
!>expander module #02 ZN 17-24 (N) :>
!>expander module #03 ZN 25-32 (N) :>
!>expander module #04 ZN 33-40 (N) :>
!>expander module #05 ZN 41-48 (N) :>
!Relay Modules Y/N Max allowed: 04
!>relay module #01 (Y) :>Y
!>relay module #02 (Y) :>Y
!>relay module #03 (Y) :>Y
!>relay module #04 (Y) :>Y
!>Emulate Long Range Radio Y/N: (N) :>N
!>Address Filter Mask (ffffffff) :>
!>Deduplicate (N) :>
!Reading configuration.
!UART init.
[1000000100000000----],008,[f70000051008001c08020000000000],"DISARMED Ready to Arm "
Console escape. Commands are:
l go to line mode
c go to character mode
z suspend telnet
e exit telnet
root@MiOS_35002000:~# reboot[/code]