Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Envisalink dsc issue #65856

Closed
owenmckeith opened this issue Feb 5, 2022 · 8 comments
Closed

Envisalink dsc issue #65856

owenmckeith opened this issue Feb 5, 2022 · 8 comments

Comments

@owenmckeith
Copy link

The problem

Dsc controller flashes "programming" once every 5 seconds.
When arming system "arm stay" the system arms in away mode.
When disarming, the system immediately arms again, and can only be disarmed after a number of attempts from the envisalink app.

When removing configuration from home assistant, the alarm system with envisalink works normally.

What version of Home Assistant Core has the issue?

2022.2.1

What was the last working version of Home Assistant Core?

2021.12.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Envisalink

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@probot-home-assistant
Copy link

envisalink documentation
envisalink source
(message by IssueLinks)

@MrSiO
Copy link

MrSiO commented Feb 6, 2022

Confirmed. Same issue. I also opened a ticket 2 days ago but your description is more accurate: #65729

@dasb00ter
Copy link

Same issue. While the programming icon lights on the panel it will not accept input which sabotages actions. Do you think the cause is home assistant or update pushed to the hardware? Has anybody reverted there HA and stopped this behaviour? Not useful info: My wife says I'm in the doghouse

@torbjorn2000
Copy link

I'm having the same issue, the physical control panel "restarts" and shows "The system is not available" (translated from Swedish (Systemet är inte tillgängligt").
Not useful info 2: Yesterday, I installed a wifi adapter for the Envisalink, letting it take power from the 12v backup battery. The alarm triggered because of the "sabotage" (expected) but I couldn't turn it off because of panel being disabled. The whole family woke up in panic (I did this during late evening of course), and 10 minutes later I found the fuse to pull the power to the sirens. I'm now looking for a cheap hostel.

@vincearcuri
Copy link

Same issue. While the programming icon lights on the panel it will not accept input which sabotages actions. Do you think the cause is home assistant or update pushed to the hardware? Has anybody reverted there HA and stopped this behaviour? Not useful info: My wife says I'm in the doghouse

@dasb00ter you need to remove the Envisalink integration from configuration.yaml, check your config and reboot HA to regain the use of your physical panels. The problem is with an update to HA Core introduced in version 2022.2.1 or 2. There appear to be some workarounds being floated in other threads you can try in the interim, or just wait for a fix to HA Core before renabling the Envisalink integration again.

@mniquette
Copy link

Seeing similar behavior on a DSC panel. Also if the panel is armed home and a ha reboot occurs the system will first come up in armed home mode but then switch to armed away some 10's of seconds later. In this state, the first attempt to disable the system from the ha ui panel fails with no visible affect but a second disarm attempt will disarm the system.

@dasb00ter
Copy link

I think people who know more about the inner workings of HA have defined the problem and are working on a fix. You can either research and implement the fix/hac found in the other references or as I have done disabled the integration until a fix comes with a core update. Thanks to those looking out for us. I do look at the breaking charges before updating but I think this was unforseen. My wife is unhappy but that will pass

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale label May 10, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jun 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants