Event timestamp is no longer valid

jyourstone commented 3 years ago

Version of the custom_component and HA setup (version, OS, etc)

SIA v0.5.0-beta.6 Home Asistant 2021.5.1 Supervisor 2021.04.3 Home Assistant OS 5.13

Configuration


                "entry_id": "xxx",
                "version": 2,
                "domain": "sia",
                "title": "SIA Alarm on port 8124",
                "data": {
                    "accounts": [
                        {
                            "account": "xxx",
                            "encryption_key": "xxx",
                            "ping_interval": 1,
                            "zones": 1
                        }
                    ],
                    "port": 8124,
                    "protocol": "TCP"
                },
                "options": {},
                "system_options": {
                    "disable_new_entities": false
                },
                "source": "user",
                "connection_class": "local_push",
                "unique_id": "sia_8124",
                "disabled_by": null

Describe the bug

Not sure if this happened after Ajax updated itself, but all of a sudden I cannot see the status of Ajax in Home Assistant anymore and in the Ajax app it says that the alarm central is disconnected.

The log file is filled with warnings (at the moment just 45 occurences since I just restarted HA to enable log debugging).

Debug log


Logger: pysiaalarm.base_server
Source: /usr/local/lib/python3.8/site-packages/pysiaalarm/base_server.py:126
First occurred: 8:37:33 AM (45 occurrences)
Last logged: 8:45:28 AM

Event timestamp is no longer valid: 2021-05-09 06:47:23+00:00
Event timestamp is no longer valid: 2021-05-09 06:47:33+00:00
Event timestamp is no longer valid: 2021-05-09 06:47:43+00:00
Event timestamp is no longer valid: 2021-05-09 06:47:53+00:00
Event timestamp is no longer valid: 2021-05-09 06:48:04+00:00

---

2021-05-09 08:37:33 DEBUG (MainThread) [pysiaalarm.base_server] Incoming line: xxx
2021-05-09 08:37:33 DEBUG (MainThread) [pysiaalarm.event] Content matches: {'account': 'xxx', 'ti': None, 'id': None, 'ri': '1', 'code': 'OP', 'message': '1', 'xdata': None, 'timestamp': '06:40:08,05-09-2021'}
2021-05-09 08:37:33 WARNING (MainThread) [pysiaalarm.base_server] Event timestamp is no longer valid: 2021-05-09 06:40:08+00:00

eavanvalkenburg commented 3 years ago

I have this issue with my alarm as well but ajax support hasn't helped, in the latest beta you can reconfigure with a ignore timestamp flag and then it works again!

jyourstone commented 3 years ago

Wow, that was a fast reply!

I did what you suggested and reconfigured SIA with a timestamp ignore flag and then restarted HA. In the Ajax app it's now connected to the alarm central, but in Home Assistant I still cannot see the alarm status, it just says unknown, even though I armed the system and then disarmed it again.

jyourstone commented 3 years ago

The alarm central in Ajax actually went back to disconnected after a while. So my problem remains, even after checking the ignore timestamp flag.

eavanvalkenburg commented 3 years ago

sorry, turned out I hadn't fully implemented the timeband pieces, that is done now in b7. have a try

jyourstone commented 3 years ago

It works!

Thank you! 😊

eavanvalkenburg / sia