It’s working. Thanks!
Here’s the updated table:
| Actions via | Lock | Unlock |
|---|---|---|
| Android app (Bluetooth off; Nuki reachable via Thread) | 2,0,912,0,0 | 1,0,912,0,0 |
| Android app (Internet off; Nuki reachable via Bluetooth) | 2,0,912,0,0 | 1,0,912,0,0 |
| Nuki Web | 2,0,123838,0,0 | 1,0,123838,0,0 |
| MQTT | 2,172,0,0,0 | 1,172,0,0,0 |
| Matter triggered (Home Assistant) | 2,171,0,0,0 | 1,171,0,0,0 |
Regarding my other observation:
The MQTT lockActionEvent payload does not provide a way to distinguish whether an action was triggered via Matter, Bluetooth, or Wi-Fi.
I have opened a feature request for that a few months ago (see bellow).
The rationale is that having an ID for Bluetooth separate from “system” can be useful for auditing, forensic analysis and troubleshooting.