Skip to content

Conversation

@ftesser
Copy link

@ftesser ftesser commented Jan 25, 2026

When enabling snapclient from the web interface, the service does not start even though the flag is correctly set.

In the snapclient case block of srv/http/bash/features.sh, when snapclient is enabled:

  • The flag is set
  • Audio options are configured in /etc/default/snapclient
  • Flag file is moved if snapserver is active
  • pushRefresh is called

However, the service is never actually started.

Proposed Solution

Add the service start command symmetrically to the stop command:

$dirbash/snapclient.sh start



This implementation has been tested and confirmed to work correctly in my device.

@rern
Copy link
Owner

rern commented Jan 31, 2026

SnapClient start sequence:

  • Settings > SnapCast (next to Networks)
    • Search for SnapServer > Select if more than 1 found
    • Connect
      No needs to start and leave it running when not needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants