# Home Automation Hub — Product & Engineering Sync

**Date:** July 16, 2026  
**Time:** 10:00–10:45 a.m. ET  
**Location:** Video conference

## Attendees

- Maya Chen — Product Manager
- Daniel Ortiz — Hardware Lead
- Priya Nair — Firmware Engineer
- Sam Becker — Mobile App Lead
- Lena Hoffmann — Security Engineer
- Jordan Lee — Customer Support
- Alex Morgan — QA Engineer

## Agenda

1. Review hub hardware and firmware status
2. Confirm supported protocols and offline behavior
3. Discuss onboarding and device-management experience
4. Review security and privacy requirements
5. Agree on beta scope, timeline, and owners

## Discussion Notes

- The latest hardware revision passed thermal testing under a sustained load of 75 connected devices. Daniel noted intermittent USB-C power negotiation failures with two third-party adapters; the retail package will include a certified adapter.
- Matter-over-Wi-Fi, Thread, Zigbee, and Bluetooth LE are working in the current prototype. Z-Wave support would require an additional radio module and certification work.
- Core automations—including schedules, sensor triggers, and local scenes—continue running during an internet outage. Remote access, voice-assistant commands, and cloud notifications require connectivity.
- The team reviewed onboarding feedback from 14 internal testers. Most completed setup in under five minutes, but several did not understand when the app switched from Bluetooth provisioning to Wi-Fi.
- Device names and room assignments currently sync through the cloud. Priya proposed storing the latest configuration locally so the hub remains fully navigable when cloud services are unavailable.
- Lena recommended enabling automatic security updates by default, with a limited deferral option. The group agreed that indefinite update postponement would create unnecessary support and security risk.
- Customer Support requested clearer diagnostic messages for unreachable devices and Thread border-router issues. Current errors are too generic for first-line troubleshooting.

## Decisions

- Version 1 will support Matter-over-Wi-Fi, Thread, Zigbee, and Bluetooth LE.
- Z-Wave support is deferred until after launch; the enclosure will retain space for a possible future radio module.
- Automations, schedules, room data, and device names must remain available locally during internet outages.
- Automatic firmware updates will be enabled by default. Users may defer an update for up to seven days.
- The mobile app will display a clear setup-stage indicator for Bluetooth discovery, Wi-Fi connection, and account registration.
- The beta target is 50 households, with priority given to homes using at least two supported protocols.
- Beta entry criteria include 72 hours of stable operation, successful recovery after power loss, and no open critical security findings.

## Action Items

- **Daniel:** Validate the certified power adapter with the next 20 hardware units by **July 23**.
- **Priya:** Implement local caching for device names and room assignments by **July 30**.
- **Sam:** Add onboarding stage indicators and revised Wi-Fi error messages by **July 28**.
- **Lena:** Complete the firmware update threat model and define the seven-day deferral behavior by **July 24**.
- **Alex:** Expand outage, power-loss recovery, and mixed-protocol test coverage by **August 3**.
- **Jordan:** Draft support troubleshooting flows for unreachable devices and Thread connectivity by **July 31**.
- **Maya:** Finalize beta participant criteria and circulate the recruitment brief by **July 22**.

## Open Questions

- Should local backups be exportable to a user-owned USB drive?
- Can Z-Wave be added through an external accessory without requiring a new hub certification?
- What retention period should apply to cloud diagnostic logs?
- Should advanced users be allowed to opt out of automatic updates after the initial warranty period?

## Next Meeting

**July 30, 2026, 10:00 a.m. ET** — Beta readiness review and go/no-go assessment.