I recently took the plunge into the world of smart home automation by integrating Shelly devices with Home Assistant. Initially, I followed a YouTube tutorial that recommended using the ShellyForHASS component, which supposedly offered more functionality than the core integration. However, after installing the component, I quickly realized I might have made a misstep. The devices weren’t behaving as expected, and I noticed an error in the logs suggesting that the core Shelly integration should be used instead.
After deinstalling ShellyForHASS and restarting Home Assistant, I was hopeful for a fresh start. But to my surprise, Home Assistant now listed three Shelly devices: the actual device, the old ShellyForHASS entry, and another duplicate. Additionally, the integration interface displayed an error message about the configuration possibly coming from a custom integration. Despite multiple restarts and checks, the issue persisted.
After some research, I discovered that removing the Shelly entry from the configuration.yaml file was necessary. However, even after doing so, the problem remained. The duplicate devices and entities were still present, and the error message kept appearing. This was frustrating, especially since I wanted a seamless integration experience.
Finally, I found a solution by purging all related entries from the Home Assistant database and reinstalling the core Shelly integration. This process restored everything to normal, and now my Shelly devices function perfectly within the core integration. It was a valuable learning experience, emphasizing the importance of sticking with official integrations whenever possible.
If anyone else is experiencing similar issues, here’s what I recommend: carefully remove any custom integrations, ensure all related entries are deleted from the configuration files, and restart Home Assistant. This should help resolve any conflicts and allow the core integration to work smoothly. Happy automating! 