I think that in this case the route would be .... Skill works out which LMS proxy player maps to which Alexa device and gets IP address. Then when play is to be started ... Alexa grabs the pls via https (has to be https) from the back-end of the skill which returns the IP address of the proxy player. Alexa then does http gets expecting Shoutcast-style stream to play .... (although Alexa player currently ignores the metadata I think but making it optional to include would be good just in case they one day add support) if possible this would then may the proxy player start fetching from the LMS queue and drip-feeding Alexa.
For testing ... the proxy ->Alexa mapping could be static with the proxy player not disappearing. On Pause/Next/Stop the skill would tell LMS .. controling the proxy player. Paul Webster http://dabdig.blogspot.com author of \"now playing\" plugins covering radio france (fip etc), kcrw, supla finland, abc australia, cbc/radio-canada and rte ireland ------------------------------------------------------------------------ Paul Webster's Profile: http://forums.slimdevices.com/member.php?userid=105 View this thread: http://forums.slimdevices.com/showthread.php?t=111016 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
