# Home Automation Hub — Product Meeting Notes

**Date:** July 16, 2026  
**Time:** 10:00–11:00 AM ET  
**Location:** Video conference  
**Facilitator:** Maya Chen  
**Note-taker:** Daniel Ruiz

## Attendees

- Maya Chen — Product Manager
- Daniel Ruiz — Firmware Lead
- Priya Shah — Mobile App Engineer
- Liam O’Connor — Cloud Platform Engineer
- Sofia Martinez — UX Designer
- Ethan Brooks — Security Engineer
- Nora Kim — Customer Support Lead

## Agenda

1. Review prototype feedback
2. Confirm launch scope and supported devices
3. Discuss local control and cloud dependencies
4. Review security and privacy requirements
5. Identify beta-readiness gaps

## Discussion Notes

- Prototype users liked the guided setup but had difficulty identifying devices with similar names.
- The team agreed that core automations should continue running during an internet outage.
- Initial support will focus on Matter, Thread, Wi-Fi, and selected Zigbee devices. Z-Wave support would add hardware cost and certification risk.
- Push notifications and remote access will require the cloud service; schedules, scenes, and sensor-triggered routines will run locally.
- Support reported that unclear recovery instructions are a common source of frustration with competing hubs.
- Security recommended mandatory signed firmware, encrypted local storage, automatic security updates, and optional multi-factor authentication.
- The current mobile onboarding flow takes approximately eight minutes. The beta target is five minutes for a standard setup.

## Decisions

- Launch with Matter, Thread, Wi-Fi, and Zigbee support; defer Z-Wave to a future hardware revision.
- Store automation rules locally and execute them without an internet connection.
- Require explicit user consent before collecting diagnostic logs.
- Retain diagnostic logs for 30 days by default, with an in-app option to delete them immediately.
- Add room-based naming suggestions and device-type icons to the pairing flow.
- Include a physical reset button with a ten-second hold requirement to reduce accidental resets.
- Target a closed beta of 100 households before the public release.

## Action Items

- **Daniel:** Validate offline execution for schedules, scenes, and sensor-triggered routines by July 24.
- **Priya:** Update the pairing flow with room suggestions, device icons, and duplicate-name warnings by July 28.
- **Liam:** Document cloud-dependent features and implement the 30-day diagnostic-log retention policy by July 31.
- **Sofia:** Produce revised onboarding and factory-reset recovery screens by July 23.
- **Ethan:** Complete the firmware-signing and local-storage threat-model review by July 25.
- **Nora:** Recruit 100 beta households and prepare a support FAQ covering connectivity and reset procedures by August 7.
- **Maya:** Finalize beta success metrics and circulate the launch-scope document by July 21.

## Open Questions

- Should automatic security updates permit a user-defined maintenance window?
- Which Zigbee device models will receive official compatibility certification?
- What level of functionality should remain available if the cloud account is suspended?
- Is battery backup necessary for the first hardware revision?

## Next Meeting

**Date:** July 30, 2026  
**Focus:** Beta-readiness review and security sign-off