search

eavanvalkenburg / sia

SIA alarm systems integration into Home Assistant
MIT License
48 stars 11 forks source link

Unhandled event type: #1

Closed moodiejo closed 5 years ago

moodiejo commented 5 years ago

Version of the custom_component

Intalled Commit: 0289409

Configuration

sia: port: 3000 hubs:

*** I tried to format this YAML correctly, however it displays poorly formatted - the YAML is valid, I have format checked this via yamlint, it is just the formatting that is showing badly here. Not sure how to correct this when logging an issue - Yes, you guessed it, this is the first issue i have logged on github..


2019-09-11 20:19:13 WARNING (Thread-3) [custom_components.sia] Unhandled event type: Code: CG, Type: Close Area, Description: System has been partially armed, Concerns: Area number, Message: CG501
2019-09-11 20:19:14 WARNING (Thread-3) [custom_components.sia] Unhandled event type: Code: CF, Type: Forced Closing, Description: System armed, some zones not ready, Concerns: User number, Message: CF501
2019-09-11 20:19:14 WARNING (Thread-3) [custom_components.sia] Unhandled event type: Code: CG, Type: Close Area, Description: System has been partially armed, Concerns: Area number, Message: CG501
2019-09-11 20:19:14 WARNING (Thread-3) [custom_components.sia] Unhandled event type: Code: CG, Type: Close Area, Description: System has been partially armed, Concerns: Area number, Message: CG501

2019-09-11 20:49:26 WARNING (Thread-2) [custom_components.sia] Unhandled event type: Code: CG, Type: Close Area, Description: System has been partially armed, Concerns: Area number, Message: CG501
2019-09-11 20:49:27 WARNING (Thread-2) [custom_components.sia] Unhandled event type: Code: OG, Type: Open Area, Description: System has been partially disarmed, Concerns: Area number, Message: OG501
2019-09-11 20:49:28 WARNING (Thread-2) [custom_components.sia] Unhandled event type: Code: OG, Type: Open Area, Description: System has been partially disarmed, Concerns: Area number, Message: OG501

Describe the bug

Constantly receiving Unhandled event type error messages in the log.

I have installed the component via HACS, setup my Ajax alarm and configured HA, which I think is correct. I have not done anything special or weird, and I truly hope that I am not wasting your time by logging this.

The sensors have been setup in HA as expected, however, I believe due to the Unhandled event type, these sensors are not updating correctly. This is for basic arming and disarming events.

If you need any more testing done, please let me know, I cannot develop in python, but am more than happy to help debug and assist in any form of testing you may require.

Debug log

