AD2USB over network / ethernet

[andreimios]

Hi all,

I updated the last plugin version with changes suggested by hugheaves in order to add this feature to the official plugin but I did it "blindly"(we don't have this alarm panel at the office) and I need someone to confirm that works before I update the plugin on apps.mios.com.
I added "overNetwork" variable that is set to "0" by default for using the plugin without the new feature added. You will need to change it to "1" in order to use the "over network" feature (but not before you follow the instructions provided in the first post).

Let me know if the version attached is working and if so, I will update the plugin and release a new version.

Best Regards,

- Andrei -

[Theboob]

Hi there. Just wondering if there are any pros/cons to this setup vs just using an EVL-3 with the other plugin? I'm trying to decide between a DSC or Honeywell panel. And whether to use EVL-3 or not.

Thanks.

[xuniman]

I tried testing this today with your April file above. My Vera with UI7 just went into a reboot loop.

Here is the log snippet:
50   04/29/15 15:12:09.393   luup_log:19003: Honeywell Ademco Vista Alarm Panel Plugin version 2.45 <0x2bfce680>
06   04/29/15 15:12:09.393   Device_Variable::m_szValue_set device: 19003 service: urn:micasaverde-com:serviceId:VistaAlarmPanel1 variable: PluginVersion was: 2.45 now: 2.45 #hooks: 0 upnp: 0 skip: 0 v:0x1184da8/NONE duplicate:1 <0x2bfce680>
01   04/29/15 15:12:09.394   GetLuaInterface can't find device type: 4/0x1333b80 str: 0 <0x2bfce680>
01   04/29/15 15:12:09.395   luup_variable_get interface 0x12fb228 args 4 <0x2bfce680>
50   04/29/15 15:12:09.395   luup_log:19003: (VistaAlarmPanel::getDebugMode) Debug mode disabled. <0x2bfce680>
50   04/29/15 15:12:09.396   luup_log:19003: (VistaAlarmPanel::getNumPartitions) Number of partitions = 1. <0x2bfce680>
09   04/29/15 15:12:09.400   Child_Devices::ProcessChildDevice deleting device 19049 id vista_partition_1 room 0 desc Ademco Vista Partition 1 under 19003 topmost parent 19003 because type o:urn:schemas-micasaverde-com:device:VistaAlarmPartition:2!=n:urn:schemas-micasaverde-com:device:AlarmPartition:2 or file o:D_VistaAlarmPartition1.xml!=n:D_VistaAlarmPartition1.xml embedded o:0!=n:0 ok:0/1 <0x2bfce680>
06   04/29/15 15:12:09.469   Device_Variable::m_szValue_set device: 19050 service: urn:micasaverde-com:serviceId:VistaAlarmPanel1 variable: KeypadAddresses was: EMPTY now:  #hooks: 0 upnp: 0 skip: 0 v:0x1186578/NONE duplicate:0 __LEAK__ this:61440 start:155648 to 0x14c1000 <0x2bfce680>
09   04/29/15 15:12:09.479   Child_Devices::ProcessChildDevice created device 19050 id vista_partition_1 under 19003 topmost parent 19003 <0x2bfce680>
06   04/29/15 15:12:09.481   Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastDongleBackup was:  now:  #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x2bfce680>
01   04/29/15 15:12:09.593   UserData::WriteUserData saved--before move File Size: 27810 save size 27810 <0x2bfce680>
02   04/29/15 15:12:09.594   UserData::TempLogFileSystemFailure start 0 <0x2bfce680>
02   04/29/15 15:12:09.620   UserData::TempLogFileSystemFailure 5026 res:1

I've attached the longer version if that will help. Now I just need to figure out how to get the vera back in service.

[xuniman]

I'll try and post the full log file again.

I tried hugheaves original luup file in post 1 and it causes the same kind of perpetual restart loop.

[andreimios]

Hi xuniman,

Thank you for testing this. There was an issue in the L_ file when creating the alarm partition device, device file specified in L_ file was different then the one in D_ file and this caused the reboot loop. I attached another L file that should fix this. Please test this and let me know if it worked. You can PM or email me after you finish the tests.
Thank you again for your support.

All the Bests,

- Andrei -

[andreimios]

Hi all,

With xuniman help, a new plugin version that include the support for over network / ethernet implemented by hugheaves. The instructions for configuring the plugin can be found on my earlier post.

All the Bests,

- Andrei - 

[hugheaves]

Hi all,

With xuniman help, a new plugin version that include the support for over network / ethernet implemented by hugheaves. The instructions for configuring the plugin can be found on my earlier post.

All the Bests,

- Andrei -

Hi Andrei,

Is this plug-in version supposed to work with UI5, or is it a UI7 only version? I tried version 3.82 to my UI5 veralite using the test-plugin link: http://apps.mios.com/test-plugin.php?id=968&show=versions but I'm getting a Lua error on startup. (see screenshot) There's no obvious Lua error in the logs.

Also, what's the purpose of the "overNetwork" setting? As far as I can tell, it just changes the location of the PIN code storage from /etc/cmh-ludl/havsc to /tmp/havsc. The determination of whether or not to use the network connection seems to be still based on whether or not the "ip" luup variable is set (or not). Currently, my "overNetwork" setting is set to "0', but I'm still connecting over the TCP/IP network to the panel.

Hugh

[andreimios]

Hi hugheaves,

Is this plug-in version supposed to work with UI5, or is it a UI7 only version? I tried version 3.82 to my UI5 veralite using the test-plugin link: http://apps.mios.com/test-plugin.php?id=968&show=versions but I'm getting a Lua error on startup. (see screenshot) There's no obvious Lua error in the logs.

This is due to luup.set_failure at the end of the startup function, it should be there only for UI7. My bad, I forgot to check this.

Also, what's the purpose of the "overNetwork" setting? As far as I can tell, it just changes the location of the PIN code storage from /etc/cmh-ludl/havsc to /tmp/havsc. The determination of whether or not to use the network connection seems to be still based on whether or not the "ip" luup variable is set (or not). Currently, my "overNetwork" setting is set to "0', but I'm still connecting over the TCP/IP network to the panel.

I tried to include the changes form our first post into plugin and this was the only difference I noticed. I don't have this alarm panel and I don't know how it should work. I did the changes and I asked some users to test it. Based on the feedback I got, I decided to publish the new version, but it seems that it was causing problems for some users, so I removed it from apps. This is another reason for letting you maintain the plugin. I tried to help when I found some time between my task but the result was not the on I expected, so I will let you handle the plugin.

All the Bests,

- Andrei -

[BillFulton]

OK, I feel like I must be the only who can't get this to work.

I installed the AD2USB from the App tab (version 3.12) on a Vera Edge running UI7 (1.7.1320). I do not have the IODevice field in the advance/variables tab. It showed for a brief second and when I set it to 0 it disappeared. I do have a commUse field that is set to RS232 and I can't get it change.

I've rebooted, reloaded Luup and refreshed the page many many times.

I have the IP entered correctly.

I have the AD2PI with a PI running perfectly on my network. I can access it from internal and external with my phone or laptop.

The Vera Edge is working fine running several devices and scenes.

Here's the kicker, I can use the Envisalink plugin fine. I prefer to use the AD2Pi and shelve the Envisalink but can't get it to work.

I'm certain I've done everything in this post at least 14 times.

Any help is greatly appreciated.

[Vandamme23]

I'm using Vera Edge, Raspberry Pi, and a AD2USB... Trying to get the Edge to connect to the AD2USB through the network.  Installed the latest Vera plug-ins and the .lua files from this thread, and can't get the new settings to show...  Any help would be appreciated...  Haven't been able to locate any step-by-step instructions, so I will document my journey here...

I keep finding(through Google) bits and pieces so I'll try to document what I have done so far...

---Raspberry Pi
1. Attach AD2USB to USB port
2. Installed ser2net...  'sudo apt-get install ser2net'
3. Installed monodevelop...  'sudo apt-get install monodevelop'
4. Installed AlarmDecoder Keypad...  download here -  http://www.alarmdecoder.com/wiki/index.php/AlarmDecoder_Keypad
5. Configure and test Alarm using AlarmDecoder Keypad

---Vera
1. Installed AD2USB plugin
2. Uploaded latest, patched L_VistaAlarmPanel1.lua from this thread


Feel free to help out with the next steps...

[krayola]

I'm using Vera Edge, Raspberry Pi, and a AD2USB... Trying to get the Edge to connect to the AD2USB through the network.  Installed the latest Vera plug-ins and the .lua files from this thread, and can't get the new settings to show...  Any help would be appreciated...  Haven't been able to locate any step-by-step instructions, so I will document my journey here...

I keep finding(through Google) bits and pieces so I'll try to document what I have done so far...

---Raspberry Pi
1. Attach AD2USB to USB port
2. Installed ser2net...  'sudo apt-get install ser2net'
3. Installed monodevelop...  'sudo apt-get install monodevelop'
4. Installed AlarmDecoder Keypad...  download here -  http://www.alarmdecoder.com/wiki/index.php/AlarmDecoder_Keypad
5. Configure and test Alarm using AlarmDecoder Keypad

---Vera
1. Installed AD2USB plugin
2. Uploaded latest, patched L_VistaAlarmPanel1.lua from this thread


Feel free to help out with the next steps...

I had to add the overNetwork setting in UI7 manually:

Panel device > Advanced ... New Service/Variable
New Service: urn:micasaverde-com:serviceId:VistaAlarmPanel1
New Variable: overNetwork
New value: 1

I also had to set "ip" on the Params tab to my RPI ser2net ip:port

Then I had to go to the partition device and set the KeypadAddresses to 16,18

I still get "Can't Detect Device" despite it working so far.  Now to sort out the PIN storage problem I'm having.

[Vandamme23]

Thx krayola,  Those final steps have me up and running.  The full rundown is below...

Edge, Raspberry Pi, and a AD2USB.

---Raspberry Pi
1. Attach AD2USB to USB port
2. Installed ser2net...  'sudo apt-get install ser2net'
3. Installed monodevelop...  'sudo apt-get install monodevelop'
4. Installed AlarmDecoder Keypad...  download here -  http://www.alarmdecoder.com/wiki/index.php/AlarmDecoder_Keypad
5. Configure and test Alarm using AlarmDecoder Keypad

---Vera
1. Installed AD2USB plugin (It creates 2 devices, one for Panel, one for Partition)
2. Uploaded latest, patched L_VistaAlarmPanel1.lua from this thread
3.  On the Panel device add the overNetwork setting in UI7 manually:
Panel device > Advanced ... New Service/Variable
New Service: urn:micasaverde-com:serviceId:VistaAlarmPanel1
New Variable: overNetwork
New value: 1
4.  On the Panel device change the 'ip' variable to the ser2net ip:port from your raspberry pi
5.  On the Partition device set the KeypadAddresses to 31(yours may be different)

[kevinnutech]

Just FYI, if you use ser2sock in raw device mode instead of ser2net you can run the AlarmDecoder Keypad software at the same time as the Vera because it can share the socket stream with more than one device at the same time.

[kevinnutech]

Hi,

So I've done a little work on the file in this thread to make it support some firmware changes in the 2.8 branch.  In my lab I've gotten this to work following these instructions:

---Vera
1. Installed AD2USB plugin (It creates 2 devices, one for Panel, one for Partition)
2. Uploaded latest, patched L_VistaAlarmPanel1.lua from this thread
3.  On the Panel device add the overNetwork setting in UI7 manually:
Panel device > Advanced ... New Service/Variable
New Service: urn:micasaverde-com:serviceId:VistaAlarmPanel1
New Variable: overNetwork
New value: 1
4.  On the Panel device change the 'ip' variable to the ser2sock ip:port from your raspberry pi
5.  On the Partition device set the KeypadAddresses to 31(yours may be different)

On the raspberry pi, I use our image from alarmdecoder.com with the ser2sock already running (no need for ser2net or any modifications on the pi side if you are using our image) - I prefer ser2sock as it is multicast, so I will always use that in our lab.

[mrwildbob]

Hi Kevin,

I installed per instructions above.  The plugin works and I am able to control the panel via partition device but I keep getting Can't Detect Device for the panel device.  Any ideas?

Also, after 20 days or so, I have to reboot the RPi becuase Vera/Keypad App is not able to connect to it.  Do you know where I can find any logs that might clue me into why it is failing?  The RPi is up to date.

Thanks

boB