Normal
As I wrote before about GetExternalMediaInfo, it's just a container of information that can be passed to WifiRemote to either start the media or show the media in the MP gui.Maybe it's enough with the id in MP2, maybe you need to know exactly the Serie, season, episode etc. in order to display it in the MP2 gui.I'm eager to test but I think it will have to wait until tomorrow before I can install the latest MP2 on my production HTPC. This since bridging network adapter is not working with the MP2 webserver, I never managed to reach the MP2 webserver outside Windows VM.Btw, Emby API has a really nice swagger interface where one can see what's implemented and also see parameters and test the calls out in a webbrowser without having to do trialing with api docs. Maybe that is something to look at further on. It really simplifies using the API.
As I wrote before about GetExternalMediaInfo, it's just a container of information that can be passed to WifiRemote to either start the media or show the media in the MP gui.
Maybe it's enough with the id in MP2, maybe you need to know exactly the Serie, season, episode etc. in order to display it in the MP2 gui.
I'm eager to test but I think it will have to wait until tomorrow before I can install the latest MP2 on my production HTPC. This since bridging network adapter is not working with the MP2 webserver, I never managed to reach the MP2 webserver outside Windows VM.
Btw, Emby API has a really nice swagger interface where one can see what's implemented and also see parameters and test the calls out in a webbrowser without having to do trialing with api docs. Maybe that is something to look at further on. It really simplifies using the API.