PLUGIN: Ademco Vista Alarm Panel with EVL3

Plugins & Plugin Development Unmaintained
, ,
101

See the first post, under manual insallation - step 2.

I was afraid of that…

Testing would help considerably…

If you could first turn on debug mode and arm the panel in away and post the log… so I can see what’s going on…
Then turn off chime mode and rearm… so we can verify that it is chime mode causing the issue…

Once I look at the log, I should be able to see the problem…

Thanks.[/quote]

Done as requested! The log files are attached. Chime doesn’t seem to affect the issue.

Also, I apologize if I did this incorrectly, but I think it’s right. If not, just let me know and I can try again. :slight_smile:

102

If you have the ip address correct, and the EVL3 password correct… It should connect to the EVL3 and work…

The fact that it is not means something out of the ordinary is going on… You need to post logs… Turn on debug mode, then reload the LuaUPnP engine… and post the logs from the restart onwards…

You have the IP address and the EVL3 password correct… The screenshot show “EVL3 FW: 01.11.136A”, which is obtained by fetching the EVL3 webpage (which requires IP address and password)… So that means that something fishy is going on… Please post logs as above…

PERFECT!!!

Nope… not chime mode!!

I was having issues with Imperihome on my tablet not displaying the arm modes correctly… It has a different interpretation of the DetailedArmMode values (and I use the wall and desk tablets more than I use the Vera web interface)… So, I added a translation table to the plugin so that the mode names that are used by the panel are translated into either the values used with the Vera web interface or the values used with the Imperihome android app. The Vera translations are normally used and the Imperihome translations are used when the plugin detects that the Imperihome companion plugin is installed on the Vera… Well… It seems I made a error and got the translation tables backwards!!! Oppsie… 8-}

Unfortunately, I don’t have access to the computer with the development files for the next several days… BUT, as a work-around (and a test)… could you try installing the Imperihome plugin from the app marketplace… You do not need to use the Imperihome android app, just the presence of the plugin will trigger that use of the other translation table. It will create an imperihome device but will not have any other deleterious effects and can be removed once I fix the tables. I may have the translation tables totally screwed up, but the “Away” button, “Stay” button and “Disarmed” buttons should work…

Let me know if that solves the issues or not, and if it creates more issues.

103

I will post logs. Can someone provide a link to the easiest method to view and download logs (sorry, new here). Thanks.

Just to confirm, the interface password is the four digit code typed into the keypad preceding a manual arm/disarm sequence and installer code is the four digit code typed into the keypad prior to keypad programming (four digit code followed by 800), correct?

The only password I have for EVL3 is the pw to access the eyez-on site.

104

[quote=“chicagodan, post:103, topic:183436”]Just to confirm, the interface password is the four digit code typed into the keypad preceding a manual arm/disarm sequence and installer code is the four digit code typed into the keypad prior to keypad programming (four digit code followed by 800), correct?

The only password I have for EVL3 is the pw to access the eyez-on site.[/quote]

No.

The four digit code used to arm/disarm is an alarm panel user code. User codes do not exist on a factory fresh alarm panel, and must be programmed into the panel before they can be used.

The four digit code used for programming the panel IS the Installer code. It is factory set to 4112, and the plugin will use this as default if not defined in the plugin.

The eyez-on site password is the eyez-on site password.

The interface password is the password needed to log into the EVL3 web interface on your local network… IE: your EVL3 has an IP address of 192.168.1.2, you go to http://192.168.1.2 in a browser, the EVL3 displays a status and configuration website… The default passwork is “user”… This password is also used as the password for the TPI interface that the plugin uses… If you have not changed the interface password from the EVL3 web interface, you can leave the entry in the plugin blank and it will use the default password.

The interface password and installer code are set on the setup page for the alarm PANEL device (the device used for configuration).

The User codes are set in the PARTITION device (the device used for arm.disarm control), in the box market PIN CODE.

105

Got it. Huge help and thanks. Will try again tonight.

106

If you have the ip address correct, and the EVL3 password correct… It should connect to the EVL3 and work…

The fact that it is not means something out of the ordinary is going on… You need to post logs… Turn on debug mode, then reload the LuaUPnP engine… and post the logs from the restart onwards…

