Envisalink Unique Entities

[Elliptic6435]

Hi, I was working on my Envisalink Integration. I was wondering if someone could point me in a direction for how to add in unique entity ID’s to the Envisalink configuration.

So far i have followed the default configuration here and have been able to see the binary sensors added to the lovelace UI.

Envisalink

Problem…
I am unable to use any of these sensors that are showing data in the Lovelace UI for any additional Automation (trying through UI). turning on lights etc…

I have referenced these two topics as well and so far i have not been able to get an understanding as to what my options are for using these sensors now that they are connected.

EnvisaLink/DSC integration not on UI but in Entities

Hi all, I just started play with HA and got an EnvisaLink 4 card for my DSC. After installed, I can use web browser to access with user/user, and it shows the Home/Network status, I can reboot the Envisalink. The config in configuration.yaml I think is not much different from lot of other posts: # Example configuration.yaml entry envisalink: host: 192.168.86.25 panel_type: DSC user_name: user password: user code: xxxx port: 4025 evl_version: 4 keepalive_interval: 60 zonedump_…

https://community.home-assistant.io/t/customizing-entity-on-ui-envisalink-honeywell-vista-20p-panel/214418/2make

i even tried to just throw unique id in there to no avail.

Unique IDs for entities in configuration.yaml

@Burningstone, thanks for the tip @dahill64, well that is just frustrating, presumably it’s on their ‘to do’ list

Thanks in advance

Here is my config.yaml for reference.

envisalink:
 # security.test
  host: 10.0.0.31
  user_name: !secret envisa_username
  password: !secret envisa_password
  panel_type: DSC
  code: !secret envisa_code
  port: 4025
  evl_version: 4
  keepalive_interval: 60
  zonedump_interval: 10
  timeout: 10
  zones:
    1:
      name: "1 - DriveWay SideDoor"
      type: "opening"
    2:
      name: "2 - Center Door"
      type: "opening"
    3:
      name: "3 - Patio Door"
      type: "opening"
    4:
      name: "4 - Garage Door"
      type: "opening"
    5:
      name: "5 - Detached Garage Door"
      type: "opening"
    6:
      name: "6 - Barn Entry Motion"
      type: "Motion6"
    7:
      name: "7 - Basement Bath"
      type: "opening"
    8:
      name: "8 - Garage Motion"
      type: "Motion"
    9:
      name: "9 - House Heat Detector"
      type: "opening"
    10:
      name: "10 - Game Room Door"
      type: "opening"
    11:
      name: "11 - Master Bedroom Door"
      type: "opening"
    12:
      name: "12 - Living Room Door"
      type: "opening"
    13:
      name: "13 - Game Room Motion"
      type: "motion"
    14:
#Verified
      name: "14 - Sitting Room"
      type: "motion"
    15:
      name: "15 - Living Room Motion"
      type: "opening"
    16:
      name: "16 - Garage Low Temp"
      type: "opening"
    17:
      name: "17 - Front Door"
      type: "opening"
  partitions:
    1:
      name: "Home Alarm"
    2:
      name: "Front Garage"

[NathanCu (Nathan Curtis)]

@Elliptic6435

if someone could point me in a direction for how to add in unique entity ID’s to the Envisalink configuration.

You ask the developer to add support to the integration.

What I bet money you’re trying to do (because it was literally the second thing I tried to do when I added my Envisalink) is show doors like doors and windows like windows? Look up using customize.yaml to customize device_class.

[Elliptic6435]

Thank you for pointing me in a direction. I will look into that.

[Elliptic6435]

Hey, do you have any sample code you can share for the customize.yaml I was trying to add in a unique ID but was only able to duplicate the sensor not add an id.
Thanks in advance

[Elliptic6435]

Most of my security is doors only. The end goal is to try to use it to create some automations with motion sensors and some Caseta lights

[Elliptic6435]

So I was able to solve this by using the state automation where I was able to select what I was looking for.

[vedno_lacni]

can you share your code for state automation?

[Elliptic6435]

This is a screenshot hopefully that works, if not here is the YAML

description: “”
mode: single
trigger:

• platform: state
  entity_id:
  • binary_sensor.12_living_room_door
    from: “off”
    to: “on”
    for:
    hours: 0
    minutes: 0
    seconds: 5
    condition: []
    action: []
    alias: New Automation

What made me confused originally was selecting the state field but needing to leaving some fields empty

[ddetton (Dean Detton)]

@Elliptic6435 Are you saying that you worked around the unique_id issue by implementing state automations? You still were not able to assign a unique_id to the panel or the zones correct?

[rymiller (Ryan Miller)]

Bump ^^. Has anyone figured out the unique_id issue?

[NathanCu (Nathan Curtis)]

What do you mean ‘figure it out’

Unique ID will require a rewrite/refactor of the Envisalink integration. Currently it doesn’t create them and doesn’t understand them. I totally agree that it needs to be done. Though. But until that happens. You’re out of luck.

There was a very recent bug fixed in 2024.6.3 that works around the lack of unique_id for the latest alarm updates but do not believe they currently have it in the plan. Be happy to be mistaken on that one.