ufodone / envisalink_new

A modernized version of the Home Assistant envisalink integration available through HACS.
MIT License
69 stars 8 forks source link

Intermittent: All zones tripped when arming #26

Closed ufodone closed 1 year ago

ufodone commented 1 year ago
          I’ve seen some weird behavior with the recent update, but I can’t seem to replicate. It appears (not sure) that during arming, all the zones are tripped. But the system is still able to be armed. So the Envisalink seems ok, it may be the integration logging the trips. When this happens and I disarm, all is cleared. I’ll keep monitoring.

_Originally posted by @larry-glz in https://github.com/ufodone/envisalink_new/issues/1#issuecomment-1442803743_

ufodone commented 1 year ago

@larry-glz I assume this is with the 0.6.2 release? Do you have a Honeywell or DSC system?

If you're able to capture the issue with debug logging turned on, that would be very helpful. Thanks!

larry-glz commented 1 year ago

Yes, on the 0.6.2 with a Honeywell system. Here's my config and the logs. You'll see the system is initially Armed, then i disarm it. When i arm it again, all the zones are triggered.

envisalink_new:
  host: 192.168.22.68
  panel_type: HONEYWELL
  user_name: !secret envisalink_username
  password: !secret envisalink_password
  code: !secret envisalink_code
  port: 4025
  evl_version: 4
  keepalive_interval: 60
  zonedump_interval: 0 # was 30
  timeout: 15 # was 10
  panic_type: Police
  zones:
    1:
      name: "Main/Garage/Mud Rm Front Entries"
      type: "door"
    2:
      name: "Patio Entry"
      type: "door"
    3:
      name: "Lounge Entry"
      type: "door"
    4:
      name: "Kitchen/Laundry Windows"
      type: "window"
    5:
      name: "Master Bed/Bath Windows"
      type: "window"
    6:
      name: "Upstairs Openings"
      type: "opening"
    7:
      name: "Main Areas Motion"
      type: "motion"
    8:
      name: "Glass Break"
      type: "sound"
    9:
      name: "Alarm Garage Door 1"
      type: "garage_door"
    10:
      name: "Alarm Garage Door 2"
      type: "garage_door"
    11:
      name: "Mud Rm Motion"
      type: "motion"
    12:
      name: "Laundry Smoke"
      type: "smoke"
    13:
      name: "Family Rm Smoke"
      type: "smoke"
    14:
      name: "Upstairs Smoke"
      type: "smoke"
    15:
      name: "Security Rm Panic"
      type: "safety"
    16:
      name: "Mud Rm Rear Entry"
      type: "door"
  partitions:
    1:
      name: "Rancho Gonzalez Alarm"

home-assistant_2023-02-24T15-33-18.488Z.log

ufodone commented 1 year ago

@philh30 Would you mind taking a peek at the log?

garyak commented 1 year ago

Also on 0.6.2 with EV4 and Honeywell. I'm seeing an automation using alarm sensors trigger when arming the alarm. (See attached)

ha_alarm.log

ufodone commented 1 year ago

I've pushed v0.6.3 which I hope fixes these issues. I don't have a Honeywell system myself but tried to replicate what was in the logs you both provided in my mock setup.

larry-glz commented 1 year ago

I updated to v0.6.3 and armed stay seemed to have worked OK. I'll keep monitoring. thanks!

garyak commented 1 year ago

Loaded 0.6.3 and testing by arming the alarm as before. HA History shows that all zone sensors remained Off (closed). alarmsnr

larry-glz commented 1 year ago

Same here. Tested arming/disarming/arming and all zones closed/open as expected. Thanks!