Music Assistant
-
@megaboz783ee4a692 thank you for sharing your thoughts on this! I’ve added your vote to the feature request!
-
I cant see how to add this as a service. maybe i’m missing something. no real instructions on how to add this as a source.
-
@sbarrowcliff78 it’s in the beta, it will be released in the next major update for Music Assistant, likely coming in September.
-
@mikerockwell – yes it is in the beta Music Assistant – https://github.com/orgs/music-assistant/discussions/3664#discussioncomment-17405735
-
It was released today:
https://www.music-assistant.io/blog/2026/08/26/music-assistant-2-10/So it’s now possible to have PocketCasts on Home Assistant! Thanks to the hard work of the contributors, especially @yfhyou.
To all the folks at PocketCasts, have a look at the open source code and see if there are any improvements you can make, it would be appreciated. -
@blucose that’s excellent news — congratulations to @yfhyou and everyone who put in the work. Nine months from the first post in this thread to shipping in 2.10 is a great run.
One thing I should be upfront about: the Pocket Casts provider is built and maintained by the Music Assistant community rather than by us, so it isn’t something we’re able to support or troubleshoot, and we can’t promise it’ll keep working if things change on our end. The Music Assistant repo is the best place to raise anything that breaks.
That said, I’m glad you flagged it here — I’ll make sure the team sees it, and it’s a good thing to have alongside the feature request this thread has been feeding.
-
@mikerockwell unless I’m mistaken, the Pocket Casts addition to Music Assistant, (which is extremely welcome and works brilliantly BTW), is open source and maintained by the community so there’s no reason why the Pocket Casts devs can’t contribute to it or at the very least ensure that it continues to function. This would be the correct course of action in my opinion.
-
Thank you so very much for this integration. This kind of thing is why I use and support PocketCasts.
-
@yorkie71 I hear you, and you’re right that it’s open source — there’s nothing stopping us from contributing, and I’d genuinely like to see this keep working for everyone using it.
The honest answer is just that it has to compete for time against the integrations we’ve built and maintain ourselves, and those tend to come first. That’s not a no, and it’s not me brushing it off — I just don’t want to promise something I can’t be sure we’ll deliver. What I can tell you is that the team knows the integration exists and that people are actively relying on it.