# Home Automation Hub — Product Review

**Date:** July 30, 2026  
**Time:** 2:00–2:50 PM ET  
**Location:** Video conference

## Attendees

- Maya Chen — Product Manager
- Luis Romero — Firmware Lead
- Priya Shah — Mobile App Lead
- Evan Brooks — Cloud Platform Engineer
- Nina Patel — Security Engineer
- Jordan Kim — Customer Support Lead
- Sam Okafor — QA Lead

## Agenda

1. Review prototype stability and pilot feedback
2. Confirm supported connectivity standards
3. Decide how core automations behave during internet outages
4. Review security and privacy requirements
5. Set the pilot-release scope and timeline

## Discussion Notes

- The latest prototype completed a seven-day soak test without crashing. Two Zigbee devices failed to reconnect after a hub reboot; Luis believes the issue is related to stale device-session data.
- Pilot users found device setup straightforward but were confused by the distinction between “rooms,” “scenes,” and “automations.” Priya proposed adding short examples during onboarding.
- The team reviewed support for Matter over Wi-Fi and Thread, Zigbee, and Bluetooth Low Energy. Z-Wave would require additional certification, hardware cost, and engineering work.
- Local execution is working for schedules, sensor triggers, and basic scenes. Cloud-dependent features currently include remote access, push notifications, voice-assistant linking, and firmware downloads.
- Nina recommended encrypting hub backups before upload and requiring an explicit user confirmation before diagnostic logs are shared with support.
- QA needs a stable firmware candidate at least two weeks before the pilot begins.

## Decisions

- Version 1 will support Matter over Wi-Fi and Thread, Zigbee, and Bluetooth Low Energy.
- Z-Wave support is deferred until after the pilot; demand will be reassessed using pilot feedback and sales data.
- Schedules, sensor-triggered automations, and scenes must continue running locally when the internet connection is unavailable.
- Remote access will require multi-factor authentication during initial account setup.
- Diagnostic logs will remain on the hub unless the user explicitly authorizes an upload.
- Automatic firmware updates will be enabled by default, with a seven-day deferral option.
- The pilot will target 75 households and begin the week of September 21, subject to QA sign-off.
- Onboarding will use “scenes” for user-triggered device groups and “automations” for rule-based behavior; both terms will include examples.

## Action Items

- **Luis:** Fix Zigbee reconnection after reboot and provide a test build by August 7.
- **Priya:** Update onboarding copy and prototypes for rooms, scenes, and automations by August 10.
- **Evan:** Document offline and cloud-dependent feature behavior by August 6.
- **Nina:** Complete the backup-encryption and diagnostic-log privacy review by August 12.
- **Sam:** Finalize the pilot test plan, including outage and recovery scenarios, by August 14.
- **Jordan:** Draft the pilot support guide and escalation process by August 21.
- **Maya:** Recruit 75 pilot households and confirm device-mix requirements by August 28.
- **Maya and Luis:** Prepare a post-pilot estimate for adding Z-Wave support by October 16.

## Open Questions

- Should users be able to select a preferred maintenance window for firmware updates?
- How long should encrypted cloud backups be retained after a hub is removed from an account?
- Is cellular failover needed for a future security-focused hub model?

## Next Meeting

**Date:** August 13, 2026  
**Focus:** Firmware readiness, revised onboarding, and pilot test-plan review