don’t wory about the ip issue for now, the plugin is not yet fonctional.
You can try setting Ip manualy because dhcp is not your friend for infrastructure devices such as Vam or Vera. So use hard set ip and populate manualy until you hit the next batch of issues.
I have a static ip for my vam so Im not using the DHCP but when I try and set it manually in the plug in it tells me "No Implementation and I cannot set the ip for it. any suggestions?
Are and Vam both in the same Ip domain … 192.168.1.xxx?
try to let plugin discover ip then also try manually seting it…
I don’t recall having many issues with the ip detection. The problem is after once the plugin talks to the Vam… not a whole lot of useful stuff comes out: my vista zones were never picked up.
I did that and the plug in finds my Honeywell wifi thermostat instead of the VAM…so weird
we need the developer back !! May be Santa can help fulfill our wishes???
It is a tall order to make something like that work on spare time. So many things need to be done right…
I just uninstalled the plug in and reinstalled and now it found my vam…I can arm disarm through micasa but don’t see any zones listed and I have my installer pin set…what now? Is this all this does?
Note to all: Since mid November I have been dealing with several major issue at work, a new job (with the same company) and a long distance change of domicile. This has left me with very little spare time, only occasional and very brief internet access, and no access to a functioning Vera system to do any development. This will continue until I am settled into the new home and job, and I can install all my toys. The plugin has not been abandoned. I will be back… may be a bit though.
The issue with no zones being loaded is that the VAM is not reporting a partition. If you log into the VAM web interface and go to the security page… There should be a box in the lower left hand corner that says “P1 H” or “P2 H” or “P3 H”. This indicated which partition the VAM is currently controlling (the “P1”, etc) and weither the partition is the “Home” partition for the VAM. When you first log into the VAM interface, it should show the home partition (ie: my unit displays “P1 H”, as my VAM is configured for partition 1). If it does not display the partition indicator OR it does not display the “Home” indicator for a partition, then the API will not report the home partition to the plugin. Without the home partition being reported, the plugin does not attempt to retrieve the zone list (as the API command for the zone list needs the partition number and is not reliable without it).
This situation indicates that your VAM is not correctly configured to the panel, or the panel is not correctly configured for the VAM. Make sure the ECP address that is set for the VAM is the address that was configured in the panel. Make sure that the ECP address that you will use in the panel (It is programmed under AUI - addresses 2,3,5 or 6 - not under keypads) is programmed for remote services and for the correct partition.
Once I have access to my development system, I will add a “use at your own risk” option to ignore the partition report and continue with the zone data…
Hi CybrMage, thank you for all the good things you do besides hardworking during the day…
I can confirm my VAM properly shows P1H but Ademco VistaPNL zones never got populated in the plug-in… so there must be another issue standing across the way in your design. FYI, as it is my VAM controler works as designed with PNL, limited but quite stable unit.
I don’t know too much about debugging in VERA environment but I am sure it’s no picknick for developers to work with as the Linux CL console only provides limited extra criptic information.
Looking forward to you finding time for VAM plugin. Txs
Hi…
Here is a quick-and-dirty test release… If the VAM fails to send a partition list, it assumes that P1 is the home partition, creates the data structures needed and (hopefully) continues…
This should let the plugin complete the startup and start processing data from the VAM… In the long term, I would still prefer to determine what is causing your VAM to not send the partition information… did you verify the AUI configuration in your panel? what was the result?
Upload the attached file to your Vera (Apps/Develop Apps/Luup Files) and try to capture the complete log of the startup process…
As you pointed out, the problem might be on the AUI side…
I have 3 physical keypads (6150, 6160, 6160V) plus 1 virtual keypad for AlarmNet LRR/remote UI, plus the VAM itself. While it is not typical on bare-bone installs, the latest Vista 20P ROM supports even more AUI (5?) than the original ROM (2?). So this config works perfectly.
As far as testing, I am a little shy right now since I have some traveling plans. I don’t want my system to crap out while I am remote.
[quote=“ElGringoCurioso, post:31, topic:184006”]As you pointed out, the problem might be on the AUI side…
I have 3 physical keypads (6150, 6160, 6160V) plus 1 virtual keypad for AlarmNet LRR/remote UI, plus the VAM itself. While it is not typical on bare-bone installs, the latest Vista 20P ROM supports even more AUI (5?) than the original ROM (2?). So this config works perfectly.[/quote]
The three keypads shoud be configured for ecp addresses 16,17 and 18, and should not affect the VAM. The Alarmnet LRR/remote UI (I’m assuming TC2) should use one AUI address… but may use more (likely a RIS address)
The VAM takes takes two ecp addresses - one AUI address and address 25 (for RIS and TC2). I can not find clear documentation on what addresses the alarmnet services require but will do some more digging… The Alarmnet/TC2 service may be set as primary RIS, requiring the VAM to be reconfigured to a secondary address…
Completely understandable… Have a safe trip, and test at your convenience…
I wanted to say thanks for developing this plugin and let you know that I have been unable to get the plugin to download and create zones with my current set up.
So far I have the VeraEdge and a Vista 21ip (ip 192.168.1.5) and the VAM (ip 192.168.1.35) sort of talking through your plugin. I had to uses version 1.1 of the plugin to even get the software speaking to each other. The plugin continually detects the Vista panel thinking it is the VAM so I had to utilize ver 1.1 and set the ip manually. Once that is complete and the luup engine reloads several times and I reboot the Vera unit I am able to arm and disarm the Vista panel through the Vera but I still get zero zones loaded.
Does this module/plugin give zone status updates while the alarm system is armed?
I don’t believe so only actual Alarms and not Faults can be picked up while armed. As I understand this is a limitation caused by the properly secured interface between the Vam and Panel.
Honeywell does not want anyone to get into their turf and start exposing engineering issues or building competing services when all they want is to create a money pump at $30/month for their partners/customers.
Long story short… I don’t believe you can access any zone FAULT conditions while PNL is Armed to activate your Vera logic… even if you succeed in retreiving Zone Labels out of the VAM. On the flip side, Fault conditions can be used inside the VAM, 10Max or so.
ElGringoCurioso: Are you done with your travelling??? If so, let me know if your wish to resume testing to resolve the issues you were having…
I don’t have a 21iP, and the ones I had access to had the IP communicator disabled… Are the first pairs in the MAC address the same between the 21iP and the VAM???
I still don’t know why the zones are reported by my VAM and not by others… Not enough testing…
The 1st 3 pairs are the same.
Yep I am good txs CybrMage
I took a brake away from Vera as it has been functional in its current state while on UI5. I’ve used that time away to shoehorn OMNIROM 5.1.x and TWRP recov from XDA-Dev in my favorite Android devices and breath new life into them.
What I’d be most interested in is a work-around to the limit of 10 actions Max on the VAM as I now really dig triggering my Zwave lights based on Vista zone Faults while PNL is Armed such as “Bedroom motion triggers BathRm lights On for 3 mn”.
Meanwhile to get my hands dirty with the limitless Pleg logic, I have built a practical “mickey-mouse” style interface to pass Vista status to Vera simply by setting different AC temps on Tstat (VAM sets unused AC_Temps according to its Status then my VeraLt Pleg logic decodes/interprets AC_Temps as: Armed, Disarmed, Away etc…). Works great!
I guess if I could capture Vista status through your PlugIn, I’d be able to reclaim some VAM Actions steps now used to pass Status to AC_Temps… This relies entirely on intraNet beeing stable between Vera and VAM where my current AC_Temp I/F does not rely on network at all (one less i/f failure point).
Nonetheless thanks a lot for enhancing the current limitations put in place by Honeywell.
Yep I am good txs CybrMage
I took a brake away from Vera as it has been functional in its current state while on UI5. I’ve used that time away to shoehorn OMNIROM 5.1.x and TWRP recov from XDA-Dev in my favorite Android devices and breath new life into them.
What I’d be most interested in is a work-around to the limit of 10 actions Max on the VAM as I now really dig triggering my Zwave lights based on Vista zone Faults while PNL is Armed such as “Bedroom motion triggers BathRm lights On for 3 mn”.
Meanwhile to get my hands dirty with the limitless Pleg logic, I have built a practical “mickey-mouse” style interface to pass Vista status to Vera simply by setting different AC temps on Tstat (VAM sets unused AC_Temps according to its Status then my VeraLt Pleg logic decodes/interprets AC_Temps as: Armed, Disarmed, Away etc…). Works great!
I guess if I could capture Vista status through your PlugIn, I’d be able to reclaim some VAM Actions steps now used to pass Status to AC_Temps… This relies entirely on intraNet beeing stable between Vera and VAM where my current AC_Temp I/F does not rely on network at all (one less i/f failure point).
Nonetheless thanks a lot for enhancing the current limitations put in place by Honeywell.[/quote]
At this point I am most interested to capture Vista Zone Faults while Armed… and not so much managing Vista: Arm/DisArm activities from Vera UI.
I am under the impression this can Not be done with VAM plugIn but perhaps the EVL3 integrarion allows to capture Zone Faults while Armed ???
Sent from my GT-P3110 using Tapatalk