PGM activation and spurious zone status
## Alarm system
EVO192  (V6.86) + IP100 (V5.1) + Hassio
baudrate 57600+ "System Options -> Communication -> “Transmit zone status on serial port” " activated

## Environment
- RPI + Python version 3.8

## Git branch
V2.7.1

## Describe the bug
A PGM is used to open the motor driven gate. PGM is activated through MQTT message "on" and deactivated with a 2s timer (defined in EVO panel) to generate a pulse (duration 1 to 2s) on the gate controler.
A magnetic sensor switch is used to detect the gate close status and connected to one EVO zone.
I observe (In PAI log and through send MQTT messages) spurious status on zone associated to the gate: when an open request is done through PAI (and the PGM) the gate open (normal), the zone status first change to open (correct),   **1s later change back (error) to close** then back to open (correct finally) 10 s after.

This spurious behaviour **is seen** on other zones which are opened simultaneously with the gate (just after PGM activation).

This spurious behaviour of the zone status is not seen if the PGM is activated through another method (EVO remote control->utility key->PGM) or via direct activation of the gate controler.

=> it seems that zone status reported just after a PGM activation are valid during 1 s, corrupted during 10s and correct after.


## To Reproduce
When the MQTT message is end to open the gate:
- the PGM is well activated.
- the zone open status open is well changed to True (in the log) and corresponding MQTT message send
- But one second later the open status open is erroneously send back to False (with erroneous MQTT message send)
- Around 10 s later the zone open status is corrected (with associated MQTT message)

## Logs
It seems it is not possible to send you logs through keybase.io (Error: no valid primary key self-signature or key(s) have expired)

So I send you commented extract without sensitive info:

#### an MQTT message is sent (from Hassio) to open the gate through PAI and the PGM "Portail"
2022-03-19 11:02:53,644 - INFO     - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/outputs/Portail, payload=on
2022-03-19 11:02:53,646 - DEBUG    - PAI.paradox.interfaces.mqtt.basic - Output command: Portail=on user: None
2022-03-19 11:02:53,646 - DEBUG    - PAI.paradox.paradox - Control Output: Portail - on
**2022-03-19 11:02:53,784 - INFO     - PAI.paradox.hardware.evo.panel - PGM command: "on" succeeded**
2022-03-19 11:02:53,970 - DEBUG    - PAI.paradox.hardware.evo.panel - Received status response: 1
.....
2022-03-19 11:02:55,127 - DEBUG    - PAI.paradox.hardware.evo.panel - Received status response: 7
####Here (2s later) we can see the zone "Portail" status changed from False to True, it is correct
**2022-03-19 11:02:55,307 - DEBUG    - PAI.paradox.data.memory_storage - Change zone/Portail/open from False to True**
#### corresponding MQTT message is send : :-) !
2022-03-19 11:02:55,312 - DEBUG    - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/states/zones/Portail/open=True
....
#### But here (1.5s later) the zone "Portail" status is change back to False, it is an ERROR, electrical status of the input didn't change, this event is not seen with PRT3
2022-03-19 11:02:56,611 - DEBUG    - PAI.paradox.hardware.evo.panel - Received status response: 58
2022-03-19 11:02:56,843 - DEBUG    - PAI.paradox.paradox - pgm/line_ring:False ignored
2022-03-19 11:02:56,845 - DEBUG    - PAI.paradox.data.memory_storage - Change system/date/time from 2022-03-19 12:02:41 to 2022-03-19 12:02:47
2022-03-19 11:02:56,845 - DEBUG    - PAI.paradox.data.memory_storage - Change system/power/vdc from 16.6 to 16.5
2022-03-19 11:02:56,845 - DEBUG    - PAI.paradox.data.memory_storage - Change system/power/dc from 11.5 to 11.6
**2022-03-19 11:02:56,847 - DEBUG    - PAI.paradox.data.memory_storage - Change zone/Portail/open from True to False**
2022-03-19 11:02:56,863 - DEBUG    - PAI.paradox.lib.ps - Future already done
2022-03-19 11:02:56,865 - DEBUG    - PAI.paradox.paradox - Could not create event from change
2022-03-19 11:02:56,865 - DEBUG    - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/states/system/date/time=2022-03-19 12:02:47
2022-03-19 11:02:56,865 - DEBUG    - PAI.paradox.paradox - Could not create event from change
2022-03-19 11:02:56,869 - DEBUG    - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/states/system/power/vdc=16.5
2022-03-19 11:02:56,869 - DEBUG    - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/states/system/power/dc=11.6
##### And the corresponding MQTT erroneous message is send
2022-03-19 11:02:56,870 - DEBUG    - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/states/zones/Portail/open=False
.....
#### 10 second later the  zone "Portail" status is  definitely corrected to True
022-03-19 11:03:06,544 - DEBUG    - PAI.paradox.hardware.evo.panel - Received status response: 58
2022-03-19 11:03:06,726 - DEBUG    - PAI.paradox.paradox - pgm/line_ring:False ignored
2022-03-19 11:03:06,728 - DEBUG    - PAI.paradox.data.memory_storage - Change system/date/time from 2022-03-19 12:02:47 to 2022-03-19 12:02:57
2022-03-19 11:03:06,728 - DEBUG    - PAI.paradox.data.memory_storage - Change system/power/dc from 11.6 to 11.7
**2022-03-19 11:03:06,730 - DEBUG    - PAI.paradox.data.memory_storage - Change zone/Portail/open from False to True**



