Closed jjlawren closed 1 year ago
This method also fits the media browser/source payload model to allow browsing from other integrations' media collections as it can just return type
/id
pairs that can be used by the media_player.play_media
service directly, even across integrations.
Following the prior art from Media Source, prefixing the media_content_id
with a domain identifier seems like the cleanest way forward. I've put a draft together here that allows Cast media players to accept Plex media_player.play_media
payloads.
This architecture issue is old, stale, and possibly obsolete. Things changed a lot over the years. Additionally, we have been moving to discussions for these architectural discussions.
For that reason, I'm going to close this issue.
../Frenck
Context
Some integrations are able to provide media which could be played by other integrations'
media_player
entities.Proposal
The behavior to allow the integration domain in the
media_content_type
of the current payload ofmedia_player.play_media
could be extended across integrations to convey this information.Example service call for
media_player.play_media
:I see a couple potential ways this could be implemented:
play_media
handler for integrations which can accept another integration's media. For example,cast
would need to know how to handle aplex
media item above.<domain>.play_media
. It would be up to the media source's integration to handle. This might involve modifying the payload to fit the playback destination and re-callingmedia_player.play_media
on the player entity.Consequences
type
/id
payload model of themedia_player.play_media
when a completely new approach could be warranted.