Konstantin
Konstantin
Indeed, in my case, `mode` attribute isn't present in the API output: Here is the output of `GetWhiteLed` call: ``` {'WhiteLed': {'auto': 1, 'channel': 0, 'state': 0}} ``` `GetDevInfo`: ```json...
One thing: > Home Assistant 2021.12.10 Not sure that current nuki_ng should work on that version. It's heavily outdated
Not sure I understand your case. Are you looking for a way to create another code entity via the home assistant? E.g. https://api.nuki.io/#!/SmartlockAuth/put_0 ?
I see. No, the keypad is paired with the Nuki lock and it can only open the lock.
Why do you think so? The project is too small for me to dedicate lots of time to. > Why is this? Probably no one needed it before?
I'm afraid you have wrong expectations, I personally wouldn't rely on this state to make any automation. Lock'n'go is an intermediate state, not a persistent one (like, locked, unlocked). The...
It's already supported, you just need to use the right sensor. `binary_sensor.nuki__locked` has only two states: locked and unlocked, but `sensor.nuki__state` has more (all supported) states.
Yeah, I also have an integration relying on the `unlatched` state change, and it's not super-reliable.
that is possible in general. There's a Web API for that. The component can already enable/disable keypad codes if you specify Web API token when adding the component.
Hmm, as polling is the only option available here, it won't be very reliable, but I can give a try