2019-02-28, 22:24
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
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
