I recently encountered a frustrating issue while trying to update AppDaemon on my Home Assistant setup. After successfully running version 0.0.12, I decided to update to 0.0.13. Unfortunately, the update process didn’t go as smoothly as I hoped. When I attempted to update, I faced an error in the supervisor logs, which stated that the repository couldn’t be found. This was perplexing because I hadn’t made any changes to my add-on repositories recently.
After several attempts to resolve the issue, I decided to take a more systematic approach. I started by reviewing my add-on repositories in Hass.io. I noticed that the repository for AppDaemon was still listed, but I wasn’t sure if it was up to date. I decided to remove the repository entirely and then re-add it. Here’s the step-by-step process that worked for me:
- Remove the Repository: I went to the add-on repositories section in Hass.io and deleted the entry for
vkorn/hassio-addons. This was the repository where AppDaemon was hosted. - Save and Update: After removing the repository, I saved the changes and manually updated the list of available repositories. This step ensures that Hass.io refreshes its cache and checks for any new or updated repositories.
- Re-add the Repository: I re-added
vkorn/hassio-addonsto the list of repositories. It’s important to ensure that the repository URL is correct to avoid any further issues. - Update Again: With the repository re-added, I saved the changes once more and attempted to update the AppDaemon add-on again.
- Success!: This time, the installation went through without any issues. AppDaemon 0.0.13 was successfully installed, and everything started working as expected.
Reflecting on this experience, it seems that the problem was related to the repository configuration rather than the add-on itself. By temporarily removing and re-adding the repository, I was able to reset the configuration and resolve the issue. It’s a good reminder to always check repository settings when facing installation problems.
I hope this solution helps anyone else who might encounter a similar issue. If you’ve had success with troubleshooting Hass.io add-ons, I’d love to hear about your experiences in the comments below!