Hi guys,
Scratching my head here…
When I use the ‘say’ function in dsl rules and use a Heos player as the target audio sink, 3 things happen that I do not expect:
- After the ‘say’ function has been executed, audio resumes playback even if the audio wasn’t playing before executing ‘say’.
- The playback always resumes with the next track in the current playlist, not the track that was playing during the execution of ‘say’.
- When playback resumes it plays from the local playlist, not the Spotify playlist or TuneIn station that was actually playing.
I’d expect:
- No prior playback = Not resuming playback.
- Resume playback of the actual track that was paused.
- Resume playback of the actual source that was playing.
EDIT 24/04/2025: After some more testing I can report that the “playSound” function basically shows the same misbehaviour.
Am I missing something or is this the intended behaviour?
Do more users encounterd this behaviour?
I switched from a LMS based multiroom audio system to HEOS and I never expected this misbehaviour. The LMS system worked well with openHAB, and I like to use the “say()” and “playSound()” functionality. What’s going on here? Is this happening only with my setup, or is this actually the way the functions should be working (maybe because of limitations within the HEOS platform)?
Maybe one of the binding’s devs or maintainers can shed some light on this issue?
Thanx.
Best regards, Jesse