You have the IP address and the EVL3 password correct… The screenshot show “EVL3 FW: 01.11.136A”, which is obtained by fetching the EVL3 webpage (which requires IP address and password)… So that means that something fishy is going on… Please post logs as above…

PERFECT!!!

Nope… not chime mode!!

I was having issues with Imperihome on my tablet not displaying the arm modes correctly… It has a different interpretation of the DetailedArmMode values (and I use the wall and desk tablets more than I use the Vera web interface)… So, I added a translation table to the plugin so that the mode names that are used by the panel are translated into either the values used with the Vera web interface or the values used with the Imperihome android app. The Vera translations are normally used and the Imperihome translations are used when the plugin detects that the Imperihome companion plugin is installed on the Vera… Well… It seems I made a error and got the translation tables backwards!!! Oppsie… 8-}

Unfortunately, I don’t have access to the computer with the development files for the next several days… BUT, as a work-around (and a test)… could you try installing the Imperihome plugin from the app marketplace… You do not need to use the Imperihome android app, just the presence of the plugin will trigger that use of the other translation table. It will create an imperihome device but will not have any other deleterious effects and can be removed once I fix the tables. I may have the translation tables totally screwed up, but the “Away” button, “Stay” button and “Disarmed” buttons should work…

Let me know if that solves the issues or not, and if it creates more issues.[/quote]

That did it! The Imperihome app’s presence seems to have temporarily solved the problem. I have working scenes now! Thank you very much for the assistance.

On a more serious note, I want you to know how grateful I am that you took the time to not only write this plugin, but to support it. It may seem trivial to some, but it’s become a critical piece in my home security and automation system, which provides a great deal of peace-of-mind and convenience to me. I’d like to show some genuine support - if there’s a way I could send a donation, or buy a license, please shoot me that info so I can do so.

107

Excellent!!! I will make the repairs to the translation tables as soon as I can…

I’m glad my efforts have contributed, in a small way, to you and your family’s piece of mind. 8-}

I’m sorry, but this plugin is NOT licensed for sale!! 8-}

Seriously, the offer is greatly appreciated, but is not in any way necessary… If you have the insatiable urge to make a donation, make it to a worthwhile charity - your local childrens hospital or food bank or some other organization that can make a genuine difference in your community.

108

What’s the easier way to review and send logs? Still no luck…

109

Bump
Is there any way to send an exit delay restart (*)? This can be done from the EyesOn login but I don’t see a way using the local Envisalink access or this plugin.

110
  1. Use Putty, or another SSH client to log into your Vera… issue “tail -f /var/log/cmh/LuaUPnP.log” command… copy the output into a forum reply.
  2. Use the Vera UI… In a browser, go to "http://(your Vera IP Address)/cgi-bin/cmh/log.sh?Device=LuaUPnP (This is NOT a good method!)
  3. Install the InfoViewer plugin… It has amazing log capture powers…

See the WIKI http://wiki.micasaverde.com/index.php/Logs for details on logging.

[quote=“sasaba, post:109, topic:183436”]Bump
Is there any way to send an exit delay restart (*)? This can be done from the EyesOn login but I don’t see a way using the local Envisalink access or this plugin.[/quote]

Having the plugin send the command is not an issue… being able to add it to the user interface is a different issue entirely… I have added the request to the to-do list.

111

Understood about adding additional functionality and that it is not trivial. Appreciate all the effort you have put in on this plugin and the consideration for possible future incorporation of this request.

112

cybrmage
I still seem to have issues every 1 to 3 days where the plugin is not talking to the EVL3. Even through multiple reloads. A Vera reboot fixes the issue.

If you can add a method so we can detect the lack of communications this would be great… then we can use a native Vera scene to watch for this and force a system reboot.

thanks!

113

[quote=“Aaron, post:112, topic:183436”]cybrmage
I still seem to have issues every 1 to 3 days where the plugin is not talking to the EVL3. Even through multiple reloads. A Vera reboot fixes the issue.

If you can add a method so we can detect the lack of communications this would be great… then we can use a native Vera scene to watch for this and force a system reboot.

thanks![/quote]

Unfortunately… if there is still some obscure bug causing the plugin to crash, the plugin is no longer running and will not be able to trigger any method to indicate that it has crashed… So… ideally… find the cause 8-}…

