#Lock states
1 messages · Page 1 of 1 (latest)
Ooh
I think enum sensor? And I guess map that semi locked state to what it is at the moment in real life
Problem is I don’t know what it is
Tedee?
Could be you turned a bit from unlocked and it’s still unlocked or a bit from locked and it’s still locked, or a bit more from unlocked and it’s physically locked but not quite far enough
Yes
Lol, then it'd be unknown I guess
Like this sounds you dont know either
But what states are there then?
class TedeeLockState(IntEnum):
"""Tedee Lock State."""
UNCALIBRATED = 0
CALIBRATING = 1
UNLOCKED = 2
HALF_OPEN = 3
UNLOCKING = 4
LOCKING = 5
LOCKED = 6
PULLED = 7
PULLING = 8
UNKNOWN = 9
UPDATING = 18
UNPULLING = 255
Is it half open?
Yes
I dont know how to model that nicely either
Like I think the lock is correct in being an unknown state because we dont know if its locked or not
But you likely want to defferentiate between unknown and half open
Exactly
I'm not sure if you can describe it in a binary sensor or so
https://github.com/home-assistant/core/pull/168750/changes switchbot seems to have a "half lock" state as well. If it's not only tedee, does it make sense to maybe extend the lock entity model?