# Home Automation Hub — Product & Engineering Sync

**Date:** July 30, 2026  
**Time:** 10:00–10:45 a.m. ET  
**Location:** Zoom

## Attendees

- Maya Chen — Product Manager
- Lucas Pereira — Hardware Lead
- Priya Shah — Firmware Engineer
- Jordan Lee — Mobile App Engineer
- Elena Rossi — UX Designer
- Sam Okafor — Security Engineer
- Nina Patel — Customer Support Lead

## Agenda

1. Review prototype stability and pilot feedback
2. Confirm supported protocols for launch
3. Decide on local versus cloud processing behavior
4. Review onboarding and account requirements
5. Set milestones for the beta release

## Notes

- The latest prototype completed a seven-day soak test with two unexpected restarts. Priya traced both to memory growth in the Zigbee device-discovery service.
- Pilot users liked the unified device dashboard but struggled to identify devices with generic manufacturer names.
- Support for Matter over Wi-Fi and Thread is working in the lab. Zigbee is stable apart from the discovery issue. Z-Wave certification would add approximately eight weeks to the schedule.
- The team agreed that core automations must continue during an internet outage. Remote access, voice-assistant integrations, and notifications will still require cloud connectivity.
- Sam recommended encrypting automation rules and credentials at rest, with device keys stored in the secure element.
- Users currently must create an account before setup. Elena’s testing showed this caused several participants to abandon onboarding.
- The mobile app needs clearer explanations when requesting local-network, Bluetooth, and notification permissions.

## Decisions

- Launch with Matter, Thread, Wi-Fi, and Zigbee support. Z-Wave will be evaluated for a later hardware revision.
- Run schedules, sensor-triggered routines, and device-to-device automations locally on the hub.
- Allow local setup without an account; require sign-in only for remote access, backups, and third-party cloud integrations.
- Add user-editable device names during discovery and suggest names based on room and device type.
- Target a closed beta on September 21, 2026, contingent on completing security review and reducing unexpected restarts to zero during a 14-day soak test.
- Retain automation event logs locally for 30 days by default, with an option to disable logging.

## Action Items

- **Priya:** Fix the Zigbee discovery memory leak and provide a new firmware build by August 7.
- **Lucas:** Start the 14-day hardware and firmware soak test by August 10.
- **Jordan:** Implement account-optional onboarding and revised permission prompts by August 21.
- **Elena:** Deliver updated onboarding screens and device-naming flows by August 12.
- **Sam:** Complete the threat model and secure-storage review by August 14.
- **Maya:** Update the launch requirements and beta readiness checklist by August 3.
- **Nina:** Recruit 25 closed-beta households representing mixed device ecosystems by September 4.
- **Maya and Lucas:** Prepare a recommendation on future Z-Wave support for the next roadmap review.

## Open Questions

- Should local backups be supported through USB storage at launch?
- What is the maximum number of active automations the launch hardware can support without noticeable latency?
- Which voice-assistant integrations will be ready for the closed beta?

## Next Meeting

**Date:** August 13, 2026  
**Focus:** Firmware stability, onboarding progress, and security-review findings