Hello,
Unfortunately the HomeCenter 3 QuickApp is not working anymore after an upgrade from Fibaro.
Now I cannot use the Nuki doorlock anymore as I want.
Does someone have a solution for this? I’m at a point to replace the Nuki, due to the missing integration with Fibaro HC3…
Any news with the HC3 integration? The main reason I bought Nuki 3 Pro was the Fibaro HC integration, and after the inital setup, I realised that Nuki is not working properly with HC3… shame
Buenas a todos, yo también estoy interesado en integrar Nuki 3 o Nuki 3 Pro con HC3.
HC3 tiene el hardware para comunicarse con bluetooth, pero todavía desde Fibaro no han desarrollado la funcionalidad en el software.
¿cuando en HC3 habiliten el bluetooth se podrá integrar el Nuki sin necesidad de Bridge?
Nuki 4 Pro, bridge and Fibaro Home Center 3 here and also interested on a development of this integration. Any news? Will try to integrate all with Home Assistant, but whould appreciate a direct integration with Fibaro HC3.
Hope you are doing very well! My special thanks to the developers of this QA. I had some issues especially with 401 errors, where my API token was not authorized. At the end I had to use the Swagger UI to find the solution. You cannot control the NUKI using the request to the URL. You need to go through the nuki.web API. Also, you need to specify the correct DeviceID of NUKI. This is the HEX you find in your device, plus a prefix 1,2,3,4 (more information can be found in the config file), and then this value converted to decimal (hex to dec). I have also made a few updates to the code, thanks to this QA, another QA, and the assistance of ChatGPT (I am not a code developer). Feel free to use. Once again, thank you to the rest of the guys doing this, I just did some changes to make it work.
Add the QA to Fibaro
Go to web.nuki create an API token
Find your deviceID in HEX
Decide the correct prefix (for Nuki 3 or 4 is 4), convert the HEX plus prefix to dec
Go to Fibaro → QA → Edit → Go to config file → Add the values of your IP, port, token, device ID. (actually now that I think of that maybe IP, and port, are not necessary because they are not used, using the new method of logging in using Device ID and API token).
Save, run
I will try to update with a newer version, if have time, with changes to remove the IP, port, if they are not required.