So I use this addon regularly and I don't see anything like this in my logs. I also took a dev system I have on the latest supervisor and core and installed the referenced addon yesterday. It's been almost 24 hours now and I still don't have this log line.

It's especially confusing because the addon you're referencing actually does have a changelog. The problematic addons previously where the ones without changelogs.

I'm kind of scratching my head here. Can you try restarting core and see if maybe there's something bad that is cached behind the scenes?

@vin100ross Ah I think I figured out what's going on. Looking at the diagnostic data you linked your system is missing the addon repository for the google drive backup addon.

Like if you remember when you first installed that addon you had to add this this repository to your list of addon repositories: https://github.com/sabeechen/hassio-google-drive-backup . And then you found the addon in your list and installed it. That repository is no longer listed in your list of addon repositories which means supervisor cannot find any information about it and is causing strange errors like this.

That also explains why your google drive backup addon is very out of date. That addon is currently on version 0.112.1, you're running 0.105.2 which is I guess about 3 years old? Although its not actually listed on that repo so perhaps it was pulled for some reason, I'm not sure.

Can you try adding that repository to your list of addon repositories and see if that fixes it?

Great find @mdegat01! I added the repository back and the errors stopped. Very strange that the repo went missing, however... I'm certain I never removed it intentionally (I wouldn't know how).

Looking at the core issue I linked above, I am obviously not the only one with this problem. May I suggest a better diagnostic that detects that an addon repository is missing or no longer valid, and a more descriptive error message suggesting adding it back to the addon store? Just the fact that the repo can go missing may be a bug in itself...

In any case, I am closing this issue since I consider this solved on my side. If you think it would be appropriate, I can file another issue for the confusing error message. If another repo mysteriously goes missing, I'll file an issue for that then.

That's a really good idea. We should have a repair for that. I'll look into that 👍

Thanks' Work for me also

Just come across the same myself - google backup repo missing, pretty sure I didn't remove it :-/