# Home Automation Hub — Product & Engineering Sync

**Date:** August 1, 2026  
**Time:** 10:00–10:45 AM ET  
**Location:** Zoom  
**Facilitator:** Maya Chen  
**Note-taker:** Liam Patel  

## Attendees

- Maya Chen — Product Manager
- Liam Patel — Firmware Engineer
- Sofia Alvarez — Mobile Lead
- Jordan Brooks — Cloud Platform Engineer
- Priya Nair — Security Engineer
- Ethan Walsh — QA Lead
- Nina Park — Customer Support Lead

## Agenda

1. Review prototype stability and pilot feedback
2. Confirm connectivity and local-control scope
3. Decide security and software-update requirements
4. Set pilot milestones and ownership

## Discussion Notes

- The latest prototype completed a seven-day soak test. Two hubs required manual restarts after repeated Wi-Fi disconnects.
- Pilot users value local automations because routines continue during internet outages.
- Matter-over-Wi-Fi and Thread support remain on schedule. Zigbee support would require additional certification work and could delay the pilot.
- Mobile onboarding takes approximately six minutes. Most failures occur during Wi-Fi credential transfer.
- Support requested clearer LED states and in-app recovery instructions.
- Security review identified certificate rotation, encrypted backups, and signed firmware as launch requirements.
- Cloud costs are within target, but verbose device telemetry should be disabled by default.

## Decisions

- The pilot release will support Matter-over-Wi-Fi and Thread. Zigbee support is deferred until after the pilot.
- Core routines, schedules, and manual device controls must work without an internet connection.
- Remote access and push notifications will require the cloud service.
- Firmware updates must be signed, support automatic rollback, and install during a configurable maintenance window.
- Diagnostic telemetry will be opt-in and retained for no more than 30 days.
- The mobile app will include guided recovery for Wi-Fi changes and failed device pairing.
- Pilot readiness requires a 14-day soak test with no unrecovered hub failures.

## Action Items

- **Liam:** Investigate the Wi-Fi reconnect failure and deliver a firmware fix by August 7.
- **Sofia:** Prototype the revised onboarding and recovery flow by August 10.
- **Jordan:** Add telemetry retention controls and document cloud dependencies by August 12.
- **Priya:** Complete the firmware-signing and certificate-rotation threat review by August 14.
- **Ethan:** Define the 14-day soak-test plan and pilot exit criteria by August 6.
- **Nina:** Draft LED-state and troubleshooting copy based on support feedback by August 9.
- **Maya:** Update the pilot scope and communicate the Zigbee deferral to stakeholders by August 5.

## Open Questions

- Should local backups be encrypted with a user-managed recovery key or a hub-generated key?
- What minimum set of third-party devices must pass interoperability testing before the pilot?
- Can remote-access latency remain below two seconds during peak usage?

## Next Meeting

**Date:** August 15, 2026  
**Focus:** Soak-test results, onboarding prototype review, and pilot go/no-go assessment.