DSC Alarm integration

Feature Requests
411

Ok, just the simple logger: line did the trick. Here is a dump of the output when I unplug the AC power from the alarm and then plug it back in. Does it shed any light?

2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] TX > b'00090'
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < 5109100
8401CD
8402CE
8403CF
8404D0
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.dsc_client] No handler defined in config for 510, skipping...
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No handler configured for evl command.
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] KeyError: 'handler'
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No callback configured for evl command.
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 840 with data: 1
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 1) state has updated: {"trouble": true}
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:42 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 840 with data: 2
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 2) state has updated: {"trouble": true}
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:42 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 840 with data: 3
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 3) state has updated: {"trouble": true}
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:42 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 840 with data: 4
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 4) state has updated: {"trouble": true}
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:42 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < 50000025
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_poll_response for code: 500 with data: 000
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.dsc_client] DSC ack recieved.
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_poll_response
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.alarm_panel] Callback has not been set by client.
2018-01-16 19:03:42 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:42 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.home_alarm_keypad, old_state=<state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=False, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>, new_state=<state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=True, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>>
2018-01-16 19:03:42 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.alarm_panel_trouble, old_state=<state binary_sensor.alarm_panel_trouble=off; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T18:56:31.460665-05:00>, new_state=<state binary_sensor.alarm_panel_trouble=on; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T19:03:42.598513-05:00>>
2018-01-16 19:03:42 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1923264816: Sending {'id': 2, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'sensor.home_alarm_keypad', 'old_state': <state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=False, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>, 'new_state': <state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=True, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 1, 17, 0, 3, 42, 565620, tzinfo=<UTC>)}}
2018-01-16 19:03:42 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1923264816: Sending {'id': 2, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'binary_sensor.alarm_panel_trouble', 'old_state': <state binary_sensor.alarm_panel_trouble=off; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T18:56:31.460665-05:00>, 'new_state': <state binary_sensor.alarm_panel_trouble=on; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T19:03:42.598513-05:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 1, 17, 0, 3, 42, 598853, tzinfo=<UTC>)}}
2018-01-16 19:03:46 INFO (SyncWorker_9) [homeassistant.components.device_tracker.asuswrt] Checking Devices
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < 51110F8
8490207
51080FE
51100F7
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.dsc_client] No handler defined in config for 511, skipping...
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No handler configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] KeyError: 'handler'
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No callback configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.dsc_client] No handler defined in config for 849, skipping...
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No handler configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] KeyError: 'handler'
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No callback configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.dsc_client] No handler defined in config for 510, skipping...
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No handler configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] KeyError: 'handler'
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No callback configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.dsc_client] No handler defined in config for 511, skipping...
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No handler configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] KeyError: 'handler'
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No callback configured for evl command.
2018-01-16 19:03:47 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < 5109100
6501CC
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.dsc_client] No handler defined in config for 510, skipping...
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No handler configured for evl command.
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] KeyError: 'handler'
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No callback configured for evl command.
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 650 with data: 1
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 1) state has updated: {"ready": true, "alpha": "Ready"}
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:48 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:48 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] RX < 51081FF
8411CE
8412CF
8413D0
8414D1
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.dsc_client] No handler defined in config for 510, skipping...
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No handler configured for evl command.
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] KeyError: 'handler'
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] No callback configured for evl command.
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 841 with data: 1
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 1) state has updated: {"trouble": false}
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:52 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 841 with data: 2
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 2) state has updated: {"trouble": false}
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:52 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 841 with data: 3
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 3) state has updated: {"trouble": false}
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:52 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] calling handler: handle_partition_state_change for code: 841 with data: 4
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.dsc_client] (partition 4) state has updated: {"trouble": false}
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] Invoking callback: callback_partition_state_change
2018-01-16 19:03:52 INFO (MainThread) [homeassistant.components.envisalink] The envisalink sent a partition update event
2018-01-16 19:03:52 DEBUG (MainThread) [pyenvisalink.envisalink_base_client] ----------------------------------------
2018-01-16 19:03:52 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.home_alarm_keypad, old_state=<state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=True, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>, new_state=<state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=False, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>>
2018-01-16 19:03:52 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=binary_sensor.alarm_panel_trouble, old_state=<state binary_sensor.alarm_panel_trouble=on; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T19:03:42.598513-05:00>, new_state=<state binary_sensor.alarm_panel_trouble=off; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T19:03:52.149135-05:00>>
2018-01-16 19:03:52 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1923264816: Sending {'id': 2, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'sensor.home_alarm_keypad', 'old_state': <state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=True, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>, 'new_state': <state sensor.home_alarm_keypad=Ready; alarm=False, alarm_in_memory=False, armed_away=False, ac_present=True, armed_bypass=False, chime=False, armed_zero_entry_delay=False, alarm_fire_zone=False, trouble=False, bat_trouble=False, ready=True, fire=False, armed_stay=False, alpha=Ready, beep=False, exit_delay=False, entry_delay=False, last_disarmed_by_user=, last_armed_by_user=, friendly_name=Home Alarm Keypad, icon=mdi:alarm @ 2018-01-16T18:59:02.586165-05:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 1, 17, 0, 3, 52, 118984, tzinfo=<UTC>)}}
2018-01-16 19:03:52 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1923264816: Sending {'id': 2, 'type': 'event', 'event': {'event_type': 'state_changed', 'data': {'entity_id': 'binary_sensor.alarm_panel_trouble', 'old_state': <state binary_sensor.alarm_panel_trouble=on; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T19:03:42.598513-05:00>, 'new_state': <state binary_sensor.alarm_panel_trouble=off; friendly_name=Alarm Panel Trouble Status @ 2018-01-16T19:03:52.149135-05:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2018, 1, 17, 0, 3, 52, 149398, tzinfo=<UTC>)}}
412

