Starting playback with T5 Touch not working, instead it raises volume +1

[benleut]

When triggering touch to start playback, nothing happens, but in the app it works.

[rudyberends]

Thanks for following up on this — there are two separate things going on here, and one of them is a real bug.

The volume step is the T5 working as designed. The Miniserver, not the Audioserver, decides what a touch surface does. The standard Loxone mapping for an audio zone is:

Button 2 (top right): single click = volume up, double click = start playback / next favorite
Button 5 (bottom right): single click = volume down, double click = pause/stop

So a single click on the top right will always raise the volume — the Audioserver never even sees a play command in that case. To start playback from the T5, use a double click on button 2. If you'd rather have a plain play/pause on a single click, you can wire that up yourself in Loxone Config by linking the button to the Play/Pause input of the Audio Player block.

The part that was genuinely broken: that double click sends audio//roomfav/plus, and we only ever used it to cycle through room favorites. So on a zone that was paused on a Spotify track, it either jumped to your first radio favorite instead of resuming, or — if you have no room favorites configured for that zone — did nothing at all. Since the single click had already nudged the volume, the zone looked like it was only doing volume.

That's fixed now: roomfav/plus resumes what the zone was playing if there is something to resume, and only cycles favorites when the zone is already playing or has nothing to pick up. It is on dev now and t'll be in the next beta.

Could you try the double click once you're on that build and let me know? If it still doesn't start, a verbose log captured at the moment you press it would tell me whether the command reaches the server at all.

[benleut]

Thats not true, it is depending if there is already playback running.

If playback is running, single click means volume up. Double click means next room fav

If playback is paused, single click starts playback.

Just tested with loxone wireless speaker.

[rudyberends]

Let's settle this with a log.

Here is what I can and cannot see. A T5 press goes to the Miniserver. The Miniserver decides what that press means and then sends one concrete audio command to the Audioserver. We only ever receive that command. The press itself is invisible to us, so I cannot tell from here whether your click was read as "volume up" or as "start playback".

So there is one question that decides everything: what does the Miniserver send us at the moment you press?

To capture it:

Set the log level to debug in the Audioserver web interface.
Start playback in the zone from the app, then pause it.
Do one single click on the top right of the T5. Nothing else — no other presses, no app actions.
Note the time of that click, then download the log and attach it here.

Two possible outcomes:

• The log shows audio/zoneid/volume/+1 arriving. Then the Miniserver decided your click meant volume, and we did exactly what it asked. Nothing on the Audioserver caused that.
• The log shows another command arriving. Then it is on me, and I'll fix it.

[rudyberends]

One correction to what I wrote above, before your log lands.

I checked the Loxone documentation for the Audio Player block's T5 input (Audio Central KB), and it backs you up:

A single click on button 2 or 5 starts playback when the player is off.

So a single click is not simply "volume up" — what it does depends on the state of the player, exactly as you said.

That also means my two outcomes above were too tidy. If the log shows a volume command arriving, that does not by itself put the Audioserver in the clear: the Miniserver decides what your click means, and the state of the player is part of that decision. So the log tells us which command arrived, and then the question becomes why the Miniserver landed on that one. I may need a capture from a real Audioserver to compare against before I can answer that part.

What stays the same is the boundary. Whatever we find, I am not going to solve it by reinterpreting commands here — mapping "volume +1 while nothing is playing" onto a play action would also start playback when you press volume up in the Loxone app on a stopped zone.

So the log is still the next step, and it is still worth capturing.