search

kukulich / home-assistant-jablotron100

Home Assistant custom component for JABLOTRON 100+ alarm system
MIT License
65 stars 24 forks source link

Wrong status when Jablotron Alarm is tripped #66

Closed marceldeklerk closed 1 year ago

marceldeklerk commented 1 year ago

Hi all,

When leaving home and arming my alarm system, the state of [alarm_control_panel.section_1] goes from arming, to armed_away. When I trigger a sensor (open a door), the status changes to pending (the time the system allows you to enter your code and disable the alarm). So far so good. However, when I am not disarming the alarm, and actually triggering it (loud sirens), the status changes back to armed_away. I would expect the status to change to triggered or in alarm or something like that.

I expect this is a bug. I would like to be able to read the status when the alarm is actually triggered in order to put my indoor and outdoor lights in blinking mode.

My setup is HASS.IO on a NUC, but this issue already existed already when I was running HASS.IO on a Pi4. I've pulled the latest version of this integration. I am using this integration for many years, and never actually tried reading the status while the Jablotron is in alarm state, I expect this never worked before for me.

I am running: Home Assistant 2023.2.5 Supervisor 2023.01.1 Operating System 9.5 Frontend 20230202.0 - latest

My Jablotron config: JA101-K control panel JA-110R Radio module JA-110A indoor siren JA-150P PIR (x2) JA-151M Door sensor (x2) JA-111m Door sensor JA-111A Outdoor siren JA-151S Smoke detector.

kukulich commented 1 year ago

Please enable debugging and log all packets. You can send me the log via private message on Discord

marceldeklerk commented 1 year ago

I've put the integration in debug mode, but it is not giving anything usefull I am afraid:

2023-02-21 19:57:57.962 DEBUG (MainThread) [custom_components.jablotron100] Central unit: JA-101K (hardware: LJ60426, firmware: LJ16120) 2023-02-21 19:58:55.982 DEBUG (ThreadPoolExecutor-2_0) [custom_components.jablotron100] Active user: 2

I have triggered the alarm in both away and at home mode, but nothing regarding it in the log. Also what is your discord id? Thanks.

kukulich commented 1 year ago

See README

marceldeklerk commented 1 year ago

Ah, sorry for that. I enabled debugging but was not aware that it needed to be enabled in the integration config as well. Below the relevant log entries

I timed the triggering of the alarm at 20:25:45

Jablotron100log.txt

kukulich commented 1 year ago

@marceldeklerk Please log all outcoming packets as well. We need to check if there's some communication from the integration to the Jablotron during the alarm.

marceldeklerk commented 1 year ago

Below the entries.

20:23:00 - armed the alarm 20:23:15 - status changed to: armed_night 20:23:30 - tripped the alarm

fyi: Device 2: keypad Device 9: Doorsensor (I used this one to trip the alarm)

Jablotron100log-2.txt

kukulich commented 1 year ago

@marceldeklerk Please try version master. I've just pushed one improvement.

kukulich commented 1 year ago

Hmm, you may need to wait for release HA 2023.3.0 because master already requires this version...

marceldeklerk commented 1 year ago

No problem. Will try the 2023.3.0 version as soon as it is released. Thanks in advance!

marceldeklerk commented 1 year ago

Upgraded to 2023.3.0 and pulled the latest version of MASTER. The status changed to 'Triggered' this time. Thanks for you help, I really appreciate it. I made a small donation.

kukulich commented 1 year ago

Thank you very much. I'll release it early.