Jevgeni Kiski
1. Strange, should be filtered out. 2. Not possible with the current implementation.
Give me an example of an event that comes through.
Or check yourself. If you have EVO then this is correct file: https://github.com/ParadoxAlarmInterface/pai/blob/dedc352b9babcac198821003bcbc6c79a99f57e0/paradox/hardware/evo/event.py#L509 Maybe tags are missing for your event.
Also if you want to study the subject in depth here are tests that describe possibilities pretty well: https://github.com/ParadoxAlarmInterface/pai/blob/dev/tests/lib/test_event_filter.py
Add "-zone_tamper_trouble=False". Should fix. And "-trouble=False", to discard "No trouble for ..." 'trouble,-clock,-restore,-zone_tamper_trouble=False,-trouble=False',
Not that simple. We have two things that emit events that end up sending notifications. - Live events sent by the panel. - Property changes that were detected during RAM...
You need to stop PAI, then remove everything related to PAI in MQTT explorer (retain flag?). I remember HA has removed deleted conf entries for me.
@elupus Can you please review this PR.
@vtamm, @elupus Do we still want to merge this?