smarties wrote:
> Thanks for the quick response - no luck with that I'm afraid. Discovery
> only finds my regular players (squeezelite based), not any of my echos.
>
> I've tried disabling and re-enabling the skill and gone through set up
> again but no luck with that either.
>
> Anything else I could try ?
Discovery never mentions your AlexaPlayers as they are ephemeral
they're just network clients that get created and destroyed on the fly
when needed. In the skill's logs, I can see you are getting
Code:
--------------------
"request": {
"type": "AudioPlayer.PlaybackFailed",
"requestId": "amzn1.echo-api.request.d68a6a76-d3b0-4a02-ad89-5735dce927f4",
"timestamp": "2022-04-16T17:23:50Z",
"locale": "en-GB",
"currentPlaybackState": {
"playerActivity": "STOPPED"
},
"error": {
"message": "Device playback error",
"type": "MEDIA_ERROR_SERVICE_UNAVAILABLE"
},
"token": "1650129829508"
}
--------------------
People randomly get this (very sporadically) when an AWS server
allocated to their Alexa account has a different patch-level to the
norm. Try setting your device language for one of the Echos (in the
Alexa app) to something other than en-GB (for example, en-US) and see if
you can stream then. If so, switch back and see if it stays good.
Just to check, the skill thinks your LMS is at 192.168.0.160:9000. Is
that correct for your LMS?
------------------------------------------------------------------------
philchillbill's Profile: http://forums.slimdevices.com/member.php?userid=68920
View this thread: http://forums.slimdevices.com/showthread.php?t=111016
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
