Getting started with balenaSound is as simple as deploying it to a balenaCloud application; no additional configuration is required (unless you're using a DAC HAT). We've outlined the installation steps below. If you want a step-by-step tutorial on how to get balenaSound up and running, feel free to check these blog posts:
One-click deploy is the easiest way to get started with balenaSound as it allows you to deploy and configure the application with a single click and without the need of installing additional tools. Check out the
CLI deploy instructions below if you are interested in an advanced alternative that enables you to achieve more complex deployments.
Click this button to go straight to application creation, where balenaSound will be pre-loaded to your application:
Once your application has been created you'll need to add a device to it:
The balenaSound application will start downloading as soon as your device appears in the dashboard.
This is the traditional and more advanced approach for deploying applications to balena powered devices. Installing and setting up the balena CLI is definitely more involved than using the
Deploy with balena button, but it allows for more flexibility and customization when choosing what and when to deploy.
For example, if you don't plan on using the Spotify integration, you can edit the
docker-compose.yml file and remove the Spotify service before deploying the application.
Raspberry Pi (v1 / Zero / Zero W)as your application will then be compatible with all Raspberry Pi versions.
balena push <appName>where
<appName>is the name you gave your balenaCloud application in the first step.
If you are running into issues getting your balenaSound application running, please try the following: