Not sure if this has already been answered yet or not, but is this compatible with glass break detectors? Would they just classify as contact sensors? Any help you could provide would be appreciated!
Hi, I’m having a little trouble getting this set up. Mainly, my question is: can I wire the EVL-3 directly to the ethernet port on my Raspberry Pi? I have a Raspberry Pi 3 Model B which is connected to my network via wifi, then my pi connected to the EVL-3 via ethernet. Do I have to bridge the ethernet and wifi connections to make this work? Can someone point me to a guide on how to do that?
The EVL-3 has to obtain an IP address and the STNP running on the RPi can only connect to the EVL-3 via its IP address. You could bridge it, but would probably be more complicated than just connecting the EVL-3 to your router. Good luck!
Found similar questions posted online regarding ethernet to wifi bridging:
Yes I think so… I personally don’t have any but I think they behave in the same way.
The EVL-3 and my router are about as far apart in my house as I can get, which is why a wifi link would be better. I did see that post about bridging, but my understanding is that anything on the Ethernet side of the pi won’t be able to talk to anything on the wifi side; i.e., the EVL-3 will get an IP address from the pi and be able to access the Internet, but my smartthings hub won’t see it. I think. But I’m not sure if that’s even a problem…now that I think about it some more, I guess the hub doesn’t actually need to see the EVL-3, just the pi, right?
That’s correct… Only the STNP needs to comm with the hub. And the STNP needs to be able to comm with the EVL-3. Give it a shot… seems like it should work.
Trying to get this setup for the first time on Windows 10. After I started the server using “npm run start”, I get the following errors over and over. Any thoughts on what might be happening? It connects, sees errors, then closes the connection.
[2017-06-27T03:18:53.388Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2017-06-27T03:18:53.394Z] [stnp] Loaded plugin: envisalink
[2017-06-27T03:18:53.397Z] [evl3] Connected to Envisalink at 192.168.1.86:4025
[2017-06-27T03:18:53.397Z] [evl3] Error: ignoring invalid message code from Envisalink: 5053CD, data: 5053CD
[2017-06-27T03:19:03.136Z] [evl3] Error: ignoring invalid message code from Envisalink: 5052CC, data: 5052CC
[2017-06-27T03:19:08.026Z] [evl3] Envisalink connection closed.
[2017-06-27T03:19:12.028Z] [evl3] Connected to Envisalink at 192.168.1.86:4025
[2017-06-27T03:19:12.029Z] [evl3] Error: ignoring invalid message code from Envisalink: 5053CD, data: 5053CD
[2017-06-27T03:19:22.291Z] [evl3] Error: ignoring invalid message code from Envisalink: 5052CC, data: 5052CC
[2017-06-27T03:19:22.332Z] [evl3] Envisalink connection closed.
Anyone have any ideas why this might be stopping still having issues …
@redloro I have a basic question. If I have Honeywell Tuxedo already lan connected, would this solution work unaltered?
Nope… this implementation requires either the Envisalink module or the AlarmDevices module to communicate with the panel.
Do you have a Honeywell/Ademco Vista 20P alarm panel or a DSC panel??
Yes I have envisalink raspberry pi 3 vista 20p and st hub. everything works fine as long as I leave the command window in the pi up with node server.js running. A few posts ago I noted my issue, I have tried pm 2 as well as the solution you linked to for startup in background and neither are working for me. Pm2 ties up the port but no messaging takes place, and the other starts and works fine after reboot and then for some reason just stops after about 8 minutes every time. I posted the command I used up above. Thanks for looking!
Do you have a Honeywell/Ademco Vista 20P alarm panel or a DSC panel??
My bad… that was meant for the post above yours…
Regarding your issue, try this and let me know what happens:
- Reboot the RPi
- From the command line type:
/etc/init.d/stnpService stop - Verify that STNP is not running and nothing is connected the EVL
- From the command line type:
forever --sourceDir=/home/smartthings-nodeproxy -p /home/smartthings-nodeproxy server.js - Verify that STNP is running and connected to the EVL
- Log out from the RPi
- Check 10 mins later and see if STNP is still running and connected to the EVL
DSC panel.
Sorry this integration only works right now with the Honeywell / Ademco Vista panels. Check out post #424… If someone wanted to help with translating commands to DSC format, it would work. But I don’t have a DSC to test with.
No problem! I will try that once I get home from work. Thanks again for your help, this integration is fantastic.
easy question; easy answer! Thank you for the response.
I rebooted the Pi and my foyer lights are turning on from the Honeywell front door contact so I know that once it rebooted the stnpService was doing its job on reboot and working. However, once I entered the command you gave me, this is what it told me.
pi@raspberrypi:~ $ /etc/init.d/stnpService stop
error: Forever cannot find process with id: server.js
If I go to that folder I see the service is in there.
pi@raspberrypi:/etc/init.d $ ls
alsa-utils hostname.sh nfs-common sendsigs
avahi-daemon hwclock.sh ntp single
bluetooth kbd plymouth skeleton
bootlogs keyboard-setup plymouth-log ssh
bootmisc.sh killprocs procps stnpService
checkfs.sh kmod raspi-config sudo
checkroot-bootclean.sh lightdm rc triggerhappy
checkroot.sh motd rc.local udev
console-setup mountall-bootclean.sh rcS udev-finish
cron mountall.sh README umountfs
dbus mountdevsubfs.sh reboot umountnfs.sh
dhcpcd mountkernfs.sh rmnologin umountroot
dphys-swapfile mountnfs-bootclean.sh rpcbind urandom
fake-hwclock mountnfs.sh rsync x11-common
halt networking rsyslog xrdp
8 minutes went by and as before the process stopped.
Bear with my thought process because I have no idea about Linux, Im just trying to figure this out. So I verified server.js is still in
pi@raspberrypi:~ $ cd /home
pi@raspberrypi:/home $ ls
pi smartthings-nodeproxy
pi@raspberrypi:/home $ cd smartthings-nodeproxy
pi@raspberrypi:/home/smartthings-nodeproxy $ ls
avail_plugins config.json node_modules package.json plugins server.js
I started the service to see if it would connect and it did
pi@raspberrypi:/home/smartthings-nodeproxy $ node server.js
[2017-06-29T21:06:06.349Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2017-06-29T21:06:06.396Z] [stnp] Loaded plugin: envisalink
[2017-06-29T21:06:06.406Z] [evl3] Connected to Envisalink at 192.168.1.202:4025
[2017-06-29T21:06:14.243Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED CHIME Ready to Arm”}
[2017-06-29T21:06:30.833Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:1,“state”:“open”}
[2017-06-29T21:06:30.841Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“notready”,“alpha”:“FAULT 01”}
[2017-06-29T21:06:33.849Z] [evl3] {“type”:“zone”,“partition”:1,“zone”:“1”,“state”:“closed”}
[2017-06-29T21:06:33.852Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DISARMED CHIME Ready to Arm”}
I hit control C because thats the only way I know how to stop it, Foyer light not working and TPI shows down so I paste in
pi@raspberrypi:~ $ forever --sourceDir=/home/smartthings-nodeproxy -p /home/smartthings-nodepro xy server.js
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 100 0ms
[2017-06-29T21:10:56.447Z] [stnp] SmartThings Node Proxy listening at http://:::8080
[2017-06-29T21:10:56.495Z] [stnp] Loaded plugin: envisalink
[2017-06-29T21:10:56.506Z] [evl3] Connected to Envisalink at 192.168.1.202:4025
[2017-06-29T21:10:57.822Z] [evl3] {“type”:“partition”,“partition”:1,“state”:“ready”,“alpha”:“DI SARMED CHIME Ready to Arm”}
TPI comes up, light is working
I close the SSH session ( Is this what you meant by logout?), and TPI immediately goes down.
Hi,
I’ve Vista-20HW. Will this work with that system?