Alarmpanel decoder - can't arm/disarm panel

Configuration
1

Hello,

Growing frustrated by a problem that I can’t seem to solve. I have had the alarmdecoder component (hassbian) installed for over a year now and in the last few weeks the arm/disarm function has started to act up. I cannot use the automations, nor call the service manually to arm/disarm the panel. The functionality of the panel still works as I can see the fault statuses coming through Homeassistant. Sometimes, if I’ve hit the disarm button on HA 50+ times it will run the disarm.

I am connected via USB to a raspberry pi. If I load up the alarm software and plug into my laptop I can control the alarm panel with no issue.

When I click arm home below is the debug event firing.

[homeassistant.components.websocket_api.http.connection.1605591536] Received {'service_data': 
{'entity_id': 'alarm_control_panel.alarm_panel', 'code': '0000'}, 'service': 'alarm_arm_home', 'id': 21, 
'type': 'call_service', 'domain': 'alarm_control_panel'}

[homeassistant.core] Bus:Handling <Event call_service[L]: 
service_call_id=b143f66cca3340559442bbe6d1c80aba, 
service_data=entity_id=alarm_control_panel.alarm_panel, code=0000, service=alarm_arm_home, 
domain=alarm_control_panel>
[homeassistant.components.websocket_api.http.connection.1585035024] Sending {'event': 
{'time_fired': datetime.datetime(2019, 2, 10, 20, 32, 17, 403915, tzinfo=<UTC>), 'data': {'service': 
'alarm_arm_home', 'service_data': {'entity_id': 'alarm_control_panel.alarm_panel', 'code': '0000'}, 
'service_call_id': 'b143f66cca3340559442bbe6d1c80aba', 'domain': 'alarm_control_panel'}, 
'event_type': 'call_service', 'context': {'user_id': '67ab15d61e8a46f8acd2315381a6d65b', 'id': 
'43f1e2e5c8734a87bf91b9ca84b86d6c'}, 'origin': 'LOCAL'}, 'id': 2, 'type': 'event'}

[homeassistant.core] Bus:Handling <Event service_executed[L]: 
service_call_id=b143f66cca3340559442bbe6d1c80aba>

Below is my config

alarmdecoder:
  device:
    type: serial
  panel_display: On
  zones:
    01:
      name: 'Doors'

It also looks like my USB is connected via serial.

pi@hassbian:~ $ dmesg | grep tty
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 
vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 
root=PARTUUID=6c94d8e3-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[    0.000806] console [tty1] enabled
[    0.833396] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 
rev2
[    4.038517] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0
[86844.947628] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[86844.947743] ftdi_sio ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[86845.036200] ftdi_sio ttyUSB0: error from flowcontrol urb
[86845.036566] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from 
ttyUSB0
[86957.627220] usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

Looking for some suggestions on what else to look at and try.

2

I’m experiencing the same issue now, FWIW

3

Never-mind. My issue was after a firmware update of the alarmdecoder, the ‘panel address’ reverted to the default (18) which doesn’t work for my set-up.

I had to reconfigure alarmdecoder to assign a different panel address (to 20 in my case)

4

Well sure enough, it’s happening again. It’s always around the same time of year. When it gets a bit colder. I can’t see how that could have any affect on the calls to the panel, but for the past 4 years it’s happening within the same time frame.

I’m at a loss as to what to do!