search

kvj / hass_nuki_ng

Better support for Nuki devices in the Home Assistant
MIT License
176 stars 33 forks source link

Lock 'n' Go State #75

Open garv3 opened 2 years ago

garv3 commented 2 years ago

The state "Lock 'n' Go" is not reflected by the entities. This is an important state to have for security automation!

For example the alarm system should be armed when the door has been locked by the Lock 'n' Go feature but not if the lock is being locked because of another automation like night mode. So it is important to know when the Lock 'n' Go feature is being used.

Should be easy to implement this because the states.py already defines the state. It has simply not been added to an entity. Why is this?

garv3 commented 2 years ago

Ok, so this project is dead?

kvj commented 2 years ago

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?

pichljan commented 1 year ago

+1 for this feature

kvj commented 1 year ago

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 chances that bridge won't report it are very high, because there's no guarantee that each state transition will be reported

pichljan commented 1 year ago

I see your point. However, my idea for this feature is kind of an extension of the "Last unlock user" entity. Let's say it would be called "Last action" and the attributes would be User (Name, Manual, Button) and Action type (Lock, Unlock, Auto Unlock, Lock n Go, Open door). All these values are reported in the Activity log using the Web interface so I believe they can be used in the integration. I did not check the documentation yet, though.

purche42 commented 1 year ago

+1 for last action (Lock, Unlock, Auto Unlock, Lock n Go, Open door). This would be great to have this info for automation. e.g. turn on light at entrance after Auto-Unlock.