Alexa Skill
Question. How does one pronounce Serviio? is it serv-E-o or serv-I-o. neither one triggers the skill for me.
when i tell alexa "Simon says ask serviio" she pronounces it serv-i-e-o; is that how we're supposed to say it?
jared69sib wrote:Yes. Remote access works. I have a secure check, and entered my ddns for the domain..... remote access works from my serviigo app...
Maybe I should try removing my ddns?
Tried it and didnt help....
I even tried matching ports exactly like in your link..
zip wrote:So I tried connecting to your domain, http (insecure) works on 23424, secure (https) on 23524.
So update your console settings accordingly - or update your router forwarding to match whatever you have in the console)
zip wrote:I can still see your server identifying itself as http 23425 and https 23424.
You should have http 23424 (external port) and https 23524 (External secure port) - change the ports to these values in your Serviio console and Save. You should then get both checks in the console green. Then try to use the skill again.
jared69sib wrote:zip wrote:I can still see your server identifying itself as http 23425 and https 23424.
You should have http 23424 (external port) and https 23524 (External secure port) - change the ports to these values in your Serviio console and Save. You should then get both checks in the console green. Then try to use the skill again.
I actually had extra ports open in the same range existing from an older server running a separate serviio server that I am not even using anymore...I think that might have been causing some confusion... I don't know.. I tried what you said above, and I'm only getting one check for secure 23424, not http 23425... I will remove all extra port forwarding now that might be causing confusion during you scans...
jared69sib wrote:jared69sib wrote:zip wrote:I can still see your server identifying itself as http 23425 and https 23424.
You should have http 23424 (external port) and https 23524 (External secure port) - change the ports to these values in your Serviio console and Save. You should then get both checks in the console green. Then try to use the skill again.
I actually had extra ports open in the same range existing from an older server running a separate serviio server that I am not even using anymore...I think that might have been causing some confusion... I don't know.. I tried what you said above, and I'm only getting one check for secure 23424, not http 23425... I will remove all extra port forwarding now that might be causing confusion during you scans...
Ok. Somehow that helped. I guess it was either my router or how you're scanning ports... I changed the secure port back to 23524 and got check marks on both. It actually linked. Thanks for your help.
Now I'm trying to get Alexa to respond to the "ask serviio" trigger and to scan and rename the dlna devices. From what I read somewhere, you cannot control the echo devices?? I don't see them on the device list in the serviio console status tab....
zip wrote:Do you pronounce Serviio correctly? https://www.youtube.com/watch?v=U1EPAyJ7ltk
jared69sib wrote:zip wrote:Do you pronounce Serviio correctly? https://www.youtube.com/watch?v=U1EPAyJ7ltk
Yes. Serv-ee-oh. I even tried using your voice several times, and nothing.....I actually relinked it, and "Alexa, open serviio" is working. BUT...after a few tries, she don't ackknowledge the serviio "Alexa, open serviio" trigger anymore...
Also, is there anyway to add Serviio as a music service in the Alexa app like pandora, tunein, and amazon music? Then we can control it without speaking. I'm going to have to look into RESTful Web Services and see if there is anyway I can help out.
jared69sib wrote:"Alexa, open Serviio", still isn't working after a couple rare times here and there. Same from other Echo units.
zip wrote:(not to self - next time pick easier product name )
zip wrote:jared69sib wrote:"Alexa, open Serviio", still isn't working after a couple rare times here and there. Same from other Echo units.
As in - no response from the Echo? Or do you hear an error message response? If the former, there's nothing I can do - probably the device / Alexa not properly picking out your voice or the Serviio pronounciation (not to self - next time pick easier product name )
I'm looking into the option to play content on the devices themselves, but it involves more cloud infrastructure - so there is cost involved. Will see how that goes.
Return to Serviio Support & Help
Users browsing this forum: No registered users and 48 guests