Daemon
An optional service is packaged in order to help with applications requiring constant access to devices.
Architecture
A list of local and remote (WI-DG) devices is maintained. Upon discovering a device, it is probed for its type and model, then made available to applications.
Static devices
Remote devices that are advertised are usually discovered, but if running into some issue it's possible to add a static device and make it always available.
minidsp probe --net
will output the urls for the devices it finds.
Example
Add a WI-DG device while bypassing auto-discovery
[[static_device]]
url = "tcp://192.168.1.2:5333"
Configuration
The following default configuration file is installed in /etc/minidsp/config.toml
:
#
# A configuration file can define many components that share the same underlying devices
#
# A default HTTP server is exposed via a unix socket at /tmp/minidsp.sock
# If set, the daemon will ignore network broadcasts for discovering devices, which can be inconvenient when dealing with complex multi-device setups
# The desired remote devices can then be manually added using `[[static_device]]` sections
# ignore_advertisements = true
# If desired, an api can be exposed over the local network
[http_server]
bind_address = "127.0.0.1:5380"
# Replace the previous line by this one in order to allow connections from other hosts
# bind_address = "0.0.0.0:5380"
# TCP servers can be setup to support using the native "plugin" apps to manage the device
[[tcp_server]]
bind_address = "127.0.0.1:5333"
# Replace the previous line by this one in order to use the plugin app from another machine
# bind_address = "0.0.0.0:5333"
# If multiple minidsp devices are used, the following options can be used to expose multiple
# plugin-compatible servers for each devices.
# device_index = 0 # Use the first device available
# device_serial = 912345 # Use the device with this serial number
# Advertise the following address for the official minidsp mobile app
# advertise = { ip = "192.168.1.100", name="Living Room Pi" }
# More servers can be declared with different bind addresses and device bindings
# Since the official apps don't support setting the port number, different addresses must be used
# for different devices.
#[[tcp_server]]
#bind_address = "192.168.1.128:5333"
# Devices can be added statically instead of being automatically discovered
# Use `minidsp probe` to find the correct URL
# [[static_device]]
# url = "usb:0001%3A0005%3A04?vid=2752&pid=0011"
# If a wi-dg isn't auto-discovered, it can be added with
# url = "tcp://192.168.1.2:5333"
# It's possible to declare mock devices for testing purposes, and give them different serial numbers
# A `response_delay` needs to be specified if connecting with the minidsp plugin, as it doesn't appreciate fast replies.
# The `serial` parameter has to be betwen `900000` and `965535`
#
# [[static_device]]
# url = "mock:?serial=911111&response_delay=50"
#
# [[static_device]]
# url = "mock:?serial=922222"