Support more lock states about hass_nuki_ng HOT 9 OPEN

Thanks for the clarification.

my pleasure. I spent days building my Nuki Card, so I spent days on their forum trying to overcome issues. I understand how you feel, but unfortunately the bridge is a badly designed solution, and I discussed with them on their forum and also in video conference with product management. But I don't expect anything good coming from those conversations, they are focused on the vast majority of users....and we're not part of them with our requirements.

Please close the issue if you're ok now. :)

from hass_nuki_ng.

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.

from hass_nuki_ng.

Hi @kvj ,
my lock is called "zuhause" and this is the log of the sensor sensor.nuki_zuhause_state:

Here, I can only see the states "locked" and "unlocked".

from hass_nuki_ng.

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.

I can confirm after 1 month of usage that the state sensor only publishes locked and unlocked states, while my door is unlatched every day a few times. Both via Nuki, Homekit and even via Nuki_NG HAS.

Without Unlatch my door won't even open.

from hass_nuki_ng.

@ZzetT @Inferi0r: the unlatched state is an intermediate state, the lock is unlatched and then unlocked (final state), the callback by the bridge to HA is triggered only on final states, no intermediate states can be reflected by HA sensors because they get updated by callback of the bridge and polling.

This is the way the bridge firmware works, as described by Nuki devs in their forum:

There's a FR open that you can vote for.

Hope it's clear how this works now.

from hass_nuki_ng.

Yeah, I also have an integration relying on the unlatched state change, and it's not super-reliable.

from hass_nuki_ng.

Thanks for the clarification.

from hass_nuki_ng.

Yeah, I also have an integration relying on the unlatched state change, and it's not super-reliable.

I'm very upset about the bridge and its implementation, they didn't do a very good job. When I spoke to the product manager I told him about this...but...they look at the big numbers, and we're less than 0.5% of their average user unfortunately. 99.5% of users don't have a clue of what we're talking about...they simply use the mobile with the web interface, etc.

from hass_nuki_ng.

@kvj you can close this one.

from hass_nuki_ng.