# Home Automation Hub — Product & Engineering Sync

**Date:** July 31, 2026  
**Time:** 10:00–10:45 AM ET  
**Location:** Video conference

## Attendees

- Maya Chen — Product Manager
- Daniel Ortiz — Hardware Lead
- Priya Nair — Firmware Engineer
- Lucas Martin — Mobile App Lead
- Erin Walsh — Security Engineer
- Sam Becker — Customer Support
- Jordan Kim — QA Engineer

## Agenda

1. Review prototype stability and connectivity
2. Confirm supported protocols for launch
3. Discuss local control, cloud services, and privacy
4. Review mobile onboarding flow
5. Set beta milestones and owners

## Notes

- The latest prototype remained online throughout the five-day soak test. Two Zigbee devices required re-pairing after a simulated power outage.
- Wi-Fi, Zigbee, and Matter-over-Thread are working in the current build. Z-Wave certification would add approximately eight weeks and require a hardware revision.
- The team agreed that core automations must continue to run without internet access. Remote access, voice-assistant integrations, and firmware downloads will require cloud connectivity.
- Device credentials and automation data will be encrypted at rest. Diagnostic logs will be opt-in and retained for 30 days.
- Mobile onboarding currently averages seven minutes. Most test users hesitated when asked to create a “home” before adding their first device.
- Support requested clearer status indicators for offline devices and a user-accessible network diagnostic report.
- The private beta is tentatively planned for September 14, with 50 households participating for four weeks.

## Decisions

- Launch support will include Wi-Fi, Zigbee, and Matter-over-Thread.
- Z-Wave support is deferred to a future hardware revision.
- Automations, schedules, and manual device controls will operate locally by default.
- Cloud diagnostic logging will be disabled by default and enabled only with explicit consent.
- The onboarding flow will add the first device before prompting users to name their home.
- The hub will retain the most recent firmware image to support automatic rollback after failed updates.
- Private beta entry criteria: 99.5% hub uptime, successful recovery after power loss, and no unresolved critical security issues.

## Action Items

- **Priya:** Investigate Zigbee re-pairing after power loss and propose a fix by August 7.
- **Daniel:** Confirm final radio-module bill of materials and certification schedule by August 5.
- **Lucas:** Update the onboarding prototype and offline-device status screens by August 12.
- **Erin:** Complete the threat-model review and document log-retention controls by August 10.
- **Jordan:** Add power-loss recovery, firmware rollback, and local-only operation to the beta test plan by August 14.
- **Sam:** Draft customer-facing troubleshooting steps for connectivity issues by August 14.
- **Maya:** Recruit 50 beta households and publish the beta success criteria by August 21.

## Open Questions

- Should users be able to export automation configurations before launch?
- What is the maximum supported device count under sustained local automation load?
- Which voice-assistant integrations are required for the public release?

## Next Meeting

**Date:** August 14, 2026  
**Focus:** Beta readiness, security review findings, and onboarding changes