Error: "Missing repository for an install add-on" after upgrade to 2024.6.0

[denverpilot]

The problem

After upgrade the following error is given as a UI warning on my instance:

---

Missing repository for an installed add-on
Translation Error: The intl string context variable "addon_url" was not provided to the string "Repository for add-on {addon} is missing. This means it will not get updates, and backups may not be restored correctly as the supervisor may not be able to build/download the resources required.

Please check the add-on's documentation for installation instructions and add the repository to the store."

Warning - 6/5/2024

It looks like a bug in parsing the add-on name judging by seeing "{addon}" exposed in user output.

What version of Home Assistant Core has the issue?

core-2024.6.0

What was the last working version of Home Assistant Core?

core-2024.5.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Current Add-On List (if needed):
Advanced SSH & Web Terminal
ESPHome
File editor
Home Assistant Google Drive Backup
Mosquitto broker
Studio Code Server
Tailscale
TasmoAdmin
TasmoBackup

[denverpilot]

A little more digging. The link to the "addon's documentation" points to :
https://github.com/danmed/TasmoBackupV1/

It's the TasmoBackup Add-on that needs an update, looks like.

[denverpilot]

Did not intend to close. Unsure how to reassociate to the add-on, however.

[KJThaDon]

Anyone figure out how to fix this?

[denverpilot]

See if this reopens it.

I believe the Add-on needs an update and I think @frenck owns the add-on… ??? Shrug. Dunno.

[denverpilot]

Dang it GitHub. The default UI on mobile keeps trying to force you to close the report. Trying again to reopen…

[tommasisimone]

I have the same warning message but I don't have TasmoBackup installed.

This is what I see in the logs:
Failed to format translation for key 'component.hassio.issues.issue_addon_detached_addon_missing.description' in language 'it'. Error: The intl string context variable "addon_url" was not provided to the string "Repository for add-on {addon} is missing. This means it will not get updates, and backups may not be restored correctly as the supervisor may not be able to build/download the resources required. Please check the add-on's documentation for installation instructions and add the repository to the store."

[RJ-Make]

I also have the same warning message but I don't have TasmoBackup installed.

[ChristophCaina]

The problem is probably, that the Addon in question is not providing the required information to generate a meaningfull repair message.

These are probably addons, installed through custom repositories - the "TasmoBackup" addon seems to be owned by danmed...

the other addon warning from @tommasisimone:
With the available information, it is unclear what addon is causing this.
Can you maybe report what addons you have added (not from the default addon store, but through custom repositories?)

[DarcyDetlor]

Same problem. I was trying to figure out what happened, and one time this message appeared, but it was listing Google Backup. I checked, and the Google Drive Backup repository was gone. After I replaced GDB repository, the original message with "Repository for add-on {addon} is missing. This means it will not get updates, and backups may not be restored correctly as the supervisor may not be able to build/download the resources required." reappeared.

I do not have TasmoBackup installed.

[stajodude]

Same problem here. Error message is "{"message":"Handler does not support user"}". I can no longer reach Developer Tools nor Settings->System. Nor can I restart from Settings.

[stoffies00711]

Google Drive Backup, Sunsynk/Deye and Modbus/TCP repos were missing from addons. Added them again and their errors disappeared.
Now stuck with that "Missing repository for an installed add-on" error. It does not specify the addon. My Home Assistant still works perfectly apart from that error message. I don't think it's being caused by one specific addon.

[mdegat01]

Hm it seems like there's an issue getting the URL of these detached addons from config. I had thought translation placeholders were optional and it would just use empty string but it seems they are required. Just put in a PR to instead always link to the addon page within HA for all addons so addon_url is always provided regardless of what is or isn't in the addon's config, that should fix this up.

[Martynhsmith]

Mine was saying "Missing repository for an install add-on Tasmta backup" so I uninstalled tasmota backup
It then reported the same thing but no name
I have reinstalled tasmota backup and have the same no name error

[jello1974]

Same here
Translation Error: The intl string context variable "addon_url" was not provided to the string "Repository for add-on {addon} is missing. I think the new AI is messing with my setup.....:)

[silversegarra]

Same problem here... waiting for a solution :)

[jeraisel]

