RoomFlow v0.0.60

The v0.0.56 fix skips re-applying motion-on when a device already reads
"on" with nothing pending. But _turn_off_device's light.turn_off call to
a Plejd entity is a fire-and-forget mesh write - the entity's reported
state only updates once (if ever) the mesh confirms it - so
hass.states.get(...).state could keep reading "on" well after
RoomFlow's own motion-off timer had already fired and sent the real off
command. Reported live: Toa's ceiling light stopped responding to fresh
motion after its own timeout ran.

Tracks RoomFlow's own turn-off intent directly now
(hass.data[DOMAIN]["motion_expected_off"], set in _turn_off_device,
cleared in _apply_motion_device_on) instead of trusting that
potentially-stale read for the skip decision, in both motion-on code
paths in _handle_motion_change. A device RoomFlow hasn't itself just
turned off still gets the original optimization (no flicker); one it
has is never mistaken for "already fine, nothing to do".

---

Installation

HACS: Integrations → ⋮ → Custom repositories → add this repo as an Integration → search RoomFlow → install → restart Home Assistant.
Manual: download roomflow.zip below and extract it to your custom_components/ folder.

Full Changelog: v0.0.59...v0.0.60