philchillbill wrote: 
> Would be really great to have it because those big touchscreens on the
> Echo Show devices are going to waste currently with this skill. 
> 
> It would also be very helpful if there was a JSON command to create a
> named network player. Right now the only way to do it is to GET the LMS
> url with “/stream.mp3?player=Alexa”. After that http call, the player
> exists and can be configured via JSON like any other player. It’s just a
> pity that the creation cannot be from JSON too.

Here that would be different. I would need to have the list of alexa
players to be bridged and I can create as many matching LMS players as I
want. Today I do UPnP and mDNS discovery but you might want to give them
to me using another way. Then you query LMS and use a special named
category to know which ones a alexa bridges. 

What codecs does alexa accept? What is the way you want to grab audio? A
HTTP server is good enough? Is the skill pointing alexa to an URL’s
where to do a GET?

I can’t remember that from our experiments with Paul. I need to look at
the code and it’s a bit late for now.



LMS 7.9  on Pi 3B+ & Odroid-C2 - *SqueezeAMP!*, 5xRadio, 3xBoom, 4xDuet,
1xTouch, 1 SB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000,
ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2,
Squeezelite on Pi,  Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5,
Riva 1 & 3
------------------------------------------------------------------------
philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=111016

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to