Tested behaviour — Abbas Dominus3 Security System

What was verified on real hardware. A limitation here belongs to the hardware, not to the adapter — where the panel cannot do something, it is recorded rather than hidden.

These results come from Protequ's behavior tests. They show how closely the adapter matches standard PQ behavior. An adapter is not required to pass them all, so a difference here is a fact to weigh, not proof of a defect.

Result	Scenarios
Could not be tested — hardware missing	2
Does not apply here	3
Works as expected	36

What was checked

Checked	Result	Note
The adapter connects to the device and reports itself online.	Works	—
A command that reaches the device is confirmed, not silently dropped.	Works	—
An operator command is confirmed by its paired audited event in the remote form, with attribution.	Works	—
A remote actuation whose action has a .remote audit variant surfaces as that attributed remote event — no adapter declares it ACK-only.	Works	—
An invalid credential configuration is rejected, not accepted and silently ignored.	Works	—
Restarting the adapter neither duplicates audited history nor re-pushes unchanged data.	Works	—
State is read back from the device after startup, not merely accumulated from events.	Works	—
The adapter writes the device clock and the change is observable.	Works	—
A command is confirmed on the Thing it was issued for, never on a sibling sharing its command — on every type where the rig offers a pair.	Works	—
Arming a partition from PQ arms it and is confirmed by an event.	Works	—
Disarming a partition from PQ disarms it and is confirmed by an event.	Works	—
Partial/stay arming maps to the correct PQ partial-arm shape.	Not applicable	—
A redundant arm on an already-armed partition fails fast, without hanging on a confirming event that cannot come.	Works	—
Arming with an open zone is refused (or force-armed) with the correct PQ outcome.	Works	—
A force override arms a partition that plain arming refuses, with a distinct outcome.	Not applicable	—
Violating an armed zone raises an alarm on the correct zone/partition.	Not tested	—
The alarm's restore/clear is reported, not swallowed.	Not tested	—
Arming one partition leaves every other partition untouched.	Works	—
A disarm issued during the exit delay resolves definitely, without an alarm.	Works	—
A protocol message split across transport segments is reassembled before it is parsed.	Not applicable	—
A command aimed at a Thing the running adapter does not hold fails fast with a reason.	Works	—
A command issued while the channel is held exclusively is refused, not deadlocked.	Works	—
Re-importing does not duplicate Things and preserves reconciled properties.	Works	—
Importing the device configuration builds a tree matching the physical panel.	Works	—
A single credential change takes the sync path the device supports.	Works	—
Running sync twice with unchanged input is a no-op on the PQ side.	Works	—
A full synchronization moves the whole owned AAT access dataset and reports the moved identities.	Works	—
A reset clears the device tables and re-pushes the whole dataset.	Works	—
A credential update is applied in place, not by duplicate.	Works	—
A sync never deletes a device address it created or updated in the same batch, so changing one person's credential set updates their existing records instead of destroying them.	Works	—
Incremental synchronization after one person changes touches only that person and required dependencies.	Works	—
Selective synchronization with multiple pending people moves only the selected person.	Works	—
Bypassing a zone from PQ takes effect and is confirmed.	Works	—
Removing a bypass from PQ restores the zone and is confirmed.	Works	—
A strike release from PQ opens the door momentarily and is confirmed.	Works	—
A permanent-open (unlock) command holds the door open until cancelled.	Works	—
Deadbolt lock/unlock is exposed where the protocol has a real lock actuator.	Works	—
A momentary remote door open can be repeated without leaving stale door state.	Works	—
A person granted arm/disarm rights on a subsystem has that authorization synced to the panel.	Works	—
A standalone PIN (no card) uploads as an independently usable code, not dropped and not merged onto a card.	Works	—
A schedule-bound grant uploads its time profile to the device (config, distinct from enforcement).	Works	—