search

blakeblackshear / frigate-hass-addons

Frigate hass.io addons
MIT License
248 stars 134 forks source link

Beta addon updated to stable #181

Closed Morphy99 closed 3 months ago

Morphy99 commented 3 months ago

As the Beta Addon was updated to the stable image, removing the beta results in this error when trying to start stable: Image ghcr.io/blakeblackshear/frigate:0.14.0 does not exist for addon_ccab4aaf_frigate-fa

I had to remove both and reinstall. I'm not sure why the beta was updated to the same image as the stable. This could also cause issues in the future when the new beta is started and a user has auto update on...

NickM-27 commented 3 months ago

What do you mean? If the beta image isn't updated then users wouldn't be on the latest version. Updating the image used for the beta won't cause any issues as users can stay on it indefinitely. We will always be disabling auto update for the addons

Morphy99 commented 3 months ago

I get that they wouldn't be on the latest version but it's caused issues with how HA OS has managed the same image with both add-ons. I don't want to jump on the latest beta of 0.15 so have gone back to the stable add-on. Removing the beta addon caused the image for both to be deleted.

NickM-27 commented 3 months ago

right, the flip side of that is that users want to just stay on the beta addon and not deal with having to reconfigure the integration every time. Once 0.14.1 comes out the beta and stable addons will be updated again.

in general, this is a bug in HA supervisor if multiple images point to the same image

Morphy99 commented 3 months ago

Sure. I'm not debating what users will do going forward. It's just unusual for a beta channel to be using stable images and it's caused a bug in the HA addon system.

NickM-27 commented 3 months ago

I disagree though, for example the home assistant beta tag always gets updated to the stable versions

Morphy99 commented 3 months ago

Ok, so what's the solution to the bug? Do I need to log it with HA OS GitHub? Or should you be using different images (which are essentially the same) to avoid this issue?

NickM-27 commented 3 months ago

I would suggest filing a bug with the HA supervisor github repo

Morphy99 commented 3 months ago

https://github.com/home-assistant/supervisor/issues/5244