RPi - AD2USB - Vera3 question

[mrwildbob]

Hello Group,

I had installed the AlarmDecoder image on my Raspberry Pi along with the AD2USB interface and they work great. I also use the AlarmDecoder KeyPad App on the desktop to monitor the system. I just purchased a Vera3 to automate the locks on my front door as well as other functions in the house. There is an app to control the alarm panel connected to an AD2USB interface with the Vera3. This would require each device to have its own interface. Is it possible to have the Vera3 talk to the RPi using the socket for the interface and only use one interface?

boB

[kevin]

You would have to confirm that the Vera can support connecting to a ser2sock instance in the plugin - perhaps the developer of the Vera plugin on the micasaverde forums can help with this? Last I heard it supported ser2net and not ser2sock but I am not sure.

[xuniman]

Can ser2sock and ser2net be run at the same time? Or do I need to terminate ser2sock in order to get the ser2net running so the AD2USB plugged into the pi can talk to my Vera3?

[kevin]

Only one device can attach to the serial port at one time, so you would have to run one or the other

It has been discussed adding support for the same protocol that ser2net uses to ser2sock at the office, I will bring it up again

[xuniman]

That would really be great. The ability to use the web interface and still have the Vera be able to talk to the AD2USB over the network would be ideal. I'm sure that there are a lot of people who would be interested.

[kevin]

I don't know if it's been tried, but perhaps socat can be used as a potential workaround to this

use socat to create a virtual com port that is connected to the ser2sock stream and have ser2net share the virtual com port created with socat so that the vera can connect to that... again, this is just a thought and I don't know if this is even going to work.

[xuniman]

I am game to give it a try. My issue is that once I did the ser2net install on the Pi I can't get the AD2USB to respond to the web app even after I kill the ser2net process. I guess I could try re-imaging the flash back to your beta image and see if that works. I did set the AD2USB settings of the web interface to NOT share the connection over the network before I installed ser2net but I don't know how to reverse that if the AD2USB won't communicate with the ser2sock anymore.

[Scott]

So I just tested the webapp with ser2net and it functions fine. There really is no difference in protocol. There is one problem with running ser2net, though, and that's the fact that it only supports a single connection so getting the Vera and webapp working together with that isn't an option.

We don't have a Vera here to test with, but I don't see any reason why ser2sock wouldn't work with the Vera. You'd just have to point it at the Pi on port 10000. I can see maybe the the informational messages causing issues, but that can be disabled with raw_device_mode=1 in /etc/ser2sock/ser2sock.conf or -0 (zero) on the command line. I would try the stock setup first, though.

[xuniman]

The change of raw to 1 in the config lets both the Vera and web app communicate to the AD2USB but I am getting a 008 - "****DISARMED**** Ready to Arm " message every 10 seconds even though I have multiple zones faulted. When there are no zones faulted I get the same message every 5 seconds.

Any idea why the incorrect "****DISARMED**** Ready to Arm " message could be occurring?

What I have is a completely unchanged pi image the (the 8-18) with the only change being the raw bit in the ser2sock conf.

[kevin]

Please telnet to the ser2sock port and copy/paste a bunch of those lines

It could be multiple partitions where one partition is disarmed etc. We won't know until we can see the raw data itself.