The Smart Lock Pro 4 keeps logs of actions such as locking, unlocking, opening, and scheduled events. These logs include some contextual information, but they do not explicitly indicate the exact connection method used for each action (e.g., whether it was BLE, Wi-Fi, or Matter).
Is the connection method used for each specific action retrievable?
Do certain degree yes. Have a look at the MQTT spec description of triggers in the /lockActionEvent
Hi @Juergen
In the current MQTT API v1.4, triggers do not differentiate between Bluetooth, Wi-Fi, and Matter connections. All of these connection methods are represented by the same trigger ID (0 – “system / bluetooth command”). This lack is unsatisfactory for auditing, forensics and troubleshooting, where identifying the specific connection method used to trigger an action is often crucial.
To address this limitation, I recommend that Nuki introduce three distinct trigger IDs, one each for Bluetooth, Wi-Fi, and Matter, in the next revision of the API.
Please create a feature request for this (and vote for it).