Product name
Nuki Bridge
Summary
Support MQTT binding for status and commands
Features
Basics:
- Topic base configurable
- Subtopic Bridgeid
- Subtopic Nukiid
- LWT for Bridge State
- Broker Hostname:Port
- Authentication
- Payload may be plain or json
Publish Nuki status:
- Locked/Unlocked state
- Door open/closed state
- Bridge online state
- Nuki online state
Commands
- Lock/Unlock commands from the Bridge API
- Possibly all the commands from the Bridge API
The MQTT settings may be configured via the App
Reason
- Clean implementation of status push
- Broker handles multiple connections from Clients (subscriptions), not the Bridge webserver
- Defined heartbeat by LWT
- Auto-discovery possibly by announce pushes
- QoS is part of the protocol
- No need to manage/process multiple callbacks
- Serialization is done by the broker
- Lightweight binary protocol
- It’s a Standard
Examples
Easy integration in:
- FHEM
- Home Assistant
- IOBroker
- Loxone
- Direct Communication between infinite MQTT Client Devices
I know that this is currently not on the roadmap.
But if the discussion comes to a new interface, keep mqtt in mind as a standardized protocol over any foreign- or own-proprietary implementations.