no ACL at this level (if you mean access control list). I just started to play with it 10 days ago - it was not working (disconnection after command) - I wrote here some new topic, but nobody responded to that for 10 days. Yesterday, I gave that a second try: lock was not calibrated so I calibrated it, connect it to MQTT, sent the command and it worked fo r 5 times. I was super happy, that I solved the problem. I started to test marginal scenarios like server disconnection and reconnections (how long will it take to reconnect). But after single reconnection it stopped working again. I wrote to support via Nuki App - no response for 24 hrsā¦
So I am pretty sure, that command is constructed according specification - as it was working for a while.
I forgot to mention, that lock had fw 3.7.2 Beta - yesterday. Today I have upgdraded it to 3.7.3 Beta - but no difference. My concert here is also with the Beta word. Iād like to have some stable fw in there.
I havenāt looked at the topic but itās not the best place to discuss this. Iāve found your other post, so I suggest going over it and closing this aside in this post.
Hello Christian, I see you are probably a Loxone user.
Could you give me a hint how to create the udp output to manage the lock?
I actually bought a smartlock 4.0 pro
Thanks in advance
Iām using the ioBroker MQTT Broker to read the data from Nuki. Unfortunately the lockActionEvent does not contain anything readable. It seems there is an error in the format Nuki is transmitting this value so the broker cannot interpretate the array as array (instead itās interpretated as binary)
Thereās a full topic about this on github:
Basically the raw data of this object looks like this: val":"\u0002\u0000Ģ\u0000\u0000
if you look careful you can see the third backslash looks weird
Unfortunately (for you) that seems to be an ioBroker problem, because the mqtt data is exactly coming in like described in the api specs in the first post.
You may install a mqtt sniffer (Mqtt Explorer or mqtt.fx or whatever) and see the raw data:
1,172,0,0,0 (Example from my SL3P, connected to openHAB, read from MQTT Explorer)
Then compare that to the api docs:
Unlatch via Keypad with
Auth-ID 54321 from Code-ID
12345:
3,0,54321,12345,1
Maybe developers can point us to some hints how encoding the data sent for iobroker.mqtt adapter.
In mosquitto i can see following data: Received PUBLISH from Nuki_xxxxxxxxx (d0, q2, r0, m59102, 'nuki/xxxxxxxxxx/lockActionEvent', ... (14 bytes))
In MQTT Explorer i can see correct conversion:
on ioBroker i see som Escape Sequences: ( kind of wrong encoding? )
Why are only some of the available MQTT topics created in HomeAssistant upon autodiscovery? Especially āstateā would be very interesting as one could trigger an automation in HomeAssistant if the SmartLock is locked. (e.g. enable surveillance cam recording in Frigate)
Is it true that the Nuki MQTT integration wonāt work if the Nuki cloud is not reachable? I am reading this here and there but hope that this is not true. Or is it only the case when using a Nuki bridge?
