diff --git a/.claude/plans/home-automation-platform-analysis.md b/.claude/plans/home-automation-platform-analysis.md index 9631944..0a81e4b 100644 --- a/.claude/plans/home-automation-platform-analysis.md +++ b/.claude/plans/home-automation-platform-analysis.md @@ -1,94 +1,297 @@ # Home Automation Platform Analysis +**Last Updated:** January 2026 +**Status:** Ready for implementation + ## Current Setup Analysis -- **Strengths:** Matter compliance, local Apple TV hub, established device ecosystem (10+ sensors, bulbs, Hue bridge) -- **Limitations:** Automation complexity ceiling, no external integrations, limited scheduling options -- **Infrastructure:** Proxmox host, Docker/Podman capability, network-local preference + +- **Device Count:** 20+ sensors and bulbs, Philips Hue Bridge +- **Strengths:** Matter compliance, local Apple TV hub, established device ecosystem +- **Limitations:** Automation complexity ceiling, no external integrations, limited scheduling options, no API access for custom integrations +- **Infrastructure:** Proxmox host with GPU passthrough, Docker/Podman capability, strong preference for local-only operation ## Platform Comparison ### 1. Home Assistant (Recommended) + **Pros:** - Exceptional automation engine with complex logic, scheduling, and templating -- Best-in-class local operation (no cloud required) +- Best-in-class local operation (100% local, tested to work through week-long internet outages) - Massive device integration library (2000+ integrations) -- Matter support has matured significantly since 2024 +- **Matter support now mature** - HA 2026.1 elevated Matter/Thread to primary Settings menu - Strong community and documentation - Supports both container and OS deployment +- Native Philips Hue integration provides MORE features than Matter bridging +- New Philips Hue BLE integration (2025.12) can control Hue lights without bridge +- Connect ZBT-2 USB adapter provides Zigbee + Thread + Matter in single device **Cons:** -- Initial setup learning curve (but much improved) -- Device re-pairing required +- Initial setup learning curve (but much improved with 2025-2026 UX updates) +- Device re-pairing required for full migration - Ongoing configuration maintenance +**Matter/Thread Status (January 2026):** +- Thread 1.4 now required for new border router certifications (as of Jan 1, 2026) +- Compatible Thread border routers: HomePod Mini/V2, Apple TV 4K, Nest Hub 2nd Gen, HA with OpenThread add-on +- Three new diagnostic binary sensors for thermostat remote sensing in 2026.1 +- Thread radio available on HA Yellow, Connect ZBT-1, and Connect ZBT-2 + **Best For:** Users wanting maximum automation flexibility and local control -### 2. Node-RED + Apple Home (Hybrid) +--- + +### 2. Hubitat Elevation C-8 Pro (Strong Alternative) + +**Pros:** +- 100% local processing with optional cloud features +- Built-in Z-Wave 800 + Zigbee 3.0 + Matter support out of box +- No additional hardware or software setup required +- Under $120 price point +- Strong performance during internet outages +- Good for users who want stability over tinkering + +**Cons:** +- Smaller integration library than Home Assistant +- Can feel sluggish with multiple simultaneous automations +- Steeper learning curve than mainstream hubs +- Less active community than Home Assistant +- Fewer advanced features and customization options + +**Best For:** Users wanting reliable local control without extensive tinkering + +--- + +### 3. Node-RED + Apple Home (Hybrid) - **NOT RECOMMENDED** + **Pros:** - Keep existing device pairings intact - Visual flow-based automation programming -- Can integrate with Apple Home via HomeKit Controller -- Good for complex orchestrations +- Can create virtual accessories visible in Apple Home +- Good for complex orchestrations with external services - Local operation possible **Cons:** -- Limited by Apple Home's device exposure limitations -- Requires running alongside Apple Home ecosystem -- Less device integration options than HA +- **CRITICAL LIMITATION:** Can only CREATE accessories in HomeKit, CANNOT READ data from existing HomeKit devices +- HomeKit's secure architecture prevents external access to device states +- Limited to controlling Node-RED-created virtual accessories +- Requires maintaining parallel systems - May hit Apple Home API rate limits on complex automations +- Active development but fundamental HomeKit limitation cannot be worked around -**Best For:** Users wanting advanced automations without disrupting existing setup +**Why Not Recommended:** The inability to read existing HomeKit device states makes this unsuitable for your use case. You cannot build automations that respond to your existing 20+ sensors/bulbs - only create new virtual devices. + +**Best For:** Adding non-HomeKit devices TO Apple Home, not automating existing HomeKit devices + +--- + +### 4. Home Assistant + Apple Home Bridge (Best of Both Worlds) -### 3. Home Assistant + Apple Home Bridge (Best of Both) **Pros:** - Keep Apple Home interface for family while gaining HA automation power -- All devices managed in HA, exposed to Apple Home selectively -- Maximum automation capabilities + familiar interface +- All devices managed in HA, exposed to Apple Home selectively via HomeKit Controller +- Maximum automation capabilities + familiar Siri/Apple interface - Local operation maintained +- Family members continue using iPhones/iPads naturally **Cons:** - Most complex initial setup -- Device re-pairing required -- Two systems to maintain +- Device re-pairing required (to HA) +- Two systems to understand (though family only sees Apple Home) + +**Best For:** Households where some members prefer Apple's interface but you want advanced automations + +--- + +### 5. Other Platforms Considered + +| Platform | Local Control | Matter | Pros | Cons | +|----------|--------------|--------|------|------| +| **Samsung SmartThings** | Hybrid | Yes (1.5 first!) | Easy setup, first Matter 1.5 support | Cloud-dependent, lost Z-Wave support | +| **Aqara Hub M3** | Hybrid | Yes (bridge) | Multi-protocol (Zigbee+Thread+Matter), PoE | Only controls Aqara Zigbee devices | +| **IKEA Dirigera** | Partial | Yes (bridge) | Budget-friendly, now Thread border router | Limited to simple automations | +| **Amazon Echo/Alexa** | Minimal | Yes | Voice-first, wide compatibility | Heavy cloud dependency | +| **Google Home** | Minimal | Yes | Good voice, Nest ecosystem | Heavy cloud dependency | + +--- ## Architecture Recommendations -### Option A: Full Home Assistant Migration -1. Deploy HA in Proxmox container/VM -2. Re-pair all devices to HA directly -3. Build automations in HA -4. Use HA mobile app + dashboards +### Option A: Full Home Assistant Migration (RECOMMENDED) + +1. Decommission old unmaintained HA VM +2. Deploy HAOS VM using community helper script (4 cores, 8GB, 64GB) +3. Re-pair all devices directly to HA +4. Build automations in HA's automation engine +5. Use HA mobile app + custom dashboards +6. Optional: Add Connect ZBT-2 for unified Zigbee/Thread/Matter + +**Why Recommended:** +- Add-on marketplace provides one-click MQTT, Node-RED, etc. +- Device re-pairing is acceptable +- Local-only operation is priority +- Maximum automation flexibility +- HAOS VM is officially supported with full Supervisor +- Philips Hue native integration provides full feature access ### Option B: HA + HomeKit Bridge Hybrid -1. Deploy HA in Proxmox container/VM -2. Re-pair devices to HA -3. Use HomeKit Controller integration to expose selected devices/automations back to Apple Home -4. Family continues using Apple Home interface, you get HA automation power -### Option C: Node-RED Overlay (Conservative) -1. Deploy Node-RED in container -2. Keep all devices paired to Apple Home -3. Use Node-RED HomeKit Controller to read Apple Home state -4. Build complex automations in Node-RED -5. Control devices through Apple Home APIs +1. Deploy HAOS VM in Proxmox +2. Re-pair all devices to HA +3. Use HomeKit Controller integration to expose selected devices back to Apple Home +4. Family continues using Apple Home/Siri interface +5. You get full HA automation power + +**When to Choose:** If Staci or other household members strongly prefer the Apple Home interface + +### ~~Option C: Node-RED Overlay~~ (REMOVED) + +Previously listed as a conservative option, but research confirms this is not viable due to HomeKit's fundamental limitation of not exposing device data to external systems. Node-RED can only create virtual accessories, not read from existing ones. + +--- + +## Philips Hue Integration Strategy + +### Recommended: Keep Hue Bridge + Native HA Integration + +**Why Native Integration > Matter Bridging:** +- Matter only provides basic on/off/brightness controls +- Native integration includes: + - Dynamic scenes + - Entertainment mode / Sync Box support + - Gradient light controls + - Motion sensor temperature readings + - Full color/color temperature control + - Power-on behavior settings + +**Integration Method:** +- HA auto-discovers Hue Bridge on network +- Link via button press (same as Apple Home pairing) +- All Hue features immediately available +- Runs 100% locally between HA and Hue Bridge + +### Future Option: Hue Bridge Pro Migration + +If you upgrade to Hue Bridge Pro later: +- Supports up to 150 lights and 50 accessories (vs 50 lights on current bridge) +- Faster processing (1.7 GHz quad-core, 8GB for 500 scenes) +- Migration assistant transfers all devices automatically +- Multi-bridge consolidation now supported (Hue app 5.57+) + +### Alternative: Direct Zigbee Control + +Skip Hue Bridge entirely by adding Zigbee coordinator to HA: +- **Pros:** One less device, unified management +- **Cons:** Lose Hue-specific features, entertainment mode, OTA updates +- **Recommendation:** Keep bridge initially, evaluate later + +--- + +## Matter 1.5 Update (November 2025) + +New device categories now supported: +- **Cameras** - First video device support in Matter +- **Energy Management** - Smart panels, EV chargers, solar +- **Smart Closures** - Motorized shades, awnings +- **Garden Sensors** - Soil moisture, outdoor weather + +Platform rollout: +- Samsung SmartThings: December 2025 (first) +- Apple Home, Google Home, Alexa: Q1 2026 +- Home Assistant: Follows shortly after official spec release + +--- ## Technical Considerations -### Deployment Method: Podman Container (Recommended) -- More flexible than Home Assistant OS -- Easier backup/restore -- Better resource control in Proxmox -- GPU passthrough compatibility you already have +### Deployment Method: HAOS VM (Recommended) -### Matter Device Strategy -- Modern Home Assistant has excellent Matter support -- Re-pairing is straightforward with Matter devices -- Thread network can be shared between platforms +Full Home Assistant OS in a Proxmox VM: +- **Add-on Marketplace** - One-click install of MQTT, Node-RED, Zigbee2MQTT, etc. +- **Supervisor included** - Automated updates, backups, health monitoring +- **USB passthrough** - Reliable support for Zigbee/Thread coordinators +- **Official support** - Fully supported installation method +- **Community helper script** - One-command deployment via community-scripts -## Next Steps Recommendation -Start with **Option A (Full HA Migration)** because: -1. Your technical comfort level makes setup manageable -2. Device re-pairing is acceptable to you -3. Local-only operation is priority -4. You want maximum automation flexibility -5. Container deployment aligns with your infrastructure \ No newline at end of file +**VM Specs:** 4 cores, 8GB RAM, 64GB disk + +### Thread Network Strategy + +- Apple TV 4K and HomePod Mini can serve as Thread border routers during migration +- HA can become Thread border router with Connect ZBT-2 or OpenThread add-on +- Thread networks can be shared between platforms during parallel operation +- Thread 1.4 compliance now required for new border routers + +### Hardware Requirements + +**Minimum:** +- 2 CPU cores +- 2GB RAM +- 20GB storage +- Gigabit network recommended + +**Your Proxmox Environment:** +- Should handle HA easily alongside existing containers +- Consider dedicating 4GB RAM for larger integrations +- Network mode: host recommended for device discovery + +--- + +## Migration Risk Assessment + +| Risk | Likelihood | Impact | Mitigation | +|------|-----------|--------|------------| +| Device re-pairing issues | Medium | Medium | Phase migration, keep Apple Home parallel | +| Family adoption resistance | Low | High | Use HomeKit bridge, maintain Siri access | +| Automation complexity | Low | Low | Your technical background handles this | +| Thread network conflicts | Low | Medium | Use Apple devices as border routers initially | +| Hue feature loss | Low | Low | Use native integration, not Matter | + +--- + +## Next Steps + +### Phase 1: Foundation +1. Create LXC or VM in Proxmox for HA container +2. Deploy Home Assistant container with Podman +3. Connect to existing Hue Bridge (native integration) +4. Test with 2-3 non-critical devices + +### Phase 2: Parallel Operation +1. Re-pair additional devices in groups +2. Build basic automations in HA +3. Keep Apple Home running for critical functions +4. Test for 2 weeks minimum + +### Phase 3: Full Migration +1. Re-pair remaining devices +2. Migrate all automations to HA +3. Optional: Set up HomeKit bridge for family Apple access +4. Decommission Apple Home as primary controller + +### Phase 4: Voice Integration (Future) +1. Deploy voice automation stack per `voice-automation-architecture.md` +2. Local Whisper STT + Claude Code interpretation +3. Natural language home control + +--- + +## Sources + +### Home Assistant & Matter +- [Home Assistant 2026.1 Release Notes](https://rc.home-assistant.io/blog/2025/12/29/release-20261/) +- [Home Assistant Matter Integration](https://www.home-assistant.io/integrations/matter/) +- [Matter Standard 2026 Status Review](https://matter-smarthome.de/en/development/the-matter-standard-in-2026-a-status-review/) + +### Platform Comparisons +- [PCWorld Best Smart Home Systems 2026](https://www.pcworld.com/article/582873/best-smart-home-system.html) +- [Smart Home Wizards Matter Compatible Devices Guide](https://smarthomewizards.com/best-matter-compatible-smart-home-products/) +- [Hubitat vs Home Assistant Comparison](https://smarthomescope.com/hubitat-vs-home-assistant/) + +### Philips Hue +- [Home Assistant Philips Hue Integration](https://www.home-assistant.io/integrations/hue/) +- [Hue Bridge Pro Details](https://hueblog.com/2025/09/04/hue-bridge-pro-almost-all-the-answers-to-the-most-important-questions/) +- [Home Assistant 2025.12 Hue BLE Support](https://www.notebookcheck.net/Home-Assistant-2025-12-brings-new-Philips-Hue-integration.1177273.0.html) + +### Node-RED HomeKit +- [NRCHKB Documentation](https://nrchkb.github.io/) +- [LinkdHome Node-RED HomeKit Guide](https://linkdhome.com/articles/using-node-red-with-homekit) diff --git a/server-configs/home-assistant/.env.example b/server-configs/home-assistant/.env.example index f5ad47b..8b38604 100644 --- a/server-configs/home-assistant/.env.example +++ b/server-configs/home-assistant/.env.example @@ -7,5 +7,5 @@ # 3. Scroll to "Long-Lived Access Tokens" # 4. Create token and paste below -HA_URL=http://10.10.0.174:8123 +HA_URL=http://10.0.0.28:8123 HA_TOKEN=your_long_lived_access_token_here