Unable to 'Force' arm partitions on SP7000

[anarinia]

Hi,
I have been experimenting with this module on my house's SP7000 alarm system. It works very well, but I found the following malfunction (?)

According to ducumentation,

• paradox/control/partitions/name allow setting some partition properties where name identifies the partition. If the name is all, all partitions will be updated. The payload can have the values arm, arm_force, arm_stay, arm_sleep, arm_stay_stayd, arm_sleep_stay or disarm and disarm_all.

But 'arm_force' seems to be putting the system in 'STAY' mode, instead of normal 'ARM' mode, see following log entries:

2024-01-27 16:00:17,530 - INFO - PAI.paradox.interfaces.mqtt.basic - message topic=paradox/control/partitions/Ground_house/, payload=arm_force
2024-01-27 16:00:17,546 - INFO - PAI.paradox.interfaces.mqtt.basic - Partition command: Ground_house=arm_force user: None
2024-01-27 16:00:17,563 - DEBUG - PAI.paradox.paradox - Control Partition: Ground_house - arm_force
2024-01-27 16:00:17,825 - DEBUG - PAI.paradox.data.memory_storage - Change partition/Ground_house/exit_delay from False to True
2024-01-27 16:00:17,845 - DEBUG - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/states/partitions/Ground_house/exit_delay=True
2024-01-27 16:00:17,852 - DEBUG - PAI.paradox.data.memory_storage - Change partition/Ground_house/current_state from disarmed to arming
2024-01-27 16:00:17,873 - DEBUG - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/events/raw={"additional_data": {}, "change": {"exit_delay": true}, "id": 1, "key": "partition,Ground house,exit_delay=True", "label": "Ground house", "label_type": null, "level": "INFO", "major": 2, "message": "Partition Ground house in exit delay", "minor": 14, "module": "0xe", "name": "Ground house", "partition": 1, "tags": [], "timestamp": "2024-01-26T16:51:00", "type": "partition"}
2024-01-27 16:00:17,902 - DEBUG - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/events/raw={"additional_data": {}, "change": {"exit_delay": true}, "key": "partition,Ground_house,exit_delay=True", "label": "Ground_house", "level": "INFO", "message": "Partition Ground_house in exit delay", "partition": "Ground_house", "property": "exit_delay", "tags": ["exit", "delay"], "timestamp": 1706364017, "type": "partition", "value": true}
2024-01-27 16:00:17,920 - DEBUG - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/states/partitions/Ground_house/current_state=arming
2024-01-27 16:00:17,958 - DEBUG - PAI.paradox.paradox - Missing element ID in system/?, m/m: 3/2, message: Bell squawk arm
2024-01-27 16:00:17,974 - DEBUG - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/events/raw={"additional_data": {}, "change": {"current_state": "arming"}, "key": "partition,Ground_house,current_state=arming", "label": "Ground_house", "level": "INFO", "message": "", "partition": "Ground_house", "property": "current_state", "tags": [], "timestamp": 1706364017, "type": "partition", "value": "arming"}
2024-01-27 16:00:17,999 - DEBUG - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/events/raw={"additional_data": {}, "change": {}, "id": null, "key": "system,,", "label": "", "label_type": null, "level": "DEBUG", "major": 3, "message": "Bell squawk arm", "minor": 2, "module": "0xe", "name": "-", "partition": 1, "tags": [], "timestamp": "2024-01-26T16:51:00", "type": "system"}
2024-01-27 16:00:18,174 - DEBUG - PAI.paradox.data.memory_storage - Change partition/Ground_house/squawk from False to True
...
...
...
2024-01-27 16:00:20,445 - DEBUG - PAI.paradox.interfaces.mqtt.core - MQTT: paradox/events/raw={"additional_data": {}, "change": {"arm_stay": true}, "key": "partition,Ground_house,arm_stay=True", "label": "Ground_house", "level": "INFO", "message": "Partition Ground_house stay arm active", "partition": "Ground_house", "property": "arm_stay", "tags": ["arm"], "timestamp": 1706364019, "type": "partition", "value": true}

Force arming is supposed to be just like regular arming, but not bypassing zones which may be open at the time of arming.

Could there be something wrong with the code? Or is it just some setting specific to my particular alarm system?

Thanks!
Aris

P.S. I am using version 2.7.1

[yozik04]

Unfortunately we do not have any documentation on the binary protocol that SP7000 uses.
We are replicating what BabyWare does.
PARTITION_ACTIONS are action commands we are sending

After arming panel sends an event that we intercept. Possible events are in event_map
change parameter is what we will send in MQTT (if it really changes).

[anarinia]

Thank you for getting back!

I tried changing

arm_force=0x02,

to various random values, but still couldn't get the SP7000 to go into 'force arm' mode.

Perhaps the issue is limited to my specific environment - could be because I have disabled one-button arming on my system (?)
I will need to do some more tests at some point.