2019-09-11 21:00:14 DEBUG (Thread-3) [custom_components.sia] Income raw string: 12900075"SIA-DCS"1682L0#FED[0796FD162A234FA69D50F2CECEBCB631FC055869C0081B3EE7C3A8AC37476C253BCDBBA1149E938E8CF00A20EAE6A955 2019-09-11 21:00:14 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line12900075"SIA-DCS"1682L0#FED[0796FD162A234FA69D50F2CECEBCB631FC055869C0081B3EE7C3A8AC37476C253BCDBBA1149E938E8CF00A20EAE6A955 2019-09-11 21:00:14 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line found data: [0796FD162A234FA69D50F2CECEBCB631FC055869C0081B3EE7C3A8AC37476C253BCDBBA1149E938E8CF00A20EAE6A955 2019-09-11 21:00:14 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.manage_string data: dT65#\�@��|#FED|Nri0/RP0000]_19:00:13,09-11-2019 2019-09-11 21:00:14 DEBUG (Thread-3) [custom_components.sia] Parsing: |#FED|Nri0/RP0000]_19:00:13,09-11-2019 2019-09-11 21:01:14 DEBUG (Thread-3) [custom_components.sia] Income raw string: 18880075"SIA-DCS"1683L0#FED[01AF5D6532FC084E1858765C03B2448547DFDB890BCB6D467F9973726737B35E69CADCD445A91697FB2DDF72348C35A8 2019-09-11 21:01:14 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line18880075"SIA-DCS"1683L0#FED[01AF5D6532FC084E1858765C03B2448547DFDB890BCB6D467F9973726737B35E69CADCD445A91697FB2DDF72348C35A8 2019-09-11 21:01:14 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line found data: [01AF5D6532FC084E1858765C03B2448547DFDB890BCB6D467F9973726737B35E69CADCD445A91697FB2DDF72348C35A8 2019-09-11 21:01:14 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.manage_string data: ;X���S���|#FED|Nri0/RP0000]_19:01:13,09-11-2019 2019-09-11 21:01:14 DEBUG (Thread-3) [custom_components.sia] Parsing: |#FED|Nri0/RP0000]_19:01:13,09-11-2019 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] Income raw string: 15BB0075"SIA-DCS"1684L0#FED[8F34A78503C3A6005D289AE5934F832B743417D0FB137BC0865AB01E6FF5DDE3706B585A13402C44A5D3BFAA143EB0D3 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line15BB0075"SIA-DCS"1684L0#FED[8F34A78503C3A6005D289AE5934F832B743417D0FB137BC0865AB01E6FF5DDE3706B585A13402C44A5D3BFAA143EB0D3 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line found data: [8F34A78503C3A6005D289AE5934F832B743417D0FB137BC0865AB01E6FF5DDE3706B585A13402C44A5D3BFAA143EB0D3 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.managestring data: (��Ek��O|#FED|Nri1/NL501]_19:01:20,09-11-2019 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] Parsing: |#FED|Nri1/NL501]_19:01:20,09-11-2019 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] Income raw string: BE980075"SIA-DCS"1685L0#FED[FA0370307EABE5FC4AF264B0F205FCBE91D91E63E8B1840482A889DD3057089EEE4AF5995C6B1E3EE1BE5C76C820133D 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_lineBE980075"SIA-DCS"1685L0#FED[FA0370307EABE5FC4AF264B0F205FCBE91D91E63E8B1840482A889DD3057089EEE4AF5995C6B1E3EE1BE5C76C820133D 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line found data: [FA0370307EABE5FC4AF264B0F205FCBE91D91E63E8B1840482A889DD3057089EEE4AF5995C6B1E3EE1BE5C76C820133D |#FED|Nri3/NL501]_19:01:20,09-11-2019[custom_components.sia] EncryptedHub.manage_string data:  4i�?��B= 2019-09-11 21:01:21 DEBUG (Thread-3) [custom_components.sia] Parsing: |#FED|Nri3/NL501]_19:01:20,09-11-2019 2019-09-11 21:01:22 DEBUG (Thread-3) [custom_components.sia] Income raw string: E69E0075"SIA-DCS"1686L0#FED[32B6A0AC723F31107BCFCD8795AFC816705C1C400B0CEA349E40B95AD8814B18D80DB97B9F3C6DB4ABF745461E63D344 2019-09-11 21:01:22 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_lineE69E0075"SIA-DCS"1686L0#FED[32B6A0AC723F31107BCFCD8795AFC816705C1C400B0CEA349E40B95AD8814B18D80DB97B9F3C6DB4ABF745461E63D344 2019-09-11 21:01:22 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line found data: [32B6A0AC723F31107BCFCD8795AFC816705C1C400B0CEA349E40B95AD8814B18D80DB97B9F3C6DB4ABF745461E63D344 2019-09-11 21:01:22 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.manage_string data: �� 2019-09-11 21:01:22 DEBUG (Thread-3) [custom_components.sia] Parsing: |#FED|Nri4/NL501]_19:01:20,09-11-2019

eavanvalkenburg commented 5 years ago

Thanks! @moodiejo, one other question, I see three events types that are unhandled, CG, CF and OG, seems like CG and OG are for arming and disarming one particular area, is that when you use the Groups function in Ajax? and what causes the CF state (System armed, some zones not ready), does that mean you arm one area, but in another area a door is open or something?

moodiejo commented 5 years ago

