@philh30 I can’t not connect. This is the error from live logging
023-03-06T20:38:22.018237722+00:00 ERROR Honeywell-Ademco Envisalink Could not connect to EnvisaLink: Connection refused (os error 111). Is this due to a password error or something else?
Is there a way where home monitor can actually make the vista 20p siren sound?
Tough to say from just that error line. A larger section of logs would help to see where the error is happening. Things to check:
- Is the local IP address for the Envisalink entered correctly, including the port?
- Is the password entered correctly, and is it the same password you use to log in at the local IP address?
- Do you have any other integrations connected to the Envisalink?
After entering the information in Step 4 and waitng more than 30 seconds, my device status just says: “No Connection to Panel”. What’s strange is arm/disarm actually works, there’s just nothing updating in the ST app, even when I fault a zone.
I verified I’m using the correct local IP and correct local password for my Evnisalink (with port 4025). I tried restarting the app, tried restarting the Hub, tried removing and re-adding the device, nothing helps.
Logging shows the following, repeated over and over, even when I fault a zone:
2023-05-13T01:45:17.502570030+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T01:45:17.503216822+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T01:45:27.422308448+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T01:45:27.422861531+00:00 TRACE Honeywell-Ademco Envisalink RX < $
But, if I armStay, I get:
2023-05-13T02:41:38.368634198+00:00 TRACE Honeywell-Ademco Envisalink Received event with handler capability
2023-05-13T02:41:38.376591425+00:00 INFO Honeywell-Ademco Envisalink <Device: 1050861f-e9cf-4766-9f38-9692e6608c19 (HW Primary Partition 1)> received command: {"args":{"alarmMode":"armStay"},"capability":"platinummassive43262.alarmMode","command":"setAlarmMode","component":"main","positional_args":["armStay"]}
2023-05-13T02:41:38.381779559+00:00 TRACE Honeywell-Ademco Envisalink Found CapabilityCommandDispatcher handler in envisalink-honeywell -> Partition
2023-05-13T02:41:38.382260966+00:00 INFO Honeywell-Ademco Envisalink 1050861f-e9cf-4766-9f38-9692e6608c19: envisalink|p|1 > RECEIVED PARTITION COMMAND armStay
2023-05-13T02:41:38.383079542+00:00 TRACE Honeywell-Ademco Envisalink TX > 22223
2023-05-13T02:41:38.383783811+00:00 DEBUG Honeywell-Ademco Envisalink HW Primary Partition 1 device thread event handled
2023-05-13T02:41:38.391674838+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T02:41:38.397565448+00:00 TRACE Honeywell-Ademco Envisalink THROTTLE: TX > 22223
2023-05-13T02:41:38.401839376+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T02:41:38.407974233+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T02:41:38.740177210+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T02:41:38.740830745+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T02:41:40.420566568+00:00 TRACE Honeywell-Ademco Envisalink THROTTLE: No more commands to send
2023-05-13T02:41:40.425162156+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T02:41:40.766211846+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
This is a new Envisalink4, I just added to my Honeywell Vista 21iP panel. Everything seems to be working fine outside of SmartThings. Any help would be appreciated. Thanks.
The Envisalink is sending blank lines. Does the Envisalink show the partition and zone status correctly on its LAN page or on your eyez on account?
Yes, the Eyezon app correctly shows status when I fault a zone, arm or disarm:
But, ST just stays like this:
Thanks
Log in through the LAN interface. Do you see any settings in the menus related to the TPI (third party interface)?
This is what I see. I tried to Enable TPI Session Alerts, but the check won’t stay. I also tried Reboot Envisalink, but no change. Thanks
Session alerts gives you notifications when the TPI disconnects. Not necessary to have it enabled. The troublesome thing is where it says TPI is offline. I wouldn’t expect arm/disarm commands to work in that state.
Things to try:
- Power cycle your ST hub (unplug from the wall and plug back in).
- Check that your EVL password in the ST app is set to the same password you used to log into the LAN interface. It defaults to “user”. I think the EVL4 is better but the EVL3 at least had difficulty with long passwords and special characters. I’d stick to 6 or fewer letters/numbers.
- Check that you have the correct IP:Port for the EVL in the ST app (
192.168.0.85:4025) - With live logging running, change the IP address in the ST app to a different address, then change it back to the correct address. Logs from the connection attempt might provide a clue for what’s happening.
- Power cycle the EVL. I think you’d have to unplug your alarm panel and also disconnect battery.
Powering off/on the hub seems to have helped with the TPI Status, it now says ONLINE and Client shows my hub IP. However, the app still says No Connection to Panel.
My EVL default password is the last 6 digits of the MAC address. I changed it to just “user”, but still same problem though.
I also powered off/on the alarm panel and EVL, problem remains.
I double checked the IP and port are correct.
Here’s what the logs show when I changed the IP:
2023-05-13T19:53:59.977042964+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T19:53:59.977593339+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T19:54:09.842253677+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T19:54:09.842908302+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T19:54:19.736440765+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T19:54:19.736983932+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T19:54:29.635696478+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T19:54:29.636242062+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T19:54:39.534563483+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T19:54:39.535217566+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T19:54:43.424011526+00:00 INFO Honeywell-Ademco Envisalink <Device: f69daf9a-d66a-42c1-88a1-a791e2b5ecab (HW Primary Partition 1)> received lifecycle event: infoChanged
2023-05-13T19:54:43.424967985+00:00 TRACE Honeywell-Ademco Envisalink Received event with handler device_lifecycle
2023-05-13T19:54:43.432802110+00:00 INFO Honeywell-Ademco Envisalink Renewing connection to Envisalink
2023-05-13T19:54:43.433284901+00:00 INFO Honeywell-Ademco Envisalink Using config prefs: 192.168.0.20:4025, alarmcode: 2222
2023-05-13T19:54:43.433930693+00:00 INFO Honeywell-Ademco Envisalink f69daf9a-d66a-42c1-88a1-a791e2b5ecab: envisalink|p|1 > INFO CHANGED PRIMARY PARTITION
2023-05-13T19:54:43.434573151+00:00 TRACE Honeywell-Ademco Envisalink Found DeviceLifecycleDispatcher handler in envisalink-honeywell -> Partition -> Primary Partition
2023-05-13T19:54:46.781871320+00:00 ERROR Honeywell-Ademco Envisalink Could not connect to EnvisaLink: No route to host (os error 113)
2023-05-13T19:54:46.786547320+00:00 WARN Honeywell-Ademco Envisalink Retrying to connect to Envisalink
2023-05-13T19:54:54.941739449+00:00 ERROR Honeywell-Ademco Envisalink Could not connect to EnvisaLink: No route to host (os error 113)
2023-05-13T19:55:03.102859203+00:00 ERROR Honeywell-Ademco Envisalink Could not connect to EnvisaLink: No route to host (os error 113)
2023-05-13T19:55:03.107898911+00:00 ERROR Honeywell-Ademco Envisalink Failed to connect to Envisalink
2023-05-13T19:55:03.111596411+00:00 INFO Honeywell-Ademco Envisalink <Device: f69daf9a-d66a-42c1-88a1-a791e2b5ecab (HW Primary Partition 1)> emitting event: {"attribute_id":"supportedAlarmModes","capability_id":"platinummassive43262.alarmMode","component_id":"main","state":{"value":["disarm","armAway","armStay"]}}
2023-05-13T19:55:03.160601828+00:00 DEBUG Honeywell-Ademco Envisalink HW Primary Partition 1 device thread event handled
2023-05-13T19:55:03.164983953+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:18.121830001+00:00 INFO Honeywell-Ademco Envisalink Attempting to reconnect to EnvisaLink
2023-05-13T19:55:21.267628461+00:00 ERROR Honeywell-Ademco Envisalink Could not connect to EnvisaLink: No route to host (os error 113)
2023-05-13T19:55:21.278895795+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:21.282025128+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:36.282706677+00:00 INFO Honeywell-Ademco Envisalink Attempting to reconnect to EnvisaLink
2023-05-13T19:55:39.427660012+00:00 ERROR Honeywell-Ademco Envisalink Could not connect to EnvisaLink: No route to host (os error 113)
2023-05-13T19:55:39.438750262+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:39.456657012+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:49.186994766+00:00 TRACE Honeywell-Ademco Envisalink Received event with handler device_lifecycle
2023-05-13T19:55:49.187677600+00:00 INFO Honeywell-Ademco Envisalink <Device: f69daf9a-d66a-42c1-88a1-a791e2b5ecab (HW Primary Partition 1)> received lifecycle event: infoChanged
2023-05-13T19:55:49.197467225+00:00 TRACE Honeywell-Ademco Envisalink Found DeviceLifecycleDispatcher handler in envisalink-honeywell -> Partition -> Primary Partition
2023-05-13T19:55:49.197937933+00:00 INFO Honeywell-Ademco Envisalink f69daf9a-d66a-42c1-88a1-a791e2b5ecab: envisalink|p|1 > INFO CHANGED PRIMARY PARTITION
2023-05-13T19:55:49.198585683+00:00 INFO Honeywell-Ademco Envisalink Using config prefs: 192.168.0.85:4025, alarmcode: 2222
2023-05-13T19:55:49.199219308+00:00 INFO Honeywell-Ademco Envisalink Renewing connection to Envisalink
2023-05-13T19:55:49.424231641+00:00 INFO Honeywell-Ademco Envisalink Found and connected to Envisalink device
2023-05-13T19:55:49.424852475+00:00 DEBUG Honeywell-Ademco Envisalink Waiting for login...
2023-05-13T19:55:49.426265808+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:49.431419350+00:00 TRACE Honeywell-Ademco Envisalink RX < Login:
2023-05-13T19:55:49.432040766+00:00 INFO Honeywell-Ademco Envisalink Received login password request; sending password
2023-05-13T19:55:49.433123683+00:00 TRACE Honeywell-Ademco Envisalink TX > user
2023-05-13T19:55:49.446938975+00:00 TRACE Honeywell-Ademco Envisalink RX < OK
2023-05-13T19:55:49.450943558+00:00 INFO Honeywell-Ademco Envisalink Successfully logged in to Envisalink...
2023-05-13T19:55:49.451541225+00:00 TRACE Honeywell-Ademco Envisalink TX > ^01,1$
2023-05-13T19:55:49.457223808+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:49.463097558+00:00 TRACE Honeywell-Ademco Envisalink THROTTLE: TX > ^01,1$
2023-05-13T19:55:49.470114141+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:49.476032558+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:51.488659601+00:00 TRACE Honeywell-Ademco Envisalink THROTTLE: No more commands to send
2023-05-13T19:55:51.489852517+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-05-13T19:55:52.475219976+00:00 INFO Honeywell-Ademco Envisalink <Device: f69daf9a-d66a-42c1-88a1-a791e2b5ecab (HW Primary Partition 1)> emitting event: {"attribute_id":"supportedAlarmModes","capability_id":"platinummassive43262.alarmMode","component_id":"main","state":{"value":["disarm","armAway","armStay"]}}
2023-05-13T19:55:52.476876893+00:00 DEBUG Honeywell-Ademco Envisalink HW Primary Partition 1 device thread event handled
2023-05-13T19:55:58.737112562+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T19:55:58.737760687+00:00 TRACE Honeywell-Ademco Envisalink RX < $
2023-05-13T19:56:08.633154650+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-05-13T19:56:08.633803942+00:00 TRACE Honeywell-Ademco Envisalink RX < $
Thanks.
My problem seems to have resolved itself. I noticed yesterday it started working though I hadn’t made any changes. Last week I contacted EyezOn Support for help with this, but all they did was confirm I had the latest firmware (190). I just checked and my firmware now shows 191 so I’m guessing maybe that fixed my issue.
Anyways, thanks @philh30 for all your help!
Update from EyezOn Support confirming issue fixed with update:
EYEZON SUPPORT support1@eyezon.com
Fri 5/26/2023 11:45 AMHi,
We didn’t realise you had an EVL4 MAX edition which indeed had a bug in the Honeywell TPI. It was fixed and the update pushed to all Honeywell MAX users.
Anyone with a MAC address in this range has a new MAX edition.
001C2A04XXXX
Sorry for your trouble. The release of the MAX wasn’t supposed to happen this quickly so it’s new to us too.
I’m having a hard time getting including my EnvisaLink4. I have it installed on my vista and via the eyezon website I can see it and also arm/disarm. So the device is working.
I installed the drivers. However, when I scan for nearby devices in the ST app, nothing shows up. Do I need to put the EnvisaLink into “discovery” mode somehow?
Seems like everyone has no problem getting ST to see and add the EnvistaLink, so I must be doing something wrong here.
Suggestions?
Do you have a room titled “Unassigned…” (or something to that effect? If so, is it in there?
Do you have the EVL4 using a static address and is your IP and port settings in the app correct?
Make sure that the password is for local access to your EVL4 and not the web password
Nope…didn’t get added to a random room.
I can’t even get to the point where I can enter IP/passwords in the settings portion of SmartThings. I can’t get the EVL4 to be added as a device at all.
I can’t add the EVL4 at all.
I try adding it like I would a normal z-wave device:
- icon>add device>scan for nearby devices>choose my hub (I have 2 hubs)
The scan process goes for about a minute and never discovers the EVL4. “No devices found…select device from list”
Network Setup:
ST Hub: Wifi
Wifi is an Eero Mesh network
EVL4 is connected via cat5 to a switch which is then connected to one of my eero nodes.
My laptop IS able to connect locally to my EVL4.
The initial step is that the driver creates the primary partition device. No communication with the EVL happens at that point. Even if you didn’t own an EVL, that part should still work. I just installed the driver and ran Scan nearby and all works as it should with that step. Some things you can try to troubleshoot:
-
Pull up your hub device in the app and check the driver menu to be sure that the driver is actually installed.
-
In the Devices tab, change the room to “All devices”. The three dot menu on that screen should have a search function. The device you’re looking for is by default named “HW Primary Partition 1”. You should be able to just search on HW to find it.
-
Uninstall and reinstall the driver. Then retry scan nearby.
-
If none of the above get you anywhere, download the CLI and run live logging on the driver while running scan nearby.
1 Like
Tada! Thanks. Uninstalling the driver and then reinstalling it fixed it. Who the hell knows, but all is working now!
Thanks!!
2 Likes
Curious if anyone has ever had this issue before:
When I arm stay, it does the normal count down from 60 and “arms” the system. Then from time to time as I’m walking past my panel (well after the system was armed), and I’ll see the screen lit up and courting back down. I’ve seen it go only a few seconds before starting a new 60 second cycle and also have seen it hours after I arm stay. I have verified that while this “re-countdown” event is going on, my system is in fact NOT armed. I can open a door with no alarm…even though I pressed my arm-stay button LONG before.
This is 100% my EVL4. If I unplug the red wire from the EVL4 when this happens, it stops. I know this is a smart things forum, but there is a good chance it isn’t smart things integration but rather an EVL4 to vista20 issue.
Anyone see something like this before???
Hi, new user here… I just had a new alarm system installed and the installer added the Envisalink. I was able to install the driver, set the IP address and keypad login, but when it initializes I get the following:
2023-12-15T22:15:45.690358412+00:00 ERROR Honeywell-Ademco Envisalink driver thread encountered error: [string “envisalink.lua”]:78: attempt to index a nil value (local ‘driver’)
2023-12-15T22:15:52.767650413+00:00 TRACE Honeywell-Ademco Envisalink RX < 5052CC
2023-12-15T22:15:52.768983746+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-12-15T22:15:52.780593746+00:00 DEBUG Honeywell-Ademco Envisalink Receive status = closed
2023-12-15T22:15:52.781442746+00:00 ERROR Honeywell-Ademco Envisalink Socket Receive Error occured: closed
2023-12-15T22:15:52.782664746+00:00 WARN Honeywell-Ademco Envisalink Envisalink has disconnected
2023-12-15T22:15:52.902208746+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-12-15T22:16:07.907285081+00:00 INFO Honeywell-Ademco Envisalink Attempting to reconnect to EnvisaLink
2023-12-15T22:16:07.951584415+00:00 INFO Honeywell-Ademco Envisalink Re-connected to Envisalink
2023-12-15T22:16:07.962235415+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-12-15T22:16:07.981460748+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-12-15T22:16:07.982323081+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
2023-12-15T22:16:07.983555415+00:00 TRACE Honeywell-Ademco Envisalink RX < 5053CD
2023-12-15T22:16:07.984736748+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-12-15T22:16:10.961186082+00:00 WARN Honeywell-Ademco Envisalink Failed to log into Envisalink; connect retry in 15 seconds
2023-12-15T22:16:11.066489415+00:00 ERROR Honeywell-Ademco Envisalink driver thread encountered error: [string “envisalink.lua”]:78: attempt to index a nil value (local ‘driver’)
2023-12-15T22:16:17.363568416+00:00 ERROR Honeywell-Ademco Envisalink Unknown response received
2023-12-15T22:16:17.369286416+00:00 TRACE Honeywell-Ademco Envisalink RX < 5052CC
2023-12-15T22:16:17.411273749+00:00 DEBUG Honeywell-Ademco Envisalink Receive status = closed
2023-12-15T22:16:17.412119082+00:00 ERROR Honeywell-Ademco Envisalink Socket Receive Error occured: closed
2023-12-15T22:16:17.413363416+00:00 WARN Honeywell-Ademco Envisalink Envisalink has disconnected
2023-12-15T22:16:17.528439416+00:00 DEBUG Honeywell-Ademco Envisalink driver device thread event handled
This repeats over and over every few seconds. Any thoughts on what could be wrong?
Many thanks!!
Adrian
That looks like the Envisalink protocol for a DSC panel. This driver is only for Honeywell panels. Check your panel and if it’s DSC you’ll want the driver below instead.