Envisalink Not Working After Upgrades

Configuration
1

At some point after one of the upgrades this year, my Envisalink integration became really flaky. The main issue is it looks normal, but the motion detection just stopped working.

The underlying DSC security system is fine, as is the EyezOn app on my iPhone. The iPhone is correctly showing a motion sensor last fired 35 seconds ago. My HomeAssistant says it was last fired 1 week ago.

Envialink has a weird integration as you just enter stuff in configuration.yaml. Here is my section for envisalink:

envisalink:
  host: 192.168.1.3
  panel_type: DSC
  user_name: user
  password: [redacted]
  code: "[redacted]"
  port: 4025
  evl_version: 4
  keepalive_interval: 60
  zonedump_interval: 30
  timeout: 10
  panic_type: Police
  zones:
    1:
      name: "Front Door"
      type: "opening"
    2:
      name: "Kitchen Sliding Door"
      type: "opening"
    3:
      name: "James Bedroom Door"
      type: "opening"
    4:
      name: "Graydon Bedroom Door"
      type: "opening"
    5:
      name: "Master Bedroom Door"
      type: "opening"
    6:
      name: "Basement Door"
      type: "opening"
    7:
      name: "Garage Overhead Door"
      type: "opening"
    8:
      name: "Basement Front Window"
      type: "opening"
    9:
      name: "Basement Middle Window"
      type: "opening"
    10:
      name: "Living Room Left Window"
      type: "opening"
    11:
      name: "Living Room Right Window"
      type: "opening"
    12:
      name: "Dining Room Window"
      type: "opening"
    13:
      name: "Breakfast Area Window"
      type: "opening"
    14:
      name: "Master Ensuite Window"
      type: "opening"
    15:
      name: "Garage Heat"
      type: "heat"
    16:
      name: "Sump Pump"
      type: "none"
    17:
      name: "James Bedroom Motion"
      type: "motion"
    18:
      name: "James Glass Break"
      type: "vibration"
    19:
      name: "Graydon Glass Break"
      type: "vibration"
    20:
      name: "2nd Floor CO2"
      type: "carbon_monoxide"
    21:
      name: "Master Ensuite Glass Break"
      type: "vibration"
    22:
      name: "Master Glass Break"
      type: "vibration"
    23:
      name: "Master Motion"
      type: "motion"
    24:
      name: "Main Floor CO2"
      type: "carbon_monoxide"
    25:
      name: "Basement Front Glass Break"
      type: "vibration"
    26:
      name: "Basement Middle Glass Break"
      type: "vibration"
    27:
      name: "Basement Back Glass Break"
      type: "vibration"
    28:
      name: "Office Motion"
      type: "motion"
    29:
      name: "Basement Front Motion"
      type: "motion"
    30:
      name: "Breakfast Area Glass Break"
      type: "vibration"
    31:
      name: "Breakfast Area Motion"
      type: "motion"
    32:
      name: "Kitchen Glass Break"
      type: "vibration"
    33:
      name: "Dining Room Glass Break"
      type: "vibration"
    34:
      name: "Living Room Glass Break"
      type: "vibration"
    35:
      name: "Living Room Motion"
      type: "motion"
  partitions:
    1:
      name: "Home Alarm"
2

I have the same symptoms. I have to reboot the Envisalink board to clear it and the problem recurs in about a day. It used to work flawlessly. Has anyone else noticed this and is there a solution?

1 Like
3

My Envisalink connection with my DSC alarm stopped working yesterday and can no longer connect. When I log into the Envisalink web interface, I briefly see the TPI connection turn green, then it says “Disconnected”.

2023-11-14 10:54:00.230 INFO (MainThread) [pyenvisalink.envisalink_base_client] Started to connect to Envisalink... at 192.168.2.18:4025
2023-11-14 10:54:00.232 INFO (MainThread) [pyenvisalink.envisalink_base_client] Connection Successful!
2023-11-14 10:54:00.233 ERROR (MainThread) [pyenvisalink.envisalink_base_client] The server closed the connection. Reconnecting...
2023-11-14 10:54:00.234 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Closing connection with server...

I’m running Core 2023.11.2.

I’ve tried rebooting Home Assistant, rebooting the Envisalink and changing the IP to a different static address. Any suggestions? The timing seems to be very close to when I upgraded to 2023.11.2, but I can’t be certain.

1 Like
4

I found a workaround from a thread on Github.

I had to change the password of my Envisalink module (the default was “user”). Out of desperation, I tried changing the password to a numeric code (no letters or symbols). My system has been working and stable for over 48 hours (and counting).

Here is a link to the discussion on Github. Hopefully it will work for you too.

While I’m not thrilled about having to use a numeric password, it works around the immediate issue.

Good Luck.

1 Like
5

I figured out my issue. When I setup my Envisalink, I never “registered” it or connected it to their servers. This prevented me from getting any firmware updates (I was okay with that). When I allowed the device to connect to the internet - and registered the MAC in their portal, I was able to incrementally push firmware updates to it. Once it was current, I then blocked it again from the internet in my portal and it now works perfectly. My Envisalink device is at least 4 years old and was on Firmware Version: 01.00.100. It’s now updated and running version 176 (as of today).