Can't enter code to disarm or arm homeassistant/components/envisalink

[wptracy]

The problem

I can't arm, (home away, or home stay) or disarm envisalik from the alarm panel card.

I found what I thought was the solution, but it doesn’t work.

The integration page Envisalink - Home Assistant says:

code string (Optional)

Your alarm panel’s code, for authenticating user input during arm/disarm. If you do not provide this value, the integration will prompt the user to enter the code at runtime.

So I commented out the code entry in configuration.yaml for envisalink, and now I get a code required field in the alarm panel card. I enter the code, but it doesn’t disable the alarm. No logs. I don’t know how to troubleshoot this.

What version of Home Assistant Core has the issue?

Core 2023.11.2 Supervisor 2023.11.3 Operating System 11.1 Frontend 20231030.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Envisalink https://www.home-assistant.io/integrations/envisalink/

Link to integration documentation on our website

https://www.home-assistant.io/integrations/envisalink/

Diagnostics information

I don't see a diagnostic link for this integration

Example YAML snippet

envisalink:
  host: 10.0.0.999
  panel_type: HONEYWELL
  user_name: user
  password: guess
  #  code: "9999"
  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: "Laundry Door"
      type: "opening"
    3:
      name: "Garage Service Door"
      type: "opening"
    4:
      name: "Garage Bay #3"
      type: "opening"
    5:
      name: "Garage Bay #1 & #2"
      type: "opening"
    6:
      name: "Upstairs Windows"
      type: "opening"
    7:
      name: "Downstairs Windows"
      type: "opening"
    8:
      name: "Back Sliding Door"
      type: "opening"
    9:
      name: "Upstairs Motion"
      type: "motion"
    10:
      name: "Furnace Rm Water Bug"
      type: "opening"
    11:
      name: "Sump Pump Water Bug"
      type: "opening"
  partitions:
    1:
      name: "Envisalink Home Alarm"

Anything in the logs that might be useful for us?

There are no logs when I try to disarm or arm the control panel

Additional information

No response

[home-assistant]

Hey there @ufodone, mind taking a look at this issue as it has been labeled with an integration (envisalink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of envisalink can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign envisalink Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

envisalink documentation
envisalink source
_{^{(message by IssueLinks)}}

[vez727]

I am encountering the same issue...upgraded recently to Home Assistant Core 2023.11.2

It was working with Home Assistant Core 2023.09.3

[wptracy]

I got it working by deleting the Envisalink configuration from configuration.yaml, and installing Invisialink_new.

[Cytomax55]

I got it working by deleting the Envisalink configuration from configuration.yaml, and installing Invisialink_new.

Are we still supposed to use envisalink_new because envisalink is not working anymore, i cant arm or disarm using HA, but i can using the envisalink local website

[irace]

Hi, I have this same question.

How should we be thinking about envisalink vs. envisalink_new, @ufodone? It seems like the former is broken but that the latter is still a work in progress.

Any potential of having this particular bug in envisalink fixed? Or, any chance that envisalink_new “graduates” to being ready in the near future?

Thanks so much in advance.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[irace]

Has anyone been able to get this to work without switching over to envisalink_new?