Follow these steps to get the app (formerly known as add-on) installed on your system:
- In Home Assistant, go to Settings > Apps > Install app.
- Find the "Samba share" app and click it.
- Click on the "INSTALL" button.
- In the configuration section, set a username and password. You can specify any username and password; these are not related in any way to the login credentials you use to log in to Home Assistant or to log in to the computer with which you will use Samba share.
- Review the enabled shares. Disable any you do not plan to use. Shares can be re-enabled later if needed.
If you are on Windows you use \\<IP_ADDRESS>\, if you are on MacOS you use smb://<IP_ADDRESS> to connect to the shares.
This app exposes the following directories over smb (samba):
| Directory | Description |
|---|---|
local_apps |
This is for your local apps. |
app_configs |
This is for the configuration files of your apps. |
backup |
This is for your backups. |
config |
This is for your Home Assistant configuration. |
media |
This is for local media files. |
share |
This is for your data that is shared between apps and Home Assistant. |
ssl |
This is for your SSL certificates. |
The local_apps and app_configs shares were previously named addons and
addon_configs. Existing configurations are migrated to the new names
automatically. Both the new and legacy share names stay exposed and point to
the same directories, so existing connections keep working while you move to
the new names.
App configuration:
username: homeassistant
password: YOUR_PASSWORD
workgroup: WORKGROUP
enabled_shares:
- local_apps
- app_configs
- backup
- config
- media
- share
- ssl
compatibility_mode: false
apple_compatibility_mode: true
netbios: true
local_master: true
network_discovery: true
server_signing: "default"
veto_files:
- ._*
- .DS_Store
- Thumbs.db
- icon?
- .Trashes
allow_hosts:
- 10.0.0.0/8
- 172.16.0.0/12
- 192.168.0.0/16
- 169.254.0.0/16
- fe80::/10
- fc00::/7The username you would like to use to authenticate with the Samba server.
The password that goes with the username configured for authentication.
Change WORKGROUP to reflect your network needs.
List of Samba shares that will be accessible. Any shares removed or commented out of the list will not be accessible.
List of hosts/networks allowed to access the shared folders.
List of files that are neither visible nor accessible. Useful to stop clients
from littering the share with temporary hidden files
(e.g., macOS .DS_Store or Windows Thumbs.db files)
Setting this option to true will enable old legacy Samba protocols
on the Samba app. This might solve issues with some clients that cannot
handle the newer protocols, however, it lowers security. Only use this
when you absolutely need it and understand the possible consequences.
Defaults to false.
Enable Samba configurations to improve interoperability with Apple devices. This can cause issues with file systems that do not support xattr such as exFAT.
Defaults to true.
NetBIOS is a legacy network protocol for accessing SMB/CIFS shares. Enable for legacy clients older than Windows Vista (Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager), or OS X 10.9 (Mavericks). This setting is enabled by default for compatibility; disable it on modern installations.
Defaults to true.
When NetBIOS is enabled, try and become a local master browser on a subnet.
Defaults to true.
Advertise the host on the network using Web Services Dynamic Discovery, so it appears automatically under Network in Windows File Explorer. Disable this if you connect to the shares by hostname or IP address and do not want the host to announce itself on the network.
Disabling this has no effect on share availability; only on discovery.
Defaults to true.
Configure the SMB server signing requirement. This option can improve security by requiring message signing, which helps prevent man-in-the-middle attacks. Refer to the man page for smb.conf for detailed information about the values: default, auto, mandatory, and disabled.
Defaults to default.
Got questions?
You have several options to get them answered:
- The Home Assistant Discord Chat Server.
- The Home Assistant Community Forum.
- Join the Reddit subreddit in /r/homeassistant
In case you've found a bug, please open an issue on our GitHub.