•   
  • 1
  • 164
  • 165
  • 166
  • 167
  • 168(current)
Release -  Kanzi: Amazon Alexa skill for Kodi
Update
Create mLab account and database
fill out codi config
uri mongodb
user/pass mongo db mongo db
proxy use =yes
Music warning =Yes
seems to koko alexa connected when i try to "alexa ask koko to play musik" answer "party mode playing" ore somthing but no sound on echo dot
Noch One who can Help ??
url from developer console looks like "https://proxy.lexigr.am/proxy?file=http://xxxxxx:[email protected]:8080/vfs//storage/music/Falco/Greatest Hits/02 Der Kommissar.mp3"
when put this into the firefox browser i get "Unauthorized"
Image
Reply
I can only call that way
Question: Alexa ask koko play song xyz
Answer Playing xyz
But no music on Alexa

Who can help me here ?

Cloudwatch log:https://paste.kodi.tv/acebitetin
Cloudwatch error
Reply
json Input
jsonInput
Reply
log json output
jsonOutput
Reply
You haven't stated but it's obvious that you've set up an alternate reverse-proxy server for your Kodi box.  I suspect that either it's not working properly or your Kodi box isn't wholly configured for remote access.  To check both, copy the entire URL from the output JSON you've posted and paste it into a browser.  If both are working, depending on your browser, either the song file should download or play on your computer.  If neither occurs, either the reverse proxy isn't working or Kodi isn't set up right to respond to rpc calls.

A couple of other points.  How have you set up authentication of your reverse proxy?  If it's name/password, which are you passing in your kodi.config file?  Have you looked at your kodi box setup to make sure that it's set up properly? so that it will include the kodi box username and password?  The URL you show passes the username and password to your reverse proxy, not to kodi.  You'll need to have your reverse proxy configured so that it will pass kodi's name and password on to the kodi box. UR

Another check:  Try accessing kodi's Chorus2 web interface by putting the reverse proxy URL and port into a browser, including name:[email protected] before the URL.  Does Chorus2 start?  If not, try putting the kodi box URL into the browser.  If it starts directly but not through the reverse proxy, you have a reverse proxy problem.  If the reverse proxy asks for name and password, it's not configured properly.

One other point.  If all of this works, try playing a song from the Chorus2 web interface in "local" rather than "kodi" mode.   Does the song play?  If the song seems to start but not play, and the song time counter stays at zero, it's likely there's a problem in the "sources.xml" file of your kodi box.  A direct reference to your music files needs to be included in the   "music" section of the sources files, as I show from my own (Raspberry pi) kodi box exemplies:

 <music>
        <default pathversion="1"></default>
        <source>
            <name>pi</name>
            <path pathversion="1">/media/pi/</path>
            <allowsharing>true</allowsharing>
        </source>
    </music>

RodinME
Reply
This is a reply to MichiKrem's 1/29 original question.  I noticed in your posting of the kodi.config file that you don't name an S3 or OwnCloud bucket for cache storage of Kodi library information.  If it's true that you haven't done either, this could be your problem.  In order for Alexa Kodi/Kanzi or Koko to work, Alexa needs to obtain information from your Kodi library.  In the absence of the cache, in which Kanzi/Koko will build various pieces of your library for rapid access, Kanzi/Koko must get them each time from the Kodi box.  This may be causing Kanzi/Koko timeouts.

You will need to set up the bucket ahead of time using either AWS S3, or your own internet-reachable cache.  If using AWS S3, you'll also need to use AWS IAM to set up Kodi user credentials.  In either case, Kanzi/Koko will populate the cache over time with JSON data identifying the URI's of your Kodi's media files
which will be added to the JSON RPG calls to your Kodi media libraries.

RodinME
Reply
Thanks @RodinMe Your observation that Kanzi was using the user:[email protected] url format seems to have shed light on why I have an apparently working HTTPS to HTTP reverse proxy enabling access to the Kodi web-server, and yet Kanzi doesn't see it. Configured to use HTTP everything is working great, but I'd really rather be using HTTPS.

Does anybody know how to configure HA-Proxy under pfSense to pass such a user:password pair to an HTTP backend? Seems like really basic functionality, but I've yet to find out how to configure this.

Thanks,

Steve
Reply
  •   
  • 1
  • 164
  • 165
  • 166
  • 167
  • 168(current)
 
Thread Rating:
  • 15 Vote(s) - 4.6 Average



Logout Mark Read Team Forum Stats Members Help
Kanzi: Amazon Alexa skill for Kodi4.615