Can't access Windows share owned by user containing a space

[madbrain76]

The problem

My Windows system has a username of the form "FirstName LastName", as it has since the very first time I used a multi-user version of Windows 3 decades ago. I'm unable to open the share from HA.

What version of Home Assistant Core has the issue?

core-2024.6.4

What was the last working version of Home Assistant Core?

it never worked

What type of installation are you running?

Home Assistant OS

Integration causing the issue

N/A

Link to integration documentation on our website

N/A

Diagnostics information

If I add the share to Home Assistant under Settings / Storage, I'm able to enter my username with a space, and save. However, the share is not opened, and if I go back to edit it, both the username and passwords have been deleted.

Changing the username under Windows to one without a space is an extremely disruptive change, and not a viable workaround. So, I'm unable to share anything from my Windows system to Home Assistant because of this problem.

I tried using escaping in the name (\040 for the space), but that didn't work.

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:135
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 22:08:30 (3 occurrences)
Last logged: 22:08:45

Failed to to call /mounts/TESTSHARE - Mounting TESTSHARE did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-TESTSHARE.mount for details.

Additional information

Here is how I mount the share on my Raspberry Pi :

madbrain@pi64:/etc $ cat /etc/fstab
``
# irrelevant entries removed

//higgs.local/Network\040Backups /higgs_backup cifs _netdev,credentials=/etc/creds,uid=madbrain,gid=madbrain,x-systemd.automount 0 0

madbrain@pi64:/etc $ cat /etc/creds
username=Julien Pierre
password=removed

[home-assistant[bot]]

Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of hassio can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign hassio Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

hassio documentation hassio source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.