Recently, I embarked on a journey to enhance my smart home setup by transitioning from the ShellyForHass custom integration to the official Shelly integration in Home Assistant. This decision was driven by the desire for more reliable and continuous development support. However, the process wasn’t without its challenges, and I thought I’d share my experiences and tips to help others navigate this transition smoothly. Initial Setup and Challenges I started by updating all my Shelly devices and enabling CoIoT with unicast. The goal was to ensure seamless communication between my devices and the new integration. However, when I attempted to add the official Shelly integration through the Home Assistant interface, it wasn’t listed. Instead, the custom integration from HACS kept appearing. This was perplexing, as I had removed the custom integration to make way for the official one. The Solution After some research and troubleshooting, I discovered that the custom integration from HACS might still be blocking the official one. To resolve this, I completely removed the custom integration from HACS and restarted Home Assistant. Upon doing this, the official Shelly integration became available in the list, and I was able to proceed with the setup. Transferring Automations and Scripts One of the most critical aspects of this transition was ensuring that all my existing automations and scripts were preserved. I meticulously transferred each automation to the new entities provided by the official integration. This process required careful attention to detail to ensure that all functionalities were maintained. Post-Transition Cleanup Once the official integration was successfully set up and all automations were transferred, I cleaned up any remnants of the custom integration to avoid conflicts. This involved removing any leftover entities or configurations that were no longer necessary. Key Takeaways - Backup Your Configuration: Before making any changes, ensure that your Home Assistant configuration is backed up. This provides a safety net in case something goes wrong during the transition. - Remove Custom Integrations Completely: If you’re switching from a custom integration to an official one, make sure to remove all traces of the custom integration to prevent conflicts. - Test Thoroughly: After setting up the new integration, test all your devices, automations, and scripts to ensure everything works as expected. Final Thoughts Transitioning to the official Shelly integration has been a rewarding experience. The official support and continuous development provide peace of mind, knowing that my smart home setup is in good hands. I hope this guide helps others who are considering making the switch. Happy integrating!