1. choosing “2” for KODI as invocation name
   
2. URL for Skill server: https://xxxxx.ddns.net:8000/
   

Quote:Q: I don’t want to use Lamda but it seems that the scripts wants to publish something with lamda function, is my configuration wrong?
Second and most important:: How can I solve this issue?
A view posts ago, I read about substitution URI with sourceDir in kanzi/skill.json but when I restart deploy process I guess the skill.json will be generated again and my changes will be overwritten, right?

(2018-05-04, 23:39)tkislan Wrote: I’m just gonna drop this here for anyone that wants a solution that just works.

Amazon Echo Alexa Video Skill for Kodi
https://github.com/kodi-connect/kodi-alexa-video/blob/master/readme.md

(2018-05-05, 00:41)Paranoid247 Wrote: Cheers that sorted it.
When I installed kodi-voice that automatically installed the latest version of cryptography and I didn't spot that the requirement was for a specific version.

Next problem.

I'm talking to kodi and requests such as "Ask Kanzi to open music" or "Play all Music" work, but when I ask it to play something specific I get the "there was a problem with the requested skill response" (500 server error). Here are the relevant logs:

 [2018-05-04 23:22:30,891] ERROR in app: Exception on / [POST]
 Traceback (most recent call last):
   File "/srv/www/htdocs/Kanzi/flask/app.py", line 1982, in wsgi_app
     response = self.full_dispatch_request()
   File "/srv/www/htdocs/Kanzi/flask/app.py", line 1614, in full_dispatch_request
     rv = self.handle_user_exception(e)
   File "/srv/www/htdocs/Kanzi/flask/app.py", line 1517, in handle_user_exception
     reraise(exc_type, exc_value, tb)
   File "/srv/www/htdocs/Kanzi/flask/app.py", line 1612, in full_dispatch_request
     rv = self.dispatch_request()
   File "/srv/www/htdocs/Kanzi/flask/app.py", line 1598, in dispatch_request
     return self.view_functions[rule.endpoint](**req.view_args)
   File "/srv/www/htdocs/Kanzi/flask_ask/core.py", line 767, in _flask_view_func
     result = self._map_intent_to_view_func(self.request.intent)()
   File "/srv/www/htdocs/Kanzi/alexa.py", line 74, in decorated_function
     kodi = Kodi(config, context)
   File "/srv/www/htdocs/Kanzi/kodi_voice/kodi.py", line 387, in __init__
     if not self.scheme or not self.address or not self.port or not self.username or not self.password:
 AttributeError: Kodi instance has no attribute 'password'


Any ideas?

(2018-05-05, 02:24)drizzt09 Wrote: where does init-config get downloaded when running:
C:\WINDOWS\system32>lexigram init-config

(2018-05-05, 01:38)Paranoid247 Wrote: Here's some logs from Alexa.
Alexa heard: "ask kodi to play all music"  - Party Mode - Starting party play
Alexa heard: "ask kodi to skip" - Playing next item
Alexa heard: "ask kodi to start over" - Starting current item over
Alexa heard: "ask kodi to pause" - Play/Pause
Alexa heard: "ask kodi to go back" - Skill response was marked as failure - The skill responded with 500 HTTP status code
Alexa heard: "ask kodi to stop" - Stopping playback - Playback stopped
Alexa heard: "ask kodi to" - Skill response was marked as failure - The skill responded with 500 HTTP status code
Alexa heard: "ask kodi what's playing" - Skill response was marked as failure - The skill responded with 500 HTTP status code

The "go back" command caused kodi to go back in the menu's rather than the playlist. Is it configured for a specific skin?
Tomorrow I'll snoop the communications between kodi and the host and see if can spot anything obvious.

(Kodi version 17.6., OSMC 2018-04-1, Skin Confluence 3.1.43)

(2018-05-04, 18:32)m0ngr31 Wrote:

Quote:Q: I don’t want to use Lamda but it seems that the scripts wants to publish something with lamda function, is my configuration wrong?
Second and most important:: How can I solve this issue?
A view posts ago, I read about substitution URI with sourceDir in kanzi/skill.json but when I restart deploy process I guess the skill.json will be generated again and my changes will be overwritten, right?

Amazon's error messages for this are pretty lame. They don't always seem to point to the correct thing. My best guess is that it doesn't like adding a port to the URL. Try dropping the `:8000` and deploying again. I know it won't make the skill work, but it'll be interesting to see if that resolves the error.

If that doesn't work, we can try some other things. 

(2018-05-05, 07:43)area2051 Wrote: Thanks for your feedback!
dropping :8000 was not the answer - still the same issue. maybe it's something with my raspPi?  Anyhow I tried with Ubuntu and this works!
Anyhow - we should document that amazon only supports 443 ports! I guess this will remove some pain for user users

Thanks!!