Skip to content

Audio Support#86

Draft
ccutrer wants to merge 3 commits intoseime:masterfrom
ccutrer:audio
Draft

Audio Support#86
ccutrer wants to merge 3 commits intoseime:masterfrom
ccutrer:audio

Conversation

@ccutrer
Copy link
Copy Markdown
Contributor

@ccutrer ccutrer commented Apr 20, 2026

  • Channels for controlling media player entities
  • Expose media player components as openHAB audio sinks
  • Expose voice assistant components (microphones) as openHAB audio sources

@ccutrer
Copy link
Copy Markdown
Contributor Author

ccutrer commented Apr 20, 2026

@seime: I've not tested this with an actual device yet, since I don't yet have one with a speaker or microphone, but plan to build one at some point. I just wanted to get this up here in the meantime, in case someone else can fully test it.

Would you prefer I break it up into 3 PRs, though - one for media player entities, one for audio source, and one for audio sink?

@ccutrer
Copy link
Copy Markdown
Contributor Author

ccutrer commented Apr 20, 2026

Ohhhhh, well..... the AudioSource depends on PipedAudioStream, which was first added in openHAB 4.2, so can't be compiled for 4.0 (I run 5.2-SNAPSHOT).

@seime
Copy link
Copy Markdown
Owner

seime commented Apr 20, 2026

I'm good with either 1 or 3 PRs, preferably not too big or not changing too much of the existing codebase (much harder to review).

Regarding version; perosnally bumping parent version to 4.2 isn't an issue, but could be for some users (I have no insights on what they are using). Changing the artifact name (including version) might break the marketplace listing since it AFAIK requires a stable link to the artifact.

@jimtng
Copy link
Copy Markdown
Contributor

jimtng commented Apr 20, 2026

people still using older versions of openhab can just pin their binding version to a known working one. But since we don't have any versioning system here, that won't work.

@seime
Copy link
Copy Markdown
Owner

seime commented Apr 23, 2026

@jimtng the reason I haven't bothered with a proper release cycle is

  1. The OH marketplace expects a stable link to the artifact
  2. It doesn't support multiple versions, with a workaround to create and maintain multiple marketplace postings for each (which I won't)

Sure I could work around some of these limitations, IMHO the extra hassle isn't worth it (for me). Though, I'm happy to take PRs to improve this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants