Product name
MQTT API
Summary
Add three new trigger IDs, one each for Bluetooth, Wi-Fi, and Matter, to the next revision of the MQTT API (section 3.7 of the documentation)
Reason
In the current MQTT API v1.4, the /lockActionEvent does 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 is unsatisfactory for auditing, forensic analysis and troubleshooting, where identifying the specific connection method used to trigger an action is often crucial.