api: fix response generation with new "is_main_lock" field
All checks were successful
Build Container / Build Container (push) Successful in 4m25s
All checks were successful
Build Container / Build Container (push) Successful in 4m25s
This commit is contained in:
parent
ecd6c2c48f
commit
51c67c49ae
2 changed files with 7 additions and 1 deletions
|
|
@ -54,7 +54,6 @@ class LockStatus(BaseModel):
|
|||
is_unreachable: bool
|
||||
is_low_battery: bool
|
||||
is_error_jammed: bool
|
||||
is_main_lock: bool
|
||||
lock_target_level: Literal["locked", "unlocked", "open"]
|
||||
lock_state: Literal["unknown", "locked", "unlocked"]
|
||||
activity_state: Literal["unknown", "locking", "unlocking", "stable"]
|
||||
|
|
@ -63,6 +62,7 @@ class LockStatus(BaseModel):
|
|||
class Lock(BaseModel):
|
||||
name: str
|
||||
id: str
|
||||
is_main_lock: bool
|
||||
status: LockStatus
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue