Since unlatched is not reported reliably (because it is so transient), it is not mapped to HA states (and IIRC is not a currently supported state for lock
).
Yes, the idea is to get independant of the bridge, for whatever reason. Iâve never owned one, but I heard they can be quite unreliable. Also no need for a cloud connection.
Iâm not really sure sure why you have a delay with triggering actions. Either your ESP receives them late via MQTT for some reason, or the bluetooth comunication has problems. You could check the serial output, as soon as an action is received by the ESP, itâs logged.
I donât quite get the idea about unlatching after closing. I mean this isnât something the ESP should be doing, but could be handled by HA. Checking the source of the action isnât integrated in HA yet I think, but published via MQTT. âlock/authorizationIdâ reports the last user id. If itâs not equal zero, the source should be an app or a fob.
You already expose the âlast triggerâ sensor (automatic
, button
, manual
, system
) to HA.
Thanks
Wasnât sure and didnât really have time to check.
Hello Technyon, thanks for this great project! While researching the W5500 board, I came across the WT32-ETH01 board (an ESP32 board with additional Ethernet capabilities). Do you have experience with this in connection with your ESP32 Nuki Hub?
Hi,
I actually had a look at that board already, as a ready-to-go solution with ethernet on-board would be nice. I dropped the idea, because it unfortunately doesnât have USB-to-serial built-in, which makes the initial flash more of a hassle. As of now it doesnât work, because it uses an LAN8720A chip for ethernet connectivity, and not the W5500. To make it work, the LAN8720A driver needs to be included in the firmware.
Hi everyone, i just set up the nuki hub, and have been succesfully pairing it with my smart lock 3.0 pro.
It shows up in HA as expected, BUT:
-sometimes the reading are off. i mean, battery at 105% (real level:67%).
-It looks like the nuki hub interferes with my nuki app; i canât send any command via HAâŚ
And sometimes the lock disconnects from wi-fi;
Does anyone else experence such strange behaviors?
EDIT: it looks like the commands are sent by HA, with a 8-9 minutes delayâŚ
what I need to do with MQTT?
someone can show me the steps? screenshots or video?
I just flashed and the MQTT is âonâ in web interface, the nuki will come today and I will pair him, but how I do the discovery?
thanks
You just need to enter your credentials for MQTT in the webinterface of the esp32. When connected to MQTT the esp32 is autodiscovered by home assistant and all the locks paired with it.
If i remember right to pair the lock just set it in pairing mode and reboot the esp32, then it should discover the lock and pair it.
Iâll recheck the code regarding the battery level. Regarding the Wifi issues, I can highly recommend to get a W5500 module and connect via LAN if possible.
Thank you for your answer.
I think everything is Related to the wifi problem, since after a few hours the reading is ok.
The delay problem could be solved with the LAN module, in your opinion?
If itâs related to the wifi problems yes. If the ESP somehow gets disconnected from MQTT and only reconnects minutes later, the lock command would be executed once reconnected.
Last question, i swear.
IT looks like this interferes with my nuki app too; from time to time, the door goes offline on the app, too.
Never happened before.
Has this occurred to other users?
Thank you for your time and effort.
Hi, I have already configured the hun and it works perfectly and I wanted to add the W5500 module, can I ask you how to configure the W5500 ethernet module on the esp32? I connect it physically and then? A thousand thanks
Connect all the wires as described in the readme. When connecting GND with Pin 26, the firmware switches Wifi off and switches to W5500 mode.
thaks, I connected the wires as written in the document but nothing happens, I double-checked the connections several times, but is the w5500 module powered? on the module I have two gnd pins and one called sclk and scs, I interpreted them W5x00 SCK to GPIO18 and W5x00 CS/SS to GPIO5, correct?
Hi,
which module are you using?
Well I didnât mention it in the readme, but you of course have to connect VCC so the module has power to operate. SCK to 18 and CS/SS to 5 is correct.
the pins that the module are: sclk scs mosi miso 3,3v gnd in rst gnd and 5v
VCC is 3.3V PIN or 5V PIN. I connected it to the 3.3V PIN on my ESP.