You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[…] if your addon wants to provide file-based output or give users access to internal files […]
[…] you should add addon_config:rw to map so your addon can write to this folder as well as read from it. And then you should write these files out to /config during your addon's runtime so users can see and access them.
I understand how the issues with changing config.ini raised in #639 were resolved by making them changeable via API, but as far as I could tell still no longer possible to set weathermap API key, or backup database easily.
Sounds like it should be straightforward to add
"map": [
"addon_config:rw"
],
and update PSACC_CONFIG_DIR environment variable to point to /config (therefore matching the docker image setup)
That should mean that all config files (config.ini, config.json), and database would be available by SSH to home assistant host and looking in /addon_configs/b9f12d83_psacc directory
The text was updated successfully, but these errors were encountered:
According to Home Assistant add-on configuration docs:
I understand how the issues with changing config.ini raised in #639 were resolved by making them changeable via API, but as far as I could tell still no longer possible to set weathermap API key, or backup database easily.
Sounds like it should be straightforward to add
and update
PSACC_CONFIG_DIR
environment variable to point to/config
(therefore matching the docker image setup)That should mean that all config files (
config.ini
,config.json
), and database would be available by SSH to home assistant host and looking in/addon_configs/b9f12d83_psacc
directoryThe text was updated successfully, but these errors were encountered: