mrlt8 / edge-repo Goto Github PK

I'm not entirely sure how the process works for add-ons, but I know that the ESPHome (dev) add-on has a "Rebuild" button that will cause it to rebuild the docker image from the latest dev branch.

When we install the dev add-on from this repo, it installs a statically named "dev" image, and then never gives an option to update it or rebuild it. As far as I can tell, the only way to get a newer version is to uninstall and reinstall (but maybe I'm mistaken?)

Some information (about 2/3 down the article.. I tried to link to the section, but the link-to-highlight seems to get removed randomly by LinkedIn) I've found online seems to indicate that the Rebuild button is shown when the config.json does not contain an image field, which your dev repo does: https://github.com/mrlt8/edge-repo/blob/main/dev/config.json

For comparison, esphome-beta contains an image field: https://github.com/esphome/home-assistant-addon/blob/main/esphome-beta/config.yaml#L38
while esphome-dev does not: https://github.com/esphome/home-assistant-addon/blob/main/esphome-dev/config.yaml
Also esphome-dev contains a build.yaml to describe how to do the rebuild: https://github.com/esphome/home-assistant-addon/blob/main/esphome-dev/build.yaml

It took me a long time to realize that my add-on was out of date (v2.0.1 while v2.1.5 was available), because Home Assistant did not offer to update it since version "dev" == "dev". I was using the dev build to test out some earlier changes you made for testing the Wyze Cam OG, and then never switched back to the main add-on image. I've since uninstalled the dev add-on and reinstalled the main one, so at least now I'll get update notifications again.