Supervisor 2021.02.1 seams breaking the Addon

Dear @blakeblackshear thanks a lot for this awesome addon and customcomponent. It was runing like a charm. Unfortunately I face an isse after upgrading my supervisor (supervised install method of Home assistant).

Now each time I want to save my config I geet this error (Chrome console):

chunk.97b95a62afbc18471344.js:3350 Uncaught (in promise) TypeError: Cannot read property 'find' of null
    at HTMLElement.value (chunk.97b95a62afbc18471344.js:3350)
    at HTMLElement.performUpdate (entrypoint.cf81f6d9.js:35547)
    at HTMLElement._enqueueUpdate (entrypoint.cf81f6d9.js:35547)

Could not load content for webpack://home-assistant-frontend/chunk.97b95a62afbc18471344.js (HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME)

{result: "ok", data: {}}
data: {}
result: "ok"

I dunno what’s going on here or how I can find the issue. If you might have a look in this. I guess this will impact other users with updated suervisor as well.

Please let me know if you need additional information.

[blakeblackshear]

Just pushed a new version of the addon. Frigate’s config can no longer be managed in the Configuration tab of the addon (at least for now). The addon expects a frigate.yml file to exist in the root of your homeassistant config directory. You can edit it using whatever editor you use for homeassistant config.

That I would love. Dont understand all this “in app configuration” that can not be version handled.

If you are using HassOS the snapshots take backups of your addon config too, but this is exactly why frigate does not have the ability to modify it’s own config. Even when it does, it will always just be a UI for modifying the config file with a clear option for those who want to save it out into source control since this is how I do it. There will never be a .storage folder for frigate.

[hawkeye217]

As a work-around, I’ve backed up a JSON formatted version of my configuration (used faq to convert from YAML to JSON) and installed a watch on the option.json file to replace it by the backup as soon as it is overwritten by supervisor:

root@hassio:~# while true ; do inotifywait /usr/share/hassio/addons/data/be8d440d_frigate-beta/options.json ; cp /usr/share/hassio/addons/data/be8d440d_frigate-beta/options.json{.bak,} 
; done

Managed to do something similar to get the addon started again. Thanks for the tip.