# Home Automation Hub — Product & Engineering Sync

**Date:** July 30, 2026  
**Time:** 10:00–10:45 AM ET  
**Location:** Video conference  
**Facilitator:** Maya Chen  
**Note-taker:** Luis Romero

## Attendees

- Maya Chen — Product Manager
- Luis Romero — Firmware Lead
- Priya Shah — Mobile Engineering
- Owen Brooks — Cloud Platform
- Hannah Kim — UX Design
- Jordan Bell — QA
- Samira Patel — Security
- Eli Foster — Customer Support

## Agenda

1. Review prototype and reliability testing
2. Confirm launch protocol support
3. Discuss local-control behavior during internet outages
4. Review onboarding and device-pairing flow
5. Identify security and privacy requirements
6. Confirm beta scope and owners

## Discussion Notes

- The latest prototype remained online throughout the seven-day soak test. Two Zigbee devices failed to reconnect after a simulated power outage; both recovered after the hub was restarted.
- Matter-over-Wi-Fi pairing is working on iOS. Android pairing still requires users to enter the setup code manually when QR scanning fails.
- The team agreed that common automations—including schedules, motion-triggered lighting, and door-sensor alerts—must run locally without an internet connection.
- Cloud access will remain necessary for remote control, push notifications, account management, and firmware downloads.
- UX testing showed that users were uncertain whether devices were pairing with the hub or directly with their phone. The onboarding copy and progress indicators need revision.
- Support requested a downloadable diagnostics bundle containing timestamps, radio status, firmware versions, and recent non-sensitive errors.
- Security recommended encrypting diagnostics bundles and automatically deleting them from cloud storage after seven days.
- The beta will prioritize lighting, plugs, locks, motion sensors, and contact sensors. Cameras and energy-monitoring devices are out of scope for the first beta.

## Decisions

- Version 1 will support Matter, Thread, Zigbee 3.0, Wi-Fi, and Bluetooth Low Energy for commissioning.
- Z-Wave will not be included at launch; the team will reassess demand after the beta.
- Core automations will execute locally and continue during internet outages.
- Remote access will be opt-in and protected by multi-factor authentication.
- The hub will retain a rolling seven-day local event log by default.
- Diagnostics bundles will exclude automation names, device names, video, audio, and raw lock-access history.
- The closed beta target is September 21, 2026, with approximately 75 households.
- Camera support is deferred until after the initial public release.

## Action Items

- **Luis:** Investigate Zigbee reconnection failures and propose a fix by August 5.
- **Priya:** Improve Android QR fallback and add clearer manual-entry guidance by August 7.
- **Hannah:** Revise onboarding copy and pairing-status screens; share designs by August 6.
- **Owen:** Document offline versus cloud-dependent features by August 4.
- **Samira:** Define diagnostics encryption, redaction, and deletion requirements by August 5.
- **Jordan:** Expand outage testing to include router replacement, DNS failure, and 24-hour internet loss by August 10.
- **Eli:** Draft beta support documentation and escalation criteria by August 14.
- **Maya:** Finalize beta household selection criteria and recruitment plan by August 7.

## Open Questions

- Should lock PIN management be available locally when the cloud service is unavailable?
- What is the minimum supported Android version for Matter commissioning?
- Can the hub expose local backups without increasing privacy or support risks?
- Which device brands should be represented in the beta test matrix?

## Next Meeting

**Date:** August 6, 2026  
**Focus:** Zigbee reconnection findings, revised onboarding flow, and beta-readiness risks