addon_configs has become apps_config

[reedy]

As a follow on from https://community.home-assistant.io/t/why-im-proposing-we-rename-add-ons-to-apps-and-why-it-matters-for-newcomers/945712 and then since 2026.2 in https://www.home-assistant.io/blog/2026/02/04/release-20262/

On terminal and Filebrowser, it's still /addon_configs/, but on File Editor (6.1.0) it's referred to as /apps_configs/

Migrate to the new all_app_configs folder mapping name introduced in Home Assistant Supervisor

home-assistant/addons@e030c15

The predbat docs seem to refer to use File Editor (such as on https://springfall2008.github.io/batpred/install/#editing-configuration-files-in-home-assistant), so this is going to start causing confusion down the the line

[gcoan]

Thanks for raising this @reedy it is actually more complicated than it seems.

I have changed the documentation to refer to app_configs rather than addon_configs, and also changed the auto-restart documentation and code, and the example predbat/givtcp error monitors to use the new app nomenclature.

However we have to make sure we do not break existing installations. For the app restart it was fairly easy to do, have enabled the new app restart parameter but retained the addon restart parameter.

But predbat uses /Volumes/addon_configs/6adb4f0d_predbat in the code deployment scripts and makes a HA service call to /addons/self/info to determine the slug id. If a predbat user is using an older HA supervisor then these will break.
Therefore have deferred making these changes now and propose that these be changed in Feb 2027; giving enough time for migrate to new HA supervisors. Will raise new GitHub ticket for that future change