Closed josetomas95 closed 2 years ago
The devicetype
in the requests doesn’t make sense, 2.11.9 is the firmware version; the devicetype
is a single integer, and should be 0 for the 2.0 smart lock.
This doesn’t look good, but I think it’s mitigated when you restart Homebridge, causing devicetype
to be updated.
Looking at the code, the wrong value is set when the accessory is initialised, either because it's newly created or restored from persisted cache. The right value is set when the bridge is polled. Also the but doesn't affect the Opener. I think you might have a communication issue between Homebridge NB and the Nuki bridge, unrelated to this bug. I would need to see the full log for that, please attach the log file (rather than copy/pasting large amounts of logs).
In v1.2.7.
Hi, I´m Jose I have installed the plugin and managed to pair it with the Bridge perfectly. In Homekit, the lock, the Nuki Opener appear as another lock, and then a doorbell from the Opener. The problem is that pressing to lock or unlock the lock does nothing, pressing the Nuki Opener does not react either.