FastyBird Smart Panel: HomeKit feature, serial repair, October 3 owner acceptance
FastyBird Smart Panel: HomeKit feature, serial repair, October 3 owner acceptance
Question. Can one inspect an agent-era feature from implementation through human test, changing plan, related PRs, real device behavior and owner sign-off? A good answer distinguishes an owner-accepted resolution of a visible defect from proof of all originally planned timing/client cases and from independent customer value. See feature-trace brief and feature to outcome.
Initial feature, September 5–7. Adam Kadlec's Studio81 firsthand account says Gemini implemented the HomeKit gateway, Codex reviewed, and people tested UI, simulator and real Apple Home before a live installation. Public PR #970 merged September 5 with 29 commits and automated checks/review. Agent session attribution, human hours and customer outcome are not public.
The human-found defect and decision. On September 8 an Apple Home manual test and issue #1006 found a lamp briefly switching new→old→new. In five taps, the previous command's report entered the store 1.2 seconds after the next was accepted. The issue compares backend command-window reconciliation with client-only settling and source timestamp watermarks, choosing the backend to cover Apple Home, admin, panel and third-party API paths. Its owner changed the originally suggested parallel implementation to serial, maximum one worker because the hot write path overlapped. An issue orchestrated work, a separate issue held acceptance, and linked PRs carried repairs; September 9 cache hardening #1047 was expressly not the original observed trigger. September 27 PR #1120 repaired more value-path behavior and published partial staging measurements, not the full planned matrix.
Important October 3 update, checked October 5. Hardware ledger #1032 and the epic now say closed with owner acceptance October 3, 2026, superseding our October 2–3 notes that they were open. After an ordinary alpha.40→alpha.41 system upgrade on an unchanged 111-device topology, the ledger reports 80 successful commands/restores. Alpha.41 backend preparation median/p95/max was 41.2/99.3/152.8 ms in idle and 189.8/326.7/341.6 ms under catalog load; device/network delay remains a separate interval. A further 20-command instrumented diagnostic was successful but not a normal-runtime before/after estimate. In a final short Apple Home screen, six alternating actions reached their expected post-action states; final Apple Home and independent Shelly readback were OFF. The owner explicitly confirmed visually that ordinary Apple Home switching works and the original brief flip back does not occur. The display recording was obscured and cannot independently rule out transient flicker.
What closure means—and does not. The owner consciously accepted that evidence and stopped the broader historical poll-placement and Apple Home/admin/panel matrix; unperformed cases were not marked passed. Conditional admin/panel changes #1012/#1013 were closed as not planned, historical failure #1052 remains documented, and separate CI 100-run issues #1040/#1045 remain open. This is same-request owner-observed visual acceptance with narrowed scope, not a blind hardware test of all original cases, a 30-day repair result, or external customer confirmation. Neither the active human planning/review/testing time nor model cost is given. It is stronger than feature→merge: a documented revision of what qualified for completion. Compare the four-artifact chain and Anghami's operator ledger.