Have noticed on devices that a particular command can exist in both its ‘media player’ entity and its ‘remote’ entity. What is the difference? Are there any pros or cons in using one vs the other?
It depend on the integration. Media player support basic commands such as play / pause / seek / shuffle etc while remote can support much more. Media player is often used in integrations to also provide rich media info with dynamic data such as album art, artist name etc. Developers can fhen use it to their advantage to show other dynamic data but since media player also support basic commands so they add it natively. Some integrations will need the media player for state change for capturing device power state where remote can’t detect that. So, it’s vary depending on the integration and need. But play pause stop etc commands will function the same if in media player or remote entity per the developer code base.
1 Like
Good info. Thank you. Having the remote display what is currently showing is defintiely a nice feature to have 
I have noted though that the media player display is a little erratic, sometimes showing a blank screen. If I go out of it and back in again, then the display resets and shows the proper image. Haven’t done extensive testing - mostly with AppleTV.