mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-25 22:35:53 +03:00
[GH-ISSUE #130] Unable to control from loxone webinterface #70
Labels
No labels
bug
enhancement
pull-request
released
released on @beta
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lox-audioserver#70
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Lorrentop on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/130
Hello,
First of all, thank you in advance for the effort you put into setting up the audio server.
My main problem is that I am unable to control anything through Loxone.
This is how I have set it up:
Sendspin is connected correctly. I can discover my players through Spotify.
The lox-audioserver (beta) is running in Docker. The required ports are forwarded, and the server IP is 10.10.0.5.
Another issue is that my Sendspin players always start at 100 percent volume.
Any help would be appreciated.
Thank you!
@simon2207 commented on GitHub (Jan 21, 2026):
I would say... save your config again - from Loxone Configuration and restart the docker container one more time.
@rudyberends commented on GitHub (Jan 21, 2026):
Retrieving data means the Loxone app cannot reach the audioserver’s web endpoints. The Miniserver still can (otherwise the app would show Audioserver offline).
• Verify the app device can reach the audioserver on 7095.
• Test from the same network as the phone/tablet by opening in a browser:
• http://10.10.0.5:7095/
If these do not load, it is a networking/routing/firewall issue.
If the webapi loads in the browser:
1. In the audioserver admin UI, clear logs.
2. Set log level to debug.
3. Force-stop the Loxone app (ensure it is not running in the background), then open it again.
4. You should see multiple requests/commands from the app pulling status/config.
If you do not see those requests in the audioserver logs:
• Open the miniserver web client in a desktop browser, open Developer Tools → Network, then trigger a refresh/reconnect and check:
• Which host/IP the requests are going to
• Whether they fail (CORS, DNS, timeout, refused)
• Whether the app is trying a different address than expected
@Lorrentop commented on GitHub (Jan 26, 2026):
Thanks for the feedback. When changing to the Android app, it apparently works perfectly!
When setting up for the first time, I was always testing through the web browser interface (Firefox) on my main PC.
When playing music and controlling other elements, I get the correct feedback through the Android app.
But the web interface keeps waiting for receiving data. I just let you know this information, although I'm almost not using it.
@rudyberends commented on GitHub (Jan 26, 2026):
The web interface is the exact same application as the Android app. The Android app simply embeds the web app in a browser view, which makes it look like a native app.
I use the web app all the time for testing in different browsers, and it works without issues.
If it’s not working on your side, then your browser is likely unable to connect to the audioserver. You can use the browser’s developer tools to see exactly where the connection fails.
If you want to investigate further, please share the relevant information from the developer tools (Network + Console). If you don’t mind the issue, we can close this as it doesn’t appear to be a server-side problem.
Let me know how you’d like to proceed.
@martinsefcik commented on GitHub (Jan 26, 2026):
@Lorrentop, were you accessing the Loxone web interface directly using its local IP/hostname, or do you have it behind a proxy server?
I have it behind Nginx for HTTPS (since the Miniserver Gen. 1 doesn’t support access via HTTPS), and I was experiencing some issues when controlling audio that don’t occur when accessing the web interface directly.