[GH-ISSUE #75] Volume is added #29

New issue

Closed

opened 2026-02-27 19:28:00 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 19:28:00 +03:00

Owner

Originally created by @tokylo on GitHub (Nov 16, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/75

Hello
I use KNX MDT glass buttons to control the speaker volume.
With MS4H Music Server Zone and also with another installation using the original Loxone Audio Server and the Audio Player this always worked correctly.

With the lox-audioserver the value from input V is always added to the output Volume. The value from V is not applied each time but only incremented.

Is this a bug in the lox-audioserver or did I configure something wrong in Loxone?
See the video for details.

Thank you for your support.

https://github.com/user-attachments/assets/76cdb113-9e47-445c-b893-7d4bbfffc6e2

Originally created by @tokylo on GitHub (Nov 16, 2025). Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/75 Hello I use KNX MDT glass buttons to control the speaker volume. With MS4H Music Server Zone and also with another installation using the original Loxone Audio Server and the Audio Player this always worked correctly. With the lox-audioserver the value from input V is always added to the output Volume. The value from V is not applied each time but only incremented. Is this a bug in the lox-audioserver or did I configure something wrong in Loxone? See the video for details. Thank you for your support. https://github.com/user-attachments/assets/76cdb113-9e47-445c-b893-7d4bbfffc6e2

kerem closed this issue

2026-02-27 19:28:00 +03:00

kerem commented

2026-02-27 19:28:01 +03:00

Author

Owner

@rudyberends commented on GitHub (Nov 16, 2025):

Thanks for reporting this and for providing the video — it made the issue very clear.

The problem was caused by the volume command being interpreted as a relative change in all cases.
When sending a value from KNX / MDT glass buttons (e.g. audio/14/volume/40), the Loxone Audio Server expects this to be treated as an absolute volume value. The lox-audioserver incorrectly added this value to the current volume instead of applying it directly.

This has now been fixed.

The volume parser has been updated to correctly distinguish between:
• absolute values (e.g. 40)
• relative changes (+3 / -5)

Absolute volume is now applied exactly as expected, matching the behaviour of the original Loxone Audio Server.

I will release this soon. If you want to test it now, you can use the testing branch. If you need a docker container you can use;
ghcr.io/rudyberends/lox-audioserver:testing

Please let me know if it solves your issue.

@rudyberends commented on GitHub (Nov 16, 2025): Thanks for reporting this and for providing the video — it made the issue very clear. The problem was caused by the volume command being interpreted as a relative change in all cases. When sending a value from KNX / MDT glass buttons (e.g. audio/14/volume/40), the Loxone Audio Server expects this to be treated as an absolute volume value. The lox-audioserver incorrectly added this value to the current volume instead of applying it directly. This has now been fixed. The volume parser has been updated to correctly distinguish between: • absolute values (e.g. 40) • relative changes (+3 / -5) Absolute volume is now applied exactly as expected, matching the behaviour of the original Loxone Audio Server. I will release this soon. If you want to test it now, you can use the testing branch. If you need a docker container you can use; ghcr.io/rudyberends/lox-audioserver:testing Please let me know if it solves your issue.

kerem commented

2026-02-27 19:28:01 +03:00

Author

Owner

@tokylo commented on GitHub (Nov 17, 2025):

Super, I tested it and the volume adjustment via the KNX glass button works perfectly now. Thanks a lot for the quick fix!

@tokylo commented on GitHub (Nov 17, 2025): Super, I tested it and the volume adjustment via the KNX glass button works perfectly now. Thanks a lot for the quick fix!