test(backend): validate property command convergence and Raspberry Pi latency
test(backend): validate property command convergence and Raspberry Pi latency
After a September 8 Apple Home test caught a lamp changing new→old→new, the maintainer investigated delayed device read-backs, ordered overlapping backend repairs serially and kept a separate hardware acceptance ledger. The September 27 staging checks had been explicitly insufficient; an ordinary alpha.40-to-alpha.41 system upgrade on the same 111-device setup later led to a recorded set of 80 successful commands and restores. The final short Apple Home check reached the expected states across six actions, with the lamp OFF in both Apple Home and an independent Shelly readback. The owner said ordinary switching now worked and the original visible flip back was gone, and closed the acceptance issue and epic on October 3.
That was a scoped human decision, not completion of the original test plan. The owner stopped further profiling and retired the broader poll-placement and Apple Home/admin/panel matrix as unperformed, not passed. The screen recording was obstructed and cannot rule out every transient flicker; independent CI-stability work remains open. This is unusually clear same-request owner acceptance of a real-device repair, but provides no external customer's follow-up, month-later reliability, active human hours or model spend. The issue is a long historical ledger; this summary conveys the change without requiring a weekday read of it.