Trigger web post/MQTT command to activate a relay

[polclota]

My intention is to trigger a relay attached to a ESP module with an internal web server or even better to trigger a MQTT command both from Nuki app/web so I can save my clients sometime avoiding the use of two different apps/webs. Thanks in advance.

[Stephan (Stephan Lendl)]

Do you have something similar in mind as descirbed in this feature request?

Provide callbacks in Web API

Product name Web API Summary Provide “/callback” endpoint in the Web API the same way it is already provided in the Bridge HTTP-API. Features Allow to register public (https) web services to be notified on lock/door state changes. Reason Enable web services to trigger actions in realtime following lock/door state changes instead of having to poll “/smartlock” every minute for the status. Examples Nuki callback notifies webservice that door is unlocked, webservice immediately turns on all Phi…

[polclota]

Yes, that would help a lot but MQTT support on bridge side would be even better…

[Stephan (Stephan Lendl)]

We already had some discussion about this too:

MQTT support

Hi! For integration to a Smart Home, does Nuki have thought about an MQTT integration into the bridge, to publish it’s state, and let control the SmartLocks? Most (I would say, all) home automation software supports MQTT, it is an easy to implement protocol, and it is an open standard. It would make special callback handlers unnecessary. Regards, Christian

[polclota]

I see, interesting approach with .NET…I’ll chek it out.

[aqualx (Oleksandr Kurbatov)]

It’s a pity that this solution only for Windows . While most home automations run on Linux…
MQTT client runs great on cheap ESP-01 module. I hope it is not a big deal to add support of MQTT to nuki bridge natively.
For me current integration with Home Assistant via HTTP-Api is very unreliable as I often get delays and errors like this:

• Failed to establish a new connection: [Errno 111] Connection refused’
• socket.timeout: timed out. … HTTPConnectionPool(host=‘xxx.xxx.xxx.xxx’, port=8080): Read timed out. (read timeout=5)

I understand that this may occur when someone interacts with nuki bridge via android application or web api or maybe directly with a lock via Bluetooth. But anyway, all this issues will just disappear after switching to MQTT as sending/receiving of messages will become a problem of MQTT server (that is stable enough).

[polclota]

I totally agree, I get the same problem with my Home Assistant config running raspbian on a RPI through hardware Nuki bridge. MQTT support would make all this really easy.