as of Samba add-on version 11.0.0 we now have a change in the underlying folder being shared.
/config was changed to /homeassistant
and working properly as such, no errors at all anywhere.
considering I have the /config/etc/etc in many yaml configs, either backend:
sensor:
- platform: file
file_path: /config/logging/filed/filed_notifications.txt
name: Filed notifications
or frontend:
title: Welkom
icon: mdi:home
path: welkom
type: custom:vertical-layout
#layout:
# max_cols: 2
cards:
- !include /config/dashboard/buttons/buttons_dashboard_direct.yaml
- !include /config/dashboard/includes/include_alerts_dashboard.yaml
- !include /config/dashboard/includes/include_alarm_armed.yaml
I was confused whether we should edit those accordingly. As said, even though all was working properly and no errors are logged.
I tried the frontend as that was easiest, and no, that is not accepted by the system, Dashboard responds with a
in "/config/dashboard/dashboards/ui-overzicht/view_overzicht_Welkom.yaml", line 9, column 5: Unable to read file /homeassistant/dashboard/buttons/buttons_dashboard_direct.yaml.
so, this means we now have a new folder /homeassistant
in the system, but is is mapped to /config
in our files.
just like we have the /www
folder, but we need to reference it as /local
btw the docs in the Samba add-on still show the former
but I take it that is soon to be updated .
Would appreciate if someone has the insight of explaining the why of this change, and maybe even the future. Will we soon need the /homeassistant reference anywhere in the user files, or is this all only for internal Add-on usage?
introducing conflicting folder names is a bit of an oddity, especially given the fact this is a very frequently referenced naming structure copied directly into our yaml files.