Unable to uninstall local addon that has failed

Installation Home Assistant OS
1

Trying to uninstall addon that had an improper name. I have already deleted from the addon directory but get the following errors when I run the uninstaller from Hassio.

19-11-13 21:07:41 INFO (SyncWorker_7) [hassio.docker.interface] Remove image local/amd64-addon-5310Infinitive with latest and None
19-11-13 21:07:41 WARNING (SyncWorker_7) [hassio.docker.interface] Can’t remove image local/amd64-addon-5310Infinitive: 400 Client Error: Bad Request (“invalid reference format: repository name must be lowercase”)

Thanks.

1 Like
2

Same issue here, it seems that is it possible to create addons with an uppercase character in the name (slug).

Any attempt to stop or uninstall them using the interface or cli results in the Bad Request error shown above.

3

I have the same problem, anyone knows how can I remove a local add-on from supervisor page?

I tried the command from ssh
ha ad uninstall local_Test

but it gives this error

Error: Unknown Error, see logs

4

I’ve never solved it either. Thought it was because I physically deleted them first. Probably caused because I started their names with a capital letter and other one with a number. Would really like to solve this.
5310

5

I found the solution.

first you need to follow this instructions


to get ssh access to the host

then edit the file addons.json in /resin-data directory and delete your local add-on configuration lines.

Finally you have to reboot the host.

1 Like
6

Hi
Running Hassio and can’t seem to find /resin-data or addons.json Any ideas?
K

7

Old thread but just in case it helps somebody else…

On hassos, addons.json is under /mnt/data/supervisor, You will have to go through the debugging instructions as noted bove to be able to SSH into the host and then run login to get shell access.

In my case, there were 2 sections related to the failing local addon. Deleting both of them and restarting the supervisor container (docker ps to find the container id and docker restart <containerid> to restart it) seems to have cleaned everything up without having to restart the host.

1 Like
8

B1G and alexanv’s suggestion worked flawlessly for me!
Although restarting only the supervisor docker container left me with a broken supervisor screen, restarting the whole system seems to have resolved any issues that were raised :smiley:

9

Supervisor not starting. Rebooted still no supervisor. Any ideas ?

10

little bit related on this topic, but not fully the same. I have some log statements in supervisor complaining about addons which are not installed anymore. So i’m trying to find the location where i can get supervisors input file where it gets the notion of the addons being present.

21-10-01 12:56:20 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot_exclude' is deprecated, 'backup_exclude' should be used instead. Please report this to the maintainer of AdGuard Home
21-10-01 12:56:20 WARNING (MainThread) [supervisor.addons.validate] Add-on config 'snapshot' is deprecated, 'backup' should be used instead. Please report this to the maintainer of UniFi Controller

both adguard and unifi were installed and uninstalled. so the logs are faulty and i would like the supervisor cleaned.

mnt/data folder seems empty here (running hassio). where could i start looking further?

2 Likes