When the plugin stops communicating with the EVL3… How do you know??? Does the plugin raise an error when you try to arm/disarm? is there any message in the info box???

The next time you notice that the plugin has stopped communicating, if you check the LuaUPnP logs to see if anything is amiss…

I finally have my panel and VeraLite installed and, so far it has not stopped communicating… but it’s only been a few days…

114

perhaps it may be desirable to run a watchdog (3mn countdown loop) to clear/reSync the plugin automatically when the EVL3 Coms or panel go unresponsive… From normal I/O processing you could jump back out to “get a clean pipe” from power-on initialisation…

115

Thanks for the plugin! I’m just getting started but it seems great so far!

I just wanted to share an issue I had which was mostly my own fault. I changed the default password on the EVL3 and didn’t notice that it truncates the password at 6 characters. I was using a longer password but never got an error so I suppose the local authentication box was truncating the password too. But the EVL3 plugin for the Vera was sending the whole password and getting an incorrect password error. Very easy to fix but very annoying to troubleshoot.

116

Hmmm… I never noticed it either (never bothered to change the default password)… Thanks for the report… Added to the to-do list.

117

I just got my HA system and Vista 20p this weekend and all installed. Everything came except the battery for the panel :frowning: so of course my keypads show batt level low all the time.
When I try to configure the plugin it sees the EVL3 and gives the firmware version, but when I try to read the config, it either says the panel is in an UNKNOWN state, or bad installer code. I know these are correct.

When I SSH into the box, I do see that every few seconds it popus up the low battery line, then back to ready to arm over and over. Could this low battery warning be throwing off the plugin? I’m hoping the battery will show up any day now, but its coming through USPS so there’s no telling.

Anyway, Thank you for the plugin and I can’t wait to get it fully running.

118

So this means that the panel is in a mode that the programming routine does not recognize…

The trouble reports may be the cause of the inability to program the panel… If the EVL3 sends a trouble report when the programming routine is testing the panel mode, it may be interpreted as an unknown mode, or bad installer code.

Because the panel read/programming routines CAN be destructive to the panel, it will not proceed if it receives data that it does not recognize… It’s a pain in the a**, but it better than having a panel that no longer functions correctly…

please provide details of your panel config, and excerpt from the log showing some of the communication with the EVL3.

119 
52      01/28/15 11:22:46.561   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:22:50.572   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:22:54.063   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:22:58.064   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:02.064   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:23:06.065   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:10.066   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:23:14.067   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:18.068   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:23:22.068   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:26.069   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:23:30.070   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:34.071   intercept 0x762f4c44: 0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:23:38.071   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:42.072   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:23:45.573   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:49.574   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:23:53.575   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:23:57.575   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>
52      01/28/15 11:24:01.576   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x20 0x44 0x49 0x53 0x41 0x52 0x4d 0x45 0x44 0x20 0x43 0x48 0x49 0x4d 0x45 0x20 0x20 0x20 0x52 0x65 0x61 0x64 0x79 0x20 0x74 0x6f 0x20 0x41 0x72 0x6d 0x20 0x20 0x24 (%00,01,5C28,08,00, DISARMED CHIME   Ready to Arm  $) <0x744ea520>
52      01/28/15 11:24:05.577   0x25 0x30 0x30 0x2c 0x30 0x31 0x2c 0x35 0x43 0x32 0x38 0x2c 0x30 0x38 0x2c 0x30 0x30 0x2c 0x53 0x59 0x53 0x54 0x45 0x4d 0x20 0x4c 0x4f 0x20 0x42 0x41 0x54 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x24 (%00,01,5C28,08,00,SYSTEM LO BAT                   $) <0x744ea520>

This is what i see over and over. There is one part where I told it to read panel in there. I really think this is whats keeping me from getting any farther.

I have a Vista20p
2 6162 keypads, addressed 16 and 17.
EVL3 addressed at 18
I have 1 hard wired zone expander.
zone 1 - fire
zone 2-4 doors
zones 8 motion
zones 5,6,7 and 9-13 are windows.

120

That data (with the “52” at the beginning) is the raw data being processed by the Vera…

The data being processed by the plugin will be prefixed with “50” and will contain “EVL3VistaAlarmPanel::”…

If you do not see any of these lines in the log, reload the LuaUPnP engine while watching the logs and look for any lines (in red) that indicate a failure…