added:
http://github.com/danmed/TasmoBackupV1
to the repositories ad it says on the https://github.com/danmed/TasmoBackupV1/
went back to the addon and there was an update ready.
after restarting home assistant, the message was still there
Missing repository for an installed add-on

[24zeven]

This error is closed 2 days ago, but it looks like that it's still not fixed.
I updated from 2024.5.5 to 2024.6.1 and this found this error today.
"Repository for add-on Home Assistant Google Drive Backup is missing."

Does anyone know how it is solved and what can I do to solve it?
Or is this going to be solved with a fix in 2024.6.2 ??

[DarcyDetlor]

I also upgraded to 2024.6.1 and my error still exists.

[eldeldani]

Same issue here. In my case "Repository for add-on Zigbee2mqtt is missing." If I click on the provided link for the add-on documentation and then click on the changelog for zigbee2mqtt addon I get "Addon 7ad98f9c_zigbee2mqtt with version latest does not exist in the store".

I have tried readding the repository to the add-on store but message persists.

[ChristophCaina]

the repair message itself is no HomeAssistant issue.
If you have installed addons from Custom Repostories - and you receive a repair (including relevant information about the addon, etc.) then you should raise an issue with the addon-developers.

It is expected that a repair will be shown, if the Repository URL has changed, for example.
The Repair should let you know that there is an issue and you wont be able to receive updates for your addon any more.

[denverpilot]

the repair message itself is no HomeAssistant issue. If you have installed addons from Custom Repostories - and you receive a repair (including relevant information about the addon, etc.) then you should raise an issue with the addon-developers.

It is expected that a repair will be shown, if the Repository URL has changed, for example. The Repair should let you know that there is an issue and you wont be able to receive updates for your addon any more.

First, GitHub obfuscates whether you’re someone speaking for the HA team or just a rando commenting. Can you elaborate?

Second, are you saying all the add ons in the “store” created by HA devs are fixed and this only now affects add-ons outside the ecosystem? I do not believe that to be the case but will test.

Were add-on devs notified this change was coming? This seems like an introduced bug more than an announced change. I’m unaware of anything that stated these items were mandatory prior to simply changing the parsing.

Seems like net negative to the users also when clearly updates worked fine prior to the change.

I’m used to seeing this sort of breakage reverted until proper developer notification can be done. It’s not the users fault it wasn’t properly communicated. Why the reluctance to allow the add-ons to update?

More importantly, if an add-on dev does release a patch for the uncommunicative change process, the upgrade (I assume) is blocked? Yet another reason to allow a transition period.

[ChristophCaina]

First, GitHub obfuscates whether you’re someone speaking for the HA team or just a rando commenting. Can you elaborate?

Since HA is an OpenSource project, "anyone" can contribute - and also provide support.
You don't have to be a member of the "HA-Team" - you can just submit your Code Changes as a PR...

