Samba add-on changed /config to /homeassistant

[Mariusthvdb (Marius)]

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.

[Mariusthvdb (Marius)]

see comments on the GitHub documentation change I pr’d:
the change is being reconsidered

[malosaa (Hector)]

Just seen the reply of Frenck,

so no worries no panic

[boheme61]

i just updated, and indeed /config is where it was

PS: In File Editor

[GaryK (Gary Kelley)]

This is what I see on my W10 box. I’ll need to modify a few pointers to get backups working again.

[sender]

Then I do not get Frenck as /config is not used? it changed to /homeassistant…?

[boheme61]

yes, i get the point

Maybe it can be easily “fixed” with a symlink in the root of the container
edit: nope don’t seems to work , from windows

[malosaa (Hector)]

@sender

/homeassistant

so it changed to /homeassistant ?
if so i won’t update anyway.

[justone]

lucky me not having a ‘homeassistant’ defined within the veto files … for the sake to prevent seeing such nonsense.

But since one could do a rollback to the last sensefull version, no problem.

[faderjockey]

I installed Samba share today and can mount any volume, with the exception of ‘homeassistant’.
I get an error of : The operation can’t be completed because the original item for “homeassistant” can’t be found

[boheme61]

have you installed latest core, and rebooted ?

[faderjockey]

I’m on 2023.11.2
Have done a restart of home assistant.

Are you saying I need a cold restart as well?

[boheme61]

you could try, or open a terminal and type " cd / " and verify whether you have /homeassistant or still /config there

[faderjockey]

Cold start. same issue.

When I look in Studio code server, the directory name is still CONFIG, but smb still presents me with this ‘homeassistant’ share that leads nowhere, and there’s no ‘conifg’ volume listed (assuming that has to do with the topic in the bulk of this thread).

[boheme61]

yes, there are a few bug reported in regards to this, how ever i have /homeassistant in the / of my terminal, as well as in /root folder there, there should be symlinks to /homeassistant, check again
PS: on the other hand i had Samba installed when i updated to 2023.11.2

And only thing that don’t work is if i try to access /config from windows, which is fine for me, haven’t “discovered” other than 1 own-made reference , which i change to /homeassistant/*

[faderjockey]

At the root level in SCS, I only show CONFIG, OUTLINE, TIMELINE and MDI EXPLORER.
There is a ‘homassistant’ file in the CONFIG directory, but SCS gives me a ‘file not found’ if I select it.

All I’m trying to do is to transfer some files into the www directory, I guess I’ll explore other routes at this point. Bit disappointing as smb would have been so simple…

[boheme61]

@faderjockey

At the root level in SCS, I only show CONFIG, OUTLINE, TIMELINE and MDI EXPLORER.

? i have no idea where you are, Do you have a terminal/ssh add-on installed ?
Could you open it, and type ls -la, then post a screenshot

[faderjockey]

My bad, I was assuming I was looking at my entire file structure…

Here’s what I show:

[boheme61]

ok, then type cd , and hit enter
and verify that you have a folder named … homeassistant , then then type … cd homeassistant, hit enter,

[faderjockey]

No such file or directory