Serviio

I am assuming you read the information here: https://www.serviio.org/alexa

It sounds like that info was written for Serviio before version 2.0. User accounts are a new feature starting with 2.0 , and are on a separate Users tab on the console. But there are two steps to creating and using a User account. First of course is to create the user name and password. But then you have to go into your Library Shared Folders and give that user explicit permission to use that library. If you have multiple shared folders ( I have seven), you have to grant that permission to each folder you want that user to be able to access. This step is often overlooked and can cause access problems.

At the very top of that page is a link to setting up remote access. Make sure you've followed all of those steps first, as that is required (I believe) for Alexa to work.

I'm experiencing the same problem.

- I am currently using the free evaluation version of Serviio Pro (for a few more days) (I was hoping to get this working before I had to pay for it)
- I can access the media browser remotely (http://james-curran.com:23424/mediabrowser/#/browse) using the username & password
- Whenever I attempt to link the account to the Alexa skill, it responds "The provided credentials are not valid. Try Again" (I have double- and triple-checked them; they are correct).
- Viewing the HTTP traffic for the logon, (https://y2il4cp25a.execute-api.us-east- ... prod/login), it gets a http 401 status, with the message "Authentication error: ServiioId nG8TiytDFT not found".
- So, it seems that the Alexa service doesn't know about my server. How do I tell it about it?

Same for me, can access the media browser from any device in my house, but not getting anywhere with the Alexa skill.

OK, after trying to link the skill many times, it magically took (perhaps my IP had to work its way through to serviio, who knows).

This is also helpful:

https://serviio.org/alexa