Overview
Musique Agent runs on Raspberry Pi devices to provide reliable, dedicated audio playback for your locations. This guide covers the complete installation and configuration process for Raspberry Pi 4 devices.Requirements
Before you begin, ensure you have:Hardware
- Raspberry Pi 4
- Power supply
- Audio output (3.5mm jack or HDMI)
- SD card (16GB+ recommended)
Software
- Debian-based OS (Ubuntu 24.04.3 LTS recommended)
- ALSA audio system
- PulseAudio
- Docker
This guide assumes you have a fresh installation of Ubuntu 24.04.3 LTS on your Raspberry Pi 4.
Installation Process
Step 1: Install ALSA
ALSA (Advanced Linux Sound Architecture) is required for audio output.1
Check if ALSA is installed
Run the following command to verify if ALSA is already present:If you see a list of packages, ALSA is already installed.
2
Install ALSA (if needed)
If ALSA is not installed, run:
3
Verify Installation
Check that audio devices are detected:You should see your audio output device listed.
Step 2: Install PulseAudio
PulseAudio manages audio routing for the Musique Agent.1
Check if PulseAudio is installed
Verify PulseAudio installation:
2
Install PulseAudio (if needed)
If not installed:
3
Verify Installation
Start PulseAudio (should produce no output if successful):
Step 3: Install Docker
Docker is used to run the Musique Agent container.1
Check if Docker is installed
Verify Docker installation:If you see a version number, Docker is installed.
2
Install Docker (if needed)
Install Docker and configure permissions:
3
Verify Installation
Confirm Docker is working:
Configuration
Configure ALSA for PulseAudio
Create an ALSA configuration file to route audio through PulseAudio.1
Create Configuration File
Open the ALSA configuration file:
2
Add Configuration
Paste the following content:
3
Save and Exit
Press
Ctrl + X, then Y, then Enter to save and exit.4
Reboot
Reboot the Raspberry Pi to apply changes:
Install Musique Agent
Download Docker Image
1
Authenticate with GitHub Registry
Login to the GitHub Container Registry using your organization token:
2
Pull the Image
Download the latest Musique Agent image:
Run Musique Agent
1
Get Your User ID
Find your host user ID:Note the number (typically
1000).2
Run the Container
Start the Musique Agent with your credentials:
3
Verify Connection
The agent should connect to Musique servers and appear online in your Analytics dashboard.
Enable Auto-Start on Boot
Configure the Musique Agent to start automatically when the Raspberry Pi boots.1
Create Systemd Service
Run the following command to create a systemd service (replace
1000, [your_username], and [your_password]):2
Enable the Service
Enable and start the service:
3
Reboot and Test
Reboot to test auto-start:After reboot, the agent should start automatically.
Verify Installation
After installation, verify everything is working:Check Agent Status
Check Agent Status
View the service status:Status should show “active (running)”.
View Logs
View Logs
Check agent logs for any issues:Press
Ctrl + C to exit.Test Audio Playback
Test Audio Playback
Verify audio output is working:You should hear test sounds. Press
Ctrl + C to stop.Check Online Status
Check Online Status
- Log into your Musique dashboard
- Navigate to Analytics
- Verify the device appears as online
Troubleshooting
No audio output
No audio output
Check audio device:Verify PulseAudio is running:Test audio directly:
Agent not starting
Agent not starting
Check service status:View error logs:Common issues:
- Incorrect username/password
- Network connectivity issues
- Docker not running:
sudo systemctl start docker
Docker permission denied
Docker permission denied
Add user to docker group:Log out and log back in for changes to take effect.
Device offline in dashboard
Device offline in dashboard
- Check internet connection
- Verify credentials are correct
- Check service is running:
sudo systemctl status musique-agent - Review logs:
sudo journalctl -u musique-agent -f - Test network connection:
ping google.com
Managing the Agent
Service Commands
Update the Agent
To update to the latest version:1
Stop the Service
2
Pull Latest Image
3
Restart the Service
Best Practices
Network Connection
Use wired Ethernet connection for best stability and audio quality.
Power Supply
Use official Raspberry Pi power supply to prevent stability issues.
Audio Output
Test audio output before deploying to ensure proper configuration.
Regular Updates
Keep the agent updated to receive latest features and bug fixes.
Monitor Status
Regularly check device status in Analytics dashboard.
Backup Config
Keep a copy of your systemd service file for easy redeployment.
Next Steps
Create Schedules
Set up audio schedules for your new Raspberry Pi device.
Monitor Performance
Track your device status and network quality in Analytics.
Test Network
Use the Speed Test tool to verify connection quality.
FAQ
Find answers to common Raspberry Pi setup questions.

