Jan-Ole Schümann

I'm out of ideas so far. Like I said, there four values saved after pairing, which are deleted when unpairing. The state regarding pairing should be exactly the same as...

The keypad node should be fixed in the latest release. Adding door sensor or not can be discussed. If not available, it should reflect this in the door sensor node,...

I think the lock state in MQTT (not HA) should change to motor blocked. Probably the auto discovery can't pick it up.

@DaveTiff I think it would be useful to know what is published in the lock/state topic. Can you use an MQTT client like MQTT explorer and monitor this topic please.

For scenario 1, do you get completion status undefined consistently? This status represents the failure or success of communicating with the lock via bluetooth. Undefined means nuki was not successful...

Sorry I confused the completionStatus with the commandResult. The completionStatus is returned as a number and converted to a string in the code. Whatever number your lock returns, Nuki Hub...

I have a feeling "11" is meant to represent "failure". This is from the documentation: ``` 0x00 … Success 0x01 … Motor blocked 0x02 … Canceled 0x03 … Too recent...

I have no idea :D. Someone else has to answer that.

Not sure what happened, but I think your lock lost the pairing to the ESP. Unpairing and re-pairing should help.

@magior Any update on this? Did re-pairing help?