Allow filter out MQTT sensor data

[Onepamopa]

Alarm system

EVO192

Environment

ESP32 -> HA

Git branch

DEV

Describe the bug

In HA's Logbook every 10 seconds:
EVO192 System Date Time changed to 2023-12-30 15:44:XX (where XX is every 10 seconds).
This spams and bloats the log A LOT as you can imagine.. with something that's not of any particular use.

If possible - add a way to suppress this particular message from being logged, or just disable it.

To Reproduce

Logs

[yozik04]

You can tune time syncing threshold.

[Onepamopa]

I set SYNC_TIME_MIN_DRIFT to 86400 -- no effect still spits the time every 10 seconds...

[Onepamopa]

@yozik04 any other ideas?

[yozik04]

Please share some logs as well. I have busy week. Will take a look during the weekend.

[yozik04]

Maybe you just need to replace clock battery 😃

[Onepamopa]

The panel hasn't indicated any issues with the RTC battery ... at least nothing in babyware.

Let me know what logs you need and I'll extract them.

[yozik04]

Ahh it is HA log... not the plugin's log. PAI sends all changed status data to mqtt every 10 seconds. I do not have a way to filter out some of the data at the moment.

[Onepamopa]

Yes.. HA log filling with nonsense every 10 seconds :)

[adammeghji]

Also observing the same issue with extremely chatty logs with "EVO192 System Date Time" polluting the Logbook every 10 seconds. Has anyone come up with a good workaround to suppress these?

[Onepamopa]

No .. the dev doesnt seem interested

[yozik04]

Create a PR I will merge. I have no time to deal with this at the moment. I have more things on the list as well.

[Onepamopa]

Create a PR I will merge. I have no time to deal with this at the moment. I have more things on the list as well.

Let me know which function is responsible for adding these to the log, and I'll do a PR.

[Onepamopa]

As a temp fix - click on the event in the logbook, go to settings and uncheck "Enabled" and "Visible". This stops it completely.

[adammeghji]

@yozik04 thanks for your hard work on this project, btw :) @Onepamopa I'll try that workaround, thanks a bunch.