help
Troubleshooting
The short list, learned from real installs. If yours is not on it, open an issue — a log excerpt and your setup shape (Docker or bare, host or bridge networking) shorten every conversation.
Devices are not discovered
Discovery — how the server finds Sonos, Chromecast, AirPlay and DLNA devices — needs
host networking. On bridge networking, expect to assign some outputs by IP by hand.
If you run Docker with -p port mappings instead of --network host, that is
the first thing to change.
The server won't start: port in use
Port 7090 must be free on the host — host networking bypasses port publishing, so
another service on 7090 collides directly. With Loxone enabled, 7091 and
7095 join in.
A GPIO relay does nothing
Configure the chip plus the line offset within that chip. On a Raspberry Pi 4,
header GPIO22 is typically line 22 on /dev/gpiochip0. The old sysfs-style
global number such as 534 is not what gpioset expects — a correctly wired
relay will sit silent.
From Docker, also expose the devices: the container needs /dev/gpiochip* or
/dev/hidraw*, or calls that work on a host shell will still fail inside the container.
Network share won't mount
Mounting an SMB/CIFS share as the library needs Unix mount tooling (mount.cifs) — so a
Linux host. On Windows, point the library at a local folder instead.
Loxone pairing does not complete
- Check the serial and host in Loxone Config against what the Admin UI shows.
- Split the stereo outputs into 4 zones and drag them into the project — an Audio Server without zones in the project does not pair.
- Deploy and reboot the Miniserver; pairing starts on its way back up.
- Ports
7091and7095must be reachable from the Miniserver.
Where the logs live
In the Admin UI under Logs, live; and on disk in the data folder. The
Setup page's Copy diagnostics button collects what an issue report needs.
Something else?
The README and INTEGRATING.md go deeper on every topic here, and the issue tracker is read.