Read the statement by Michael Teeuw here.
AlexaPi
-
@davidrq7 This mean you have already an instance of alexaPi running. reboot or kill the already running alexapi
-
Y, but even when i stop alexa service and start it again it looks all the same. Any sugestions? :) im getting closer to the end ^^
-
This post is deleted! -
@johnnyboy i’ll check this tomorrow by using sudo netstat -lnptu to check which application is blocking 5055 or 5050 port
-
This post is deleted! -
i had errors installing the current version 1.5, so I reverted back to v1.4 which is much more stable. this is the version that I am currently running flawlessly.
cd /opt/AlexaPi sudo git checkout v1.4I hope this helps
-
This post is deleted! -
This is what i got when i used netstat. Dont know what should i do next?
Edit: Allright i found something. sudo nano /etc/opt/AlexaPi/config.yaml at bottom is a line with numer 5055 so i change it for 5050. Diging more …;)
-
Found another intresting thing at forum.
“I’m expecting there’s a significance in which user is starting AlexaPi.
The service is started by user alexapi, but when you start it from the terminal, with “sudo”, you’re starting it as root.”
How can i use it? In super newbie … -
@davidrq7 Wait, are you still on your connexion issue ? Or it’s a sound issue ? Because the user might be an issue for the sound, but it’s unlickly to be an issue for the connexion
