Describe the issue you are experiencing
App: Samba share
Version where it started: 12.7.0
Previous behavior: 12.6.x and earlier
What changed:
The 12.7.0 changelog entry "Add Windows automatic discovery support with WSDD" introduced a WSDD daemon that runs unconditionally whenever the app starts. After updating, Home Assistant suddenly appears as a device in the Windows Network view.
Expected behavior:
With compatibility_mode set to false, the app previously did not advertise the host on the network. The share was still fully reachable
via \hostname or . I expect that turning off legacy/compatibility options keeps Home Assistant from broadcasting itself.
Actual behavior:
Home Assistant now broadcasts via WSDD regardless of configuration. There is no option in the app config to turn it off, the current schema has no wsdd key, and compatibility_mode: false has no effect on it. This is a new, unavoidable behavior introduced by an update, with no opt-out.
Impact:
Users who connect by direct \hostname/IP path don't want the host appearing in network discovery, and there's currently no way to revert to the pre-12.7.0 behavior short of downgrading and pinning the app.
Requested fix:
Add a config option to disable WSDD (e.g. wsdd: false), or gate the WSDD daemon behind compatibility_mode / an explicit "advertise on network" toggle, so the discovery behavior can be turned off.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which app are you reporting an issue with?
Samba share
What is the version of the app?
12.7.x
Steps to reproduce the issue
Steps to reproduce:
1. Run Samba share add-on 12.7.x with compatibility_mode: false.
2. Open File Explorer > Network on a Windows machine on the same LAN.
3. Home Assistant appears as a discoverable device, with no config option to prevent it.
System Health information
N/A
Anything in the Supervisor logs that might be useful for us?
Anything in the app logs that might be useful for us?
Additional information
No response
Describe the issue you are experiencing
App: Samba share
Version where it started: 12.7.0
Previous behavior: 12.6.x and earlier
What changed:
The 12.7.0 changelog entry "Add Windows automatic discovery support with WSDD" introduced a WSDD daemon that runs unconditionally whenever the app starts. After updating, Home Assistant suddenly appears as a device in the Windows Network view.
Expected behavior:
With compatibility_mode set to false, the app previously did not advertise the host on the network. The share was still fully reachable
via \hostname or . I expect that turning off legacy/compatibility options keeps Home Assistant from broadcasting itself.
Actual behavior:
Home Assistant now broadcasts via WSDD regardless of configuration. There is no option in the app config to turn it off, the current schema has no wsdd key, and compatibility_mode: false has no effect on it. This is a new, unavoidable behavior introduced by an update, with no opt-out.
Impact:
Users who connect by direct \hostname/IP path don't want the host appearing in network discovery, and there's currently no way to revert to the pre-12.7.0 behavior short of downgrading and pinning the app.
Requested fix:
Add a config option to disable WSDD (e.g. wsdd: false), or gate the WSDD daemon behind compatibility_mode / an explicit "advertise on network" toggle, so the discovery behavior can be turned off.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which app are you reporting an issue with?
Samba share
What is the version of the app?
12.7.x
Steps to reproduce the issue
Steps to reproduce:
System Health information
N/A
Anything in the Supervisor logs that might be useful for us?
Anything in the app logs that might be useful for us?
Additional information
No response