Thanks- yep i see what’s going on here.
So to indicate a “trouble” your DSC is sending code 840 to set the trouble flag, and 841 again to clear the trouble flag at the end. I’m handling that properly, and setting the trouble attribute.

Your DSC is also sending codes 510/511, which are the LED status. I have found that to be redundant to 840/841, so I’m purposely ignoring those.

Now, I see that your panel is sending 849, which stands for “verbose trouble status”. That’s definitely being used to report the power loss. I am not handling this at the moment. I was expecting to be told about AC failure from code 802/803 instead- but your panel isn’t sending that for some reason.

I’ll see what i can do to fix that on the pyenvisalink side - I’ll just need some assistance testing since I don’t have a DSC panel.

1 Like
413

Thanks, sounds good. I’ll do what I can to test, my panel is the PC1864 which is a pretty mainstream panel for DSC (though not their newest line which is the Neo, which doesn’t support Envisalink). I’d like to induce a sensor low battery report as well to see what code that is, maybe I can rig something up with a voltage divider.

414

Where do the icons get set for the different sensors? The door sensors used to show correctly but now they’re just blue squares. I can override it manually but it’d be nice if I didn’t have to.

Here the front door sensor was overridden with icon: mdi:door and all the others are their standard. The motion one still works fine as does the icon for the keypad.

22 AM
22 AM968×616 14.9 KB

415

Good question- i’m not entirely sure… are you setting the zone type of each of your zones? In terms of the envisalink component that’s as far as I’m taking it. What icon is chosen for that is determined elsewhere- i’ll take a look to see if I can figure it out because i’m curious, but i’m thinking this will be a more global change/fix.

416

i’m making pretty good progress here- just need to do some unit tests and then i can push this.

417

For the doors, I’m setting the zone types right now to type: opening, but I guess I should’ve made them type: door. Oops :flushed:

Do you maintain the envisalink component? If so, I recently opened an issue with it preventing HASS from starting: https://github.com/home-assistant/home-assistant/issues/11731

418

Well, I tried changing my zones from “opening” to “door” but then they just straight up stopped gathering data. :man_shrugging:

419

I’m doing it with classes. I think this is what you want.

homeassistant:
  customize:
    binary_sensor.garage_rollup:
      device_class: garage_door

  customize_glob:
    "binary_sensor*motion":
      device_class: motion
    "binary_sensor*door":
      device_class: door
    "binary_sensor*window":
      device_class: window
420

How do I make the binary_sensors created by addon report state_topic to mqtt broker?

Trying to sync DSC sensors it with smartthings too.

I was able to do this the other-way around with alarmserver.py syncing with smartthings and via MQTT getting both to show status, but with this addon creating devices, im not sure how to add MQTT to them

421

Hey sorry it’s been a long week- i did put that component together and have been updating it on occasion. I took a quick look at the issue over on github, but I’d need to dig deeper to see what’s going on. I know when I released it- the Home assistant project was just getting started with asyncio, and the ability to initialize a component asynchronously wasn’t there yet- so I’ll likely have to update the component to do so. Now that still doesn’t explain why it’s taking so long to actually initialize…

422

For whatever reason, things to be working better in 0.62. I was having an issue with 0.61.1 where after about a day, the envisalink stuff would just stop updating and getting new info. Since updating to 0.62 I seem to have fewer issues relaunching hass and getting that error about being unable to connect to the EVL, and it seems to continue to collect info correctly.

423

Ok good to hear! I know that the evl only allows one connection at a time so if you have something else talking to it, or if somehow some odd circumstance in hass is causing multiple connections, that could manifest itself in this way.

424

Just came across the issue where HASS stops receiving updates from the EVL. it’s been running for about 24 hours and now the only thing in my log is:

TX > b'00898'
TX > b'00090'

Over and over again with no RX like it usually has. Do you have any more info on the API that I could try curling and seeing if there’s an error in the response? The standard web interface for the EVL continues to update.

425

Actually- so those 2 commands are outbound from hass to evl. The last 2 chars are always a checksum, so the two commands are:

  • 000, which is a keep alive command
  • 008, which is a request to dump zone timers (I use them to assist with status). We don’t seem to be getting anything back at all though.
    The only way to really test this manually would be using Telnet, as it’s a pretty low level protocol.i also do have a little test script that’s part of the pyenvisalink library that spits out the same info as what you have there (without the rest of the ha stuff). Do you maybe have the cloud features turned on, and something is interfering?
426

Cloud features of the EVL? Only the standard reporting to eyez-on but I’m not really using that. I haven’t even armed the alarm in a few months. I’m really just using the alarm components for HASS.

427

If some one could point me in the right direction, Ive tried a few things with no luck. I know I could make an automation that ties one sensor to another MQTT sensor, but that doesn’t sound like the right way to do it.

428

I tried added state_topic to envisalink section, but i get the following error.

Invalid config for [envisalink]: [state_topic] is an invalid option for [envisalink]. Check: envisalink->envisalink->zones->1->state_topic. (See /config/configuration.yaml, line 118).
429

If you ever need a “tester” for a DSC panel, please let me know. I am willing to do whatever you need.

430

Thanks- i haven’t forgotten about making some of the adjustments mentioned above for night arm, but it’s been crazy as of late and I haven’t had the time!