Issue opening configured audio device #77

Activity

1. balloob commented on Jan 14, 2026

   

   balloob

   on Jan 14, 2026

   Contributor

   More actions

   @trisweb I guess systemd does not run under the same user as the person who ran the install script, so the original approach was correct and we should not list those other audio devices?
2. rajelaran commented on Jan 14, 2026

   

   rajelaran

   on Jan 14, 2026

   Last edited by rajelaran

   Author

   More actions

   Without those other devices, it seems not to work on systems that are using pulse/pipewire.
   I'm running sendspin on a system that's also a desktop, it's not a dedicated audio endpoint, so the ability to output audio into the software mixer alongside other applications is desired.
   Systemd does specify the user that sendspin is to run as, though? So it should work if that's working.

   see:

   [Unit]
   Description=Sendspin Multi-Room Audio Client
   After=network-online.target sound.target
   Wants=network-online.target
   
   [Service]
   Type=simple
   EnvironmentFile=/etc/default/sendspin
   User=rajel
   
   
3. trisweb commented on Jan 14, 2026

   

   trisweb

   on Jan 14, 2026 via email

   Contributor

   More actions

   Hey folks. The environment is the right direction I think; I have a working branch that uses that method. Will submit a PR shortly. The daemon does run as the original user (this should probably be configurable) so having the environment of the user to select audio devices is the right approach I think.

   …

   On Wed, Jan 14, 2026 at 2:04 PM Daniel Nowak ***@***.***> wrote: *lowlyocean* left a comment (Sendspin/sendspin-python-cli#77) <#77 (comment)> Does the systemd service file need a line such as the following, to tell it to connect to the Pulse session for user *raje1* ? Environment=XDG_RUNTIME_DIR=/run/pulse/1000/ (or whatever the UID of *raje1* is... I assume it's 1000 ) — Reply to this email directly, view it on GitHub <#77 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAV35DQJC6LD426NLYR2YL4G2HM5AVCNFSM6AAAAACRWM7SXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJRGE2DIOBSGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

   👍React with 👍2Reacted by Rajel Aran and Paulus Schoutsen
4. trisweb commented on Jan 17, 2026

   

   trisweb

   on Jan 17, 2026

   Contributor

   More actions

   If you'd like to test the new install script, you can run it off my branch (review the code first) using:

   curl -fsSL https://raw.githubusercontent.com/trisweb/sendspin-cli/refs/heads/trisweb-systemd-script-settings/scripts/systemd/install-systemd.sh | sudo bash

   It should both offer to create a dedicated user for the daemon, and use the correct environment to list all audio devices matching what that user will see when running the daemon. Let me know if it works as expected.
5. balloob

   closed this as completedin e758538on Jan 17, 2026
6. trisweb commented on Jan 17, 2026

   

   trisweb

   on Jan 17, 2026

   Contributor

   More actions

   Note: please re-open (or open a new issue) if testing reveals there are still issues. I was only able to test on a couple endpoints.
7. abmantis

   added a commit that references this issue on Jan 18, 2026

   Systemd install: use settings-daemon.json and refactor/improve (Sends…

   ...

   This issue will close once commit e758538 is merged into the 'main' branch.

   e758538