Home Automation Hub Product Sync
Date: July 17, 2026
Time: 10:00–10:45 AM ET
Location: Zoom

Attendees
- Maya Chen — Product Manager
- Liam O’Connor — Firmware Lead
- Priya Shah — Mobile App Engineer
- Daniel Ruiz — Cloud Platform Engineer
- Erin Walker — UX Designer
- Noah Williams — QA Lead
- Sophie Martin — Customer Support

Agenda
1. Review prototype and beta feedback
2. Confirm local-versus-cloud automation behavior
3. Prioritize device integrations for launch
4. Review onboarding, privacy, and security requirements
5. Agree on beta milestones and owners

Discussion Notes
- Beta users consistently preferred automations to continue working during internet outages.
- The current prototype supports local Zigbee and Thread devices; Matter-over-Wi-Fi support remains incomplete.
- Setup abandonment is highest during device discovery, especially when users have multiple Wi-Fi networks.
- Support requested clearer diagnostics for offline devices and failed automations.
- Engineering flagged that retaining detailed event logs indefinitely would increase storage costs and privacy risk.
- QA needs stable firmware and mobile builds at least two weeks before the expanded beta.

Decisions
- Core automations will execute locally on the hub whenever device capabilities allow.
- Cloud services will be used for remote access, account synchronization, notifications, and integrations that require external APIs.
- Launch integrations will prioritize Matter, Thread, Zigbee, and Wi-Fi devices. Z-Wave support will be evaluated after launch.
- The mobile app will include a guided setup flow with network checks, device-discovery progress, and plain-language recovery steps.
- Detailed event logs will be retained for 30 days by default. Users may disable diagnostic log uploads.
- Remote access will require multi-factor authentication for account owners.
- The expanded beta remains targeted for September 14, subject to completion of the security review and reliability testing.

Action Items
- Liam: Deliver a firmware build with local automation failover and recovery metrics by August 7.
- Priya: Add network validation and device-discovery status to the mobile onboarding flow by August 12.
- Daniel: Document cloud dependencies and implement the 30-day event-log retention policy by August 14.
- Erin: Provide revised onboarding and offline-device error-state designs by July 28.
- Noah: Publish the expanded beta test plan, including outage, reboot, and migration scenarios, by August 5.
- Sophie: Categorize the top 20 beta support issues and propose help-center updates by July 29.
- Maya: Schedule the security review and confirm September beta participants by August 3.

Open Questions
- Whether Z-Wave support should be delivered through a USB accessory or a future hub revision.
- Whether household members should have separate permissions for locks, cameras, and security automations.
- Minimum supported bandwidth for reliable remote camera previews.

Next Meeting
July 31, 2026, at 10:00 AM ET — firmware readiness and onboarding review.