The repair itself is part of a change, introduced in the supervisor (PR for implementing UI feedback into the core #118064; PR for the Supervisor "Create issue for detached addons" home-assistant/supervisor#5084)

The Dialog is using information, the Addon should provide.
And as usually, installing Community addons, is - just the same as for Custom Components (HACS integrations) ALWAYS at your own risk.

Just because HA is showing a repair for an addon - and in fact it is showing you the required information - can not be considered as a bug - in my humble opinion.
It's something different, when the Repair Dialog does not show anything (just as it was during the beta) - or then, just as you mentioned in your ticket (when you opened it) - placeholders.

But when people here starting to report issues for each of their community addons that will now be reported as a repair, because the Repository URL might has changed - I doubt, that this will help to improve the situation.

I agree, that the devs should provide a documentation of what information is missing in their developer blog or where ever (don't know, if that already happened)... but it is either the responsibility of the one who installed the community addon (on their own risk) - or of the devs of the addon to asure that it will work properly...

The repair message itself is still a benefit, because it is indicating that something might be wrong with the addon... maybe, it won't be further developed anymore, or supervisor is not able to detect if there's a newer version available.

[denverpilot]

So

On Mon, Jun 10, 2024, at 15:37, Christoph wrote: Since HA is an OpenSource project, "anyone" can contribute - and also provide support.

So you’re providing random “support” on code you don’t write? Ok.

You don't have to be a member of the "HA-Team" - you can just submit your Code Changes as a PR...

Duhhhhhhh.

The repair itself is part of a change, introduced in the supervisor (PR for implementing UI feedback into the core #118064 <#118064>; PR for the Supervisor "Create issue for detached addons" home-assistant/supervisor#5084 <home-assistant/supervisor#5084>)

Which broke official add-ons (still is) and not just third party ones. Are you paying attention?

The Dialog is using information, the Addon should provide. And as usually, installing Community addons, is - just the same as for Custom Components (HACS integrations) ALWAYS at your own risk.

The add-ons broken are in the official store. They’re not some rando stuff. This is breakage of what add-ons need to provide without prior warning. A BUG. (Until you publish your intention to break working things.)

Just because HA is showing a repair for an addon - and in fact it is showing you the required information - can not be considered as a bug - in my humble opinion.

If it stops the add on from updating, it’s a BUG, no matter your fake “humble” opinion. You’re not humble at all. You’re making up rules that weren’t communicated and pretending they’re authoritative. Are you saying there’s a fix that allows continued updates to happen whether the add on provides this info now? I’m not seeing it. Clearly the error isn’t that there isn’t a repo — if it could update from the repo before, the repos are all still there and working fine.

It's something different, when the Repair Dialog does not show anything (just as it was during the beta) - or then, just as you mentioned in your ticket (when you opened it) - placeholders.

Why I ask if there was a second fix. Haven’t made it home yet to test but if updates are still blocked by the BUG, it’s a bug.

But when people here starting to report issues for each of their community addons that will now be reported as a repair, because the Repository URL might has changed - I doubt, that this will help to improve the situation.

If the project doesn’t want to support auto updates for community add-ons, they don’t have to. But breaking working updates is a BUG.

I agree, that the devs should provide a documentation of what information is missing in their developer blog or where ever (don't know, if that already happened)... but it is either the responsibility of the one who installed the community addon (on their own risk) - or of the devs of the addon to asure that it will work properly...

The add on writers aren’t mind readers. If it’s not clearly documented what an add on needs to provide — breaking working updates is a BUG.

The repair message itself is still a benefit, because it is indicating that something might be wrong with the addon... maybe, it won't be further developed anymore, or supervisor is not able to detect if there's a newer version available.

It detected versions just fine before the change. it’s a BUG. lol. Seriously. Get off it. It’s clearly just parsing stuff not needed to update the add-on, that it never cared about before. If there’s a reason it now cares, just document it for other devs. Thru can’t guess that your code is going to enforce something it never did before. I seriously doubt it was on purpose. It smells like being sloppy and tossing errors on something new just for the sake of tossing an error. Which well, whatever… except it penalizes the user for no particular reason and makes it look poorly planned and executed. There’s ALWAYS a period of deprecation and log warnings prior to enforcement — unless well communicated there won’t be for some good reason. In this case, non-pro environment … it’s just a mistake. In a pro environment this is a process failure. Takes solid policy and peer review to catch. No biggie. Will see here in a bit if updates are still blocked. That’s… a bug. You need to give the add on devs time to update before you block… their updates. Go figure. Logical flow. Hahaha. This wasn’t in “Breaking Changes” so I’m saying it’s simply an error. Not intentional. You claim it’s intentional. Weird.

[ChristophCaina]

Which broke official add-ons (still is) and not just third party ones. Are you paying attention?

does it?
which one of the addons below (from your list) is an official addon?

• Current Add-On List (if needed):
• Advanced SSH & Web Terminal
• ESPHome
• File editor
• Home Assistant Google Drive Backup
• Mosquitto broker
• Studio Code Server
• Tailscale
• TasmoAdmin
• TasmoBackup

I can tell you:

• File editor
• Mosquitto broker
• ESPHome (can be considered as an official addon)

These are "official" Community addons - and also listed under "community addons"

• Studio Code Server

• Advanced SSH & Web Terminal

• Tailscale

• TasmoAdmin

• Tasmo Backup couldn't be found in the store.
  It seems to be a custom addon, added manually - so I don't know which URL you have added to your addon store:
  https://github.com/danmed/TasmoBackup
  https://github.com/danmed/TasmoBackupV1

I guess, it is the "V1" - and there are already issues open in the Repository of this Addon, related to the repair:
danmed/TasmoBackupV1#93
-- but going through the issue list there, it also seems, that this repository is depricated and no longer maintained.

last update was two years ago, unanswered issues and PRs open...
Or, you maybe have used another forked repository?
https://github.com/danmed/TasmoBackupV1/forks

In addition:
The Addon can't update because of the repair message - Nor because of the supervisor, detecting that there seems to be an issue with the repository URL... ;)

[denverpilot]

It isn’t TasmoBackup that’s throwing the error.

Try again fake unofficial support guy. Lol.

(But it is in your list. And is owned by Frenck. So I doubt there was any miscommunication on it needing a Repo. Grin…)

[1nutty1]

Any fix for this as yet, I see the latest update to Core did not resolve the issue...

[ChristophCaina]

It isn’t TasmoBackup that’s throwing the error.

Try again fake unofficial support guy. Lol.

(But it is in your list. And is owned by Frenck. So I doubt there was any miscommunication on it needing a Repo. Grin…)

lol... blame others for your messed up system ;)

[denverpilot]

Ah yes. Blame the user for selecting things from the official add-on “store” when someone breaks them upgrading. That’s some high quality work right there! lol.

If my system is broken, I didn’t break it. lol. The dev who arbitrarily started checking for an unnecessary field did. Grin.

How about… if nobody’s actually maintaining it to made up fictional “standards” that weren’t published, just announce it’ll be removed?

Still haven’t given a proper story for why a parsing error introduced by a GUi dev is suddenly important — when the add-ons worked just fine (including upgrades) without the arbitrary repo field before… hmmm.

It’s a BUG. Introduced without proper thought as to the consequences of checking for a non-mandatory unneeded piece of information in an add-on.

Maybe @frenck will fix his add-on packages, maybe he’ll deprecate them, maybe they just sit here in Warning forever... Shrug. Not my call.

But they’re still erroring/throwing unnecessary warnings at the users. Wasn’t fully fixed.

(Not claiming TasmoAdmin or the others missing the info are great packages but if they’re going to be in the UI as add-ons, if the rules for add-ons changed, they should be maintained or removed/deprecated with proper notice beforehand…)

I can run em outside of HA juuuuust fine if I need em. But they shouldn’t be throwing warnings if installed thru the UI… that’s not a good user experience. Just yank em if nobody has time to work on em to make them meet new arbitrary rules.

User experience today: Install add-on, it immediately throws a warning something is wrong with it.

That wasn’t before. And doesn’t need to be a warning at all if the thing is static and unchanging.

The argument that it hasn’t been updated in years really doesn’t hold water — it is what it is and it didn’t change. The warning rule did.

Without notice. The broken add-ons are not listed in Breaking Changes… but a big old warning sitting there on the main screen for no real reason, is kinda silly to defend.

Claiming I broke it — hilarious. Nope. Just installed things HA offered. And still offers. Most users have no idea about repos and such — they just see an interesting looking add-on in the “store”.

(I keep putting “store” in quotes because I have no idea why it’s called that. It’s not like users buy anything from it. Grin… trying to evoke a sense of app stores from mobile walled garden terminology, I guess? Again, shrug… a UI topic for another day, but kinda fun.)

Oh well. Not my project, not my warning bubbles. Hahaha. Pretty easy to just uninstall the breakage of their own add-ons for some of this stuff. Thought a bug report would be … shall we say, useful if they didn’t know they broke their own add-ons. If it’s going to be ignored, waste of time.

HA is going to do whatever HA is going to do. Like always. Grin.

Even weirder to have a fake support guy blame the user for installing their add-ons and claiming the user broke it. lol. Classic. I kinda enjoyed this open source weirdness. Cheers. Add-ons uninstalled. Bye bye.

[lauris-nl]

Hi guys,

I have this warning in my "Repairs" list.
I think "Spook 👻 Your homie" put it there?

Missing repository for an installed add-on
Repository for add-on TasmoBackup is missing. This means it will not get updates, and backups may not be restored correctly as the supervisor may not be able to build/download the resources required.

Please check the add-on's documentation for installation instructions and add the repository to the store.

Warning - 7/22/2024

[lauris-nl]

Update: solved

I had 2 versions of TasmoBackup installed
version: 1.04.26
version: 1.05.00

Version: 1.04.26 is missing its repository.

Manual transfer the settings. Run Backup all. And uninstall version: 1.04.26.