Hi, I have 4 groups configured, with different sensors on each zone. I am therefore using groups within the Ajax. All 4 groups have been detected by the component, and 4 individual alarm_control_panel entities within HA have been created.

This behaviour occurs irrespective of how I try to disarm or arm the alarm. Let me try and give better examples. In the example below, I have armed a single Group, named 'Outside Not Pet Friendly' and the log shows this:

2019-09-12 19:43:18 DEBUG (Thread-3) [custom_components.sia] Income raw string: 31AC0075"SIA-DCS"3088L0#FED[8C66611F50B6A868B90771F4953E67C388CCFAEA1B86B1BF9187483D4A425B85B35A2E23A363ABD5D380E224DFB37A3E 2019-09-12 19:43:18 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line31AC0075"SIA-DCS"3088L0#FED[8C66611F50B6A868B90771F4953E67C388CCFAEA1B86B1BF9187483D4A425B85B35A2E23A363ABD5D380E224DFB37A3E 2019-09-12 19:43:18 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line found data: [8C66611F50B6A868B90771F4953E67C388CCFAEA1B86B1BF9187483D4A425B85B35A2E23A363ABD5D380E224DFB37A3E 2019-09-12 19:43:18 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.manage_string data: E��d���%�!�|#FED|Nri4/CG501]_17:43:17,09-12-2019 2019-09-12 19:43:18 DEBUG (Thread-3) [custom_components.sia] Parsing: |#FED|Nri4/CG501]_17:43:17,09-12-2019 2019-09-12 19:43:18 WARNING (Thread-3) [custom_components.sia] Unhandled event type: Code: CG, Type: Close Area, Description: System has been partially armed, Concerns: Area number, Message: CG501

I have now armed a different Group, named 'Outside Pet Friendly' and the log shows:

2019-09-12 19:45:18 DEBUG (Thread-3) [custom_components.sia] Income raw string: 31160075"SIA-DCS"3093L0#FED[BAD63D5932E2596C63FEC6A6DBD32DEFB7355C84C5AEBF4F4848D65C5C2FB0A8EACC13E4B0FA42D7A52EB8973C147A12 2019-09-12 19:45:18 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line31160075"SIA-DCS"3093L0#FED[BAD63D5932E2596C63FEC6A6DBD32DEFB7355C84C5AEBF4F4848D65C5C2FB0A8EACC13E4B0FA42D7A52EB8973C147A12 2019-09-12 19:45:18 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.process_line found data: [BAD63D5932E2596C63FEC6A6DBD32DEFB7355C84C5AEBF4F4848D65C5C2FB0A8EACC13E4B0FA42D7A52EB8973C147A12 2019-09-12 19:45:18 DEBUG (Thread-3) [custom_components.sia] EncryptedHub.manage_string data: ��nžeq/�?�|#FED|Nri3/CG501]_17:45:17,09-12-2019 2019-09-12 19:45:18 DEBUG (Thread-3) [custom_components.sia] Parsing: |#FED|Nri3/CG501]_17:45:17,09-12-2019 2019-09-12 19:45:18 WARNING (Thread-3) [custom_components.sia] Unhandled event type: Code: CG, Type: Close Area, Description: System has been partially armed, Concerns: Area number, Message: CG501

The CF state occurs when I try and arm a group, and as an example, I have a door that is open that is linked to that Group, and the door has the Ajax Door Contact, which at that stage would be deemed open.

eavanvalkenburg commented 5 years ago

So, the CG are taken care of, I'll update this repo today, just for the CF state, what would be the expected state for that Alarm in HA? keep it at Disarmed, or set it to Armed? I'm a bit limited by the possible states that HA has for alarms (see here).

moodiejo commented 5 years ago

Good question, I am leaning towards 'armed_custom_bypass'

The Group is actually armed, however, some sensors are bypassed....

eavanvalkenburg commented 5 years ago

Just added those, please have a look @moodiejo

moodiejo commented 5 years ago

Hi,

The component is installed, looks good so far.

I will let it run for a few days, and report back

Thank You !