After experiencing frequent Ecobee cloud outages, I decided to migrate to a more reliable local control solution using HomeKit Controller. Here’s my journey and tips for anyone considering the same transition.Why the Switch? The Ecobee cloud integration was unreliable, causing automation failures. Moving to HomeKit Controller meant local control, reducing dependency on external services.Setup Process 1. Network Adjustment: Ensured Ecobee thermostats were on the same network as Home Assistant. This was crucial for ZeroConf discovery.2. HomeKit Integration: Added the Ecobee thermostats through HomeKit Controller. The setup wizard guided me seamlessly, requiring only a code from the thermostat’s screen.3. Configuration: Assigned areas in Home Assistant and renamed entities for clarity. I kept the original Ecobee integration for custom settings while using HomeKit for core functions.Challenges and Solutions - Unsupported Features: HomeKit Controller doesn’t support custom comfort settings. I adapted by using built-in modes (Home, Away, Sleep) and scripts for advanced automation.- Entity Management: Renamed entities to differentiate between cloud and local control, ensuring a smooth transition.Results The migration was a success! Local control eliminated cloud dependency, and the system is more responsive. I still use the Ecobee cloud integration for specific features, but HomeKit handles the essentials reliably.Tips for Others - Network Setup: Ensure all devices are on the same network for optimal discovery.- Entity Naming: Rename for clarity to avoid confusion between integrations.- Backup Automation: Keep existing scripts for unsupported features while exploring new HomeKit capabilities.This transition not only improved reliability but also deepened my understanding of Home Assistant’s flexibility. I’m now confident in my local setup and ready for further enhancements!