+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Supplementary Tools for Kodi (https://forum.kodi.tv/forumdisplay.php?fid=116)
+--- Thread: Release Kanzi: Amazon Alexa skill for Kodi (/showthread.php?tid=254502)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
RE: Amazon Echo skill for Kodi - CaptainMoody - 2016-11-03
Checked every setting and all i get when testing commands is:
"The remote endpoint could not be called, or the response it returned was invalid."
I realised my home automation software was running https on 443 so changed that but it's still not working.
Is there a way to test the endpoint address? What should I get if I put it directly into a browser? At the moment I only get "This site can't be reached"
RE: Amazon Echo skill for Kodi - jingai - 2016-11-03
If you point a web browser at the endpoint, you should get HTTP 502 (No content) and a blank page.
RE: Amazon Echo skill for Kodi - Jagsta - 2016-11-03
(2016-11-03, 18:24)jingai Wrote: FWIW, for me at least, it's not as cumbersome as you might be imagining. Unless you're just playing around with it, you're likely to issue only one or two commands for each video you watch.
Yeah I agree with this, I don't use Kodi as a PVR which might be an example of when it could be useful for flicking channels I guess. In general I am just issuing a single command, watching a particular movie, tv show or album.
(2016-11-03, 18:24)jingai Wrote: @Jagsta, you could pretty easily modify the skill if you wanted to play around with keeping the session open. I think you'll find that the misfire rate is pretty high though unless you're the only one in the room.. so it's unlikely we'd make this default behavior even if we ever did support it.
I agree that it's likely to be very hit and miss holding a session open for arbitrary additional commands when there's background noise/dialog, besides which you'll be streaming your audio to Amazon for the whole period it's in this state! I might have a play with it for the use cases I can think of for which a multi-stage conversation would be desirable.
RE: Amazon Echo skill for Kodi - jingai - 2016-11-03
For what it's worth, I intend to add proper session support at some point, because I think the power commands should ask for confirmation before executing.
I had planned at this point to think through possible use cases for conversations. I've got so much going on right now and I'm the type of person that once I get to thinking about a problem.. it's hard to not just execute it.. so I tend to keep notes and push it out of my head until I have time to really think it through properly and completely
RE: Amazon Echo skill for Kodi - layzzzee8 - 2016-11-03
Ok first off I want to say thank you for creating this and putting it out there for everyone. I have gotten everything set up with Heroku but I am trying to migrate it to AWS. I am getting the alexa response: "error parsing results" When I check the Amazon logs I see: "sending request to http://None:/xxx.xxxx.xxx:8080/None/jsonrpc" xxxx being my DDNS address. I am assuming the http://None:/ and None/jsonrpc parts of the request are causing my issue. Does anyone know what could be causing this issue?
RE: Amazon Echo skill for Kodi - jingai - 2016-11-03
Did you uncomment the SCHEME and SUBPATH variables in your env file and leave them empty?
RE: Amazon Echo skill for Kodi - layzzzee8 - 2016-11-03
(2016-11-03, 21:47)jingai Wrote: Did you uncomment the SCHEME and SUBPATH variables in your env file and leave them empty?
They are commented out. I never touched them.
RE: Amazon Echo skill for Kodi - jingai - 2016-11-03
Might need to pull KODI_SCHEME and KODI_SUBPATH out of LAMBDA_ENV_VARS.. not totally sure, as I don't use Lambda myself. But it's worth a try.
RE: Amazon Echo skill for Kodi - layzzzee8 - 2016-11-03
(2016-11-03, 22:04)jingai Wrote: Might need to pull KODI_SCHEME and KODI_SUBPATH out of LAMBDA_ENV_VARS.. not totally sure, as I don't use Lambda myself. But it's worth a try.
That was it!!!! Thanks!!!
RE: Amazon Echo skill for Kodi - layzzzee8 - 2016-11-03
Now, am I correct that any new movies or shows I add to my database I have to add them to the custom slots for the Alexa Skill? That is so annoying if that is the case.
RE: Amazon Echo skill for Kodi - jingai - 2016-11-03
(2016-11-03, 22:20)layzzzee8 Wrote: Now, am I correct that any new movies or shows I add to my database I have to add them to the custom slots for the Alexa Skill? That is so annoying if that is the case.
No, you are not correct. It helps, but isn't required.
Basically, if you notice that it has trouble matching something, try running the slot generator again.
RE: Amazon Echo skill for Kodi - layzzzee8 - 2016-11-03
(2016-11-03, 22:48)jingai Wrote:(2016-11-03, 22:20)layzzzee8 Wrote: Now, am I correct that any new movies or shows I add to my database I have to add them to the custom slots for the Alexa Skill? That is so annoying if that is the case.
No, you are not correct. It helps, but isn't required.
Basically, if you notice that it has trouble matching something, try running the slot generator again.
Oh. Nice! Does anyone know if AWS Lambda is free for 1 million requests per month forever or is it a trial that expires?
RE: Amazon Echo skill for Kodi - E-Pro - 2016-11-04
Noob here.
Just wanted to relay what I learned today. I carefully followed all of m0ngr31's setup instructions (using heroku) to no avail. Frustrated after 2 days of tinkering, troubleshooting, and reading through threads like this, I cracked a beer, decided to take a look at my heroku app logs one last time before scrapping the whole thing and BAM, there was my mistake.
app[web.1]: Sending request to http://http://mysupersecretddnsname:8080/jsonrpc
Edited my heroku app config, removing "http://" from my DDNS listing in the KODI_ADDRESS field and VOILA!
I feel like an idiot, but Alexa commands work perfectly now.
RE: Amazon Echo skill for Kodi - jingai - 2016-11-04
(2016-11-03, 22:19)layzzzee8 Wrote:(2016-11-03, 22:04)jingai Wrote: Might need to pull KODI_SCHEME and KODI_SUBPATH out of LAMBDA_ENV_VARS.. not totally sure, as I don't use Lambda myself. But it's worth a try.
That was it!!!! Thanks!!!
This should be fixed by the way, if anyone with a Lambda deployment would care to test it.
RE: Amazon Echo skill for Kodi - BDPNA - 2016-11-04
I can't thank you guys enough who work on this. This is so much fun to use!!! I got my second room working and it was a lot faster than the first.
Dumb question -- I assume if I want the echo to learn all the new shows and movies I have, I need to manually update the SLOTS often? They are only as good as when I loaded them?