zilluss
Nuki V3 is working - Request to push latest improvements
Hi zilluss,
thank you for this great project which I recently found.
I successfully flashed my NRF52832 beacon and I can confirm that it works with a Nuki V3 (original hex file in build folder). I saw your new hex file here (#3) https://github.com/zilluss/Open-Nuki-Fob/issues/3#issuecomment-1143634934_ and this version does not work for me, but the original one in the build folder.
So I assume my PCB matches your PCB. Could you please push the mentioned changes to GH? ("it supports up to 50 locks and unlocks much faster") That would be awesome!
Cheers, Max
@zilluss would you be so kind as to push the mentioned improvements to GitHub, please? :)
I pushed the latest changes. It seems to build fine but since I haven't worked on it for a while, let me know if there are any issues so I can resolve them.
Unfortunately, the tag is no longer functional after flashing the firmware. However, the manually built firmware works correctly. Could you please upload the source code?
What do you mean upload the source code? I already pushed the changes. How did you build the firmware?
Oh, I see it now. GitHub is displaying the history incorrectly.
I'll try pulling all the changes and building it again.
Sorry, my mistake.
I compiled the binary, but first, I had to update the variables for the newer hardware revision. I flashed the firmware using the
sudo openocd -f custom_swd.cfg -d2 -c 'init_reset halt; init; halt; flash erase_sector 0 0 112; flash erase_sector 0 118 127;program nrf52832_xxaa_dfu_s132.hex verify; reset; exit'
but the output when attempting pairing reports the following:
app_timer: RTC: initialized. app: Initialization done app: Scanning for locks started app: Action to execute: 4 app: Connected to Nuki app: Disconnected from Nuki, reason: 0x13 app: Enter sleep mode
I'm looking into it. Do you have any idea what might be wrong? Before you pushed the changes to GitHub, it was working fine.
I’ve got it resolved. The application remains in the AS_WAIT_FOR_MTU_UPDATE state and waits indefinitely. However, if I skip this state, set DEFAULT_MTU_SIZE to 247, and go directly to the AS_MTU_UPDATED state, the pairing is successful, and door opening works again.
And could you please push the changes to the source code? Or did you already do that? At least I can only see the changes to the build files, not the source files. :)
I don't have permissions to create a PR, so I'm sending a patch with the change to set a fixed MTU fixed_mtu.txt
@pohlond Thanks for the fix, I'll update the code this week (Don't have a machine with all the Nordic SDK stuff setup atm)
@danielducu I have a V2 with which it works, I don't know about newer models though. I checked the Bluetooth API and nothing regarding pairing and unlocking changed, so I'd say it should work.
Nice @zilluss , will try!! .. nice work and btw, this project should be kept alive. Nuki fob is 59 euros around here lol.