search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.86k stars 30.1k forks source link

SIA Alarm Showing as unavailable after upgrade to 8.6 #54504

Closed jb123567 closed 2 years ago

jb123567 commented 3 years ago

The problem

Ajax alarm was working with SIA intergration prior to upgrade to 2021.8.6, now reporting as unavailable.

What is version of Home Assistant Core has the issue?

8.6

What was the last working version of Home Assistant Core?

8.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

SIA Alarm

Link to integration documentation on our website

https://www.home-assistant.io/integrations/sia/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2021-08-11 22:08:21 DEBUG (MainThread) [pysiaalarm.base_server] Incoming line: 6EDD0075"*SIA-DCS"8959L0#AAA[A99CB4359155815BB119C65A30ED125F79717A05AB0595EC96DCDBE571370C7E20B115644551DDA6FAD3449AB6E73703
2021-08-11 22:08:21 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': 'AAA', 'ti': None, 'id': None, 'ri': '0', 'code': 'RP', 'message': '0000', 'xdata': None, 'timestamp': '21:09:04,08-11-2021'}

Additional information

No response

probot-home-assistant[bot] commented 3 years ago

sia documentation sia source (message by IssueLinks)

probot-home-assistant[bot] commented 3 years ago

Hey there @eavanvalkenburg, mind taking a look at this issue as it has been labeled with an integration (sia) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

eavanvalkenburg commented 3 years ago

@jb123567 the integration will turn entities to unavailable based on the setting for the ping interval, so if that is not set to the same value as in your alarmsystem then that will cause weird behaviour, there were no changes in 8.6, so shouldn't have anything to do with that. Please let me know if you still have this after fiddling with the settings of your alarm a bit.

jb123567 commented 3 years ago

Both Ajax and Intergration are set to 1 minute. It seems looking at the logs the alarm is sending the data every 10 seconds, which I guess is what is probably causing the issue?? Ajax update maybe?

eavanvalkenburg commented 3 years ago

Does Ajax show that it is connected to the Monitoring Station?

jb123567 commented 3 years ago

No, showing as disconnected.

jb123567 commented 3 years ago

No matter how much I play around with different settings, still showing as unavailable.

What is strange is Home assistant is clearly receiving the data.

2021-08-12 15:45:44 DEBUG (MainThread) [pysiaalarm.base_server] Incoming line: 03650039"SIA-DCS"9667L0#AAA[#AAA|Nri0/RP0000]_14:46:31,08-12-2021 2021-08-12 15:45:44 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': 'AAA', 'ti': None, 'id': None, 'ri': '0', 'code': 'RP', 'message': '0000', 'xdata': None, 'timestamp': '14:46:31,08-12-2021'}

jb123567 commented 3 years ago

Here is the full section from the logs, I have ticked ignore timestamps.

2021-08-12 15:49:44 DEBUG (MainThread) [pysiaalarm.base_server] Incoming line: 9ED60039"SIA-DCS"9671L0#AAA[#AAA|Nri0/RP0000]_14:50:31,08-12-2021 2021-08-12 15:49:44 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': 'AAA', 'ti': None, 'id': None, 'ri': '0', 'code': 'RP', 'message': '0000', 'xdata': None, 'timestamp': '14:50:31,08-12-2021'} 2021-08-12 15:49:44 WARNING (MainThread) [pysiaalarm.base_server] Event timestamp is no longer valid: 2021-08-12 14:50:31+00:00 2021-08-12 15:49:44 DEBUG (MainThread) [pysiaalarm.base_server] Incoming line: 8C970025"SIA-DCS"9671L0#AAA[#AAA|Nri0/RP0000] 2021-08-12 15:49:44 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': 'AAA', 'ti': None, 'id': None, 'ri': '0', 'code': 'RP', 'message': '0000', 'xdata': None, 'timestamp': ''}

eavanvalkenburg commented 3 years ago

if the ignore timestamp is mentioned you shouldn't see this line: Event timestamp is no longer valid: 2021-08-12 14:50:31+00:00 2021-08-12 15:49:44 DEBUG (MainThread) please check!

ceeessbee commented 3 years ago

Hi @eavanvalkenburg , I am also having issues with Ajax showing entity not available. I had made no changes to the working config before it stopped working, and have tried reinstalling but no luck. The logs are showing the same message every 10 seconds:

2021-09-09 16:52:13 WARNING (MainThread) [pysiaalarm.base_server] Unknown or non-existing account (00082E2E) was used by the event: Content: None, Zone (ri): None, Code: None, Message: , Account: 00082E2E, Receiver: None, Line: L0, Timestamp: None, Length: 007A, Sequence: 7541, CRC: A9DD, Calc CRC: A9DD, Encrypted Content: 8863C5239EB117CA688E23317813F4DD1F50EE765B5DA54B3361E4D316661BB13768793B1CA98C08EC6517CD822C81DD, Full Message: "*SIA-DCS"7541L0#00082E2E[8863C5239EB117CA688E23317813F4DD1F50EE765B5DA54B3361E4D316661BB13768793B1CA98C08EC6517CD822C81DD.

The account is the same as what is showing in Ajax, the ping is 1 minute on both sides, and Ajax is showing the monitoring station is not connected. Pretty much at a loss to know where to go with this. Appreciate a clue of what to do next, and thank you.

eavanvalkenburg commented 3 years ago

and you are sure that the account in the config is the exact same (including those 0's) in both your config and ajax? you don't need to pad the account if that is what you did!

ceeessbee commented 3 years ago

and you are sure that the account in the config is the exact same (including those 0's) in both your config and ajax? you don't need to pad the account if that is what you did!

Hi @eavanvalkenburg , I've only just had chance to look at this again. I started from the beginning and deleted the configuration, restarted HA. Then using Samba, I edited the HA config .storage files 'registry' and 'restore' files to remove any references to entities and devices, also deleted the log and database files to ensure a clean start. Restarted HA again and re-installed the official SIA configuration. I noted your point about not padding the account but sadly I am still getting the same 'unknown or non-existing account' message and not picking up the entities.

Should I try the HACS version which I used previously to see if that might work?

Thanks for you assistance, appreciated.

github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.