v0.7.7 — the lock shows what it is doing

The lock entity now reports locking and unlocking while a command is in flight, instead of sitting on its old state until the command finishes. Contributed by @djbn65.

How long the in-progress state lasts

Please read this before reporting a stall. The state covers the whole command, so how long it shows depends on your hardware:

• Hub-attached lock — roughly one senddata round trip.
• Hubless WiFi-native lock — noticeably longer, because a command there spans two transports: senddata is refused with cod=930, as it always is on these locks, and only then does the command go over the broker.

So a Visage or a PGD728FG25 will show unlocking for longer than a hub lock does, and that is the entity reporting honestly how long the command actually takes rather than anything being stuck.

It also clears if the command fails, rather than leaving the entity in-progress until Home Assistant restarts — verified on both paths.

Unchanged

No frame, transport or state-parsing changes. Everything from 0.7.6 behaves identically.