Release Kanzi: Amazon Alexa skill for Kodi - Printable Version +- 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 - blazeburna - 2017-07-23 @safesinger, open a command window in your kodi-alexa-master folder and run the following commands: venv\Scripts\activate.bat zappa init zappa update dev Your URL will be at the bottom. RE: Amazon Echo skill for Kodi - blazeburna - 2017-07-23 (2017-07-21, 18:30)psinide Wrote: Also, is there way to search movies from an add-on from alexa? I found a decent guide on youtube for adding a load of movie links to your library. This will make good use of this new echo skill. Just search 'you will love kodi 17 after this' on the tube. RE: Amazon Echo skill for Kodi - jingai - 2017-07-23 (2017-07-23, 03:22)grimmace92 Wrote:(2017-07-20, 05:09)jingai Wrote:Thanks. I'm up and running and everything works but I have questions about multiple instances of Kodi. So I have three different htpc's with its own install of kodi that share an sql database. I have two dots. One dot will control two of the htpc's and the other dot will control 1 htpc. Do I need to run through the entire setup on each machine?(2017-07-20, 01:51)grimmace92 Wrote: I'm already using another application that uses the remote control kodi via http on port 8080. Will that be an issue if I try to use the Alexa skill?Nope, it'll be fine. The skill is set up to link one Echo device to one instance of Kodi. If you need one Echo device to control more than one Kodi installation, you will need another copy of the skill for each instance. RE: Amazon Echo skill for Kodi - jingai - 2017-07-23 (2017-07-23, 02:36)blazeburna Wrote: @jingai, I edited the config file, but I am still getting the error. Edited config below: Your config file is named kodi.config, right? RE: Amazon Echo skill for Kodi - blazeburna - 2017-07-23 (2017-07-23, 04:22)jingai Wrote:I decided to start completely from scratch and as another user suggested, I moved the kodi-alexa folder out of my C: drive (windows 10). Happy to report everything is working well. Thanks for all the support.(2017-07-23, 02:36)blazeburna Wrote: @jingai, I edited the config file, but I am still getting the error. RE: Amazon Echo skill for Kodi - 8osman - 2017-07-23 This sounds exactly like the problem I am having, I'll try building it all in d:\ on Windows and run it from there. Sounds like the guide might need an update? For win10 users. RE: Amazon Echo skill for Kodi - blazeburna - 2017-07-23 (2017-07-23, 10:20)8osman Wrote: This sounds exactly like the problem I am having, I'll try building it all in d:\ on Windows and run it from there. Sounds like the guide might need an update? For win10 users. Hope it works out for you. I also got this up and running smoothly on 2 other kodi instances using the same alexa device. I have an Amazon Tap and I have kodi setup in three different rooms (study, living room, bedroom). No matter what room I'm in, as long as I have my Tap, I just have to invoke the kodi instance I want (ask bedroom kodi, or ask my computer). It works flawlessly every time. It was a bit tedious to setup, as I had to make 3 separate kodi-alexa folders and create separate alexa skills for each instance, but it was definitely worth it. I tested it out today and within seconds had 3 different shows running on 3 different machines and I didn't have to push a single button. I'll be buying the creator of this app some coffee, he definitely deserves it. RE: Amazon Echo skill for Kodi - grimmace92 - 2017-07-23 (2017-07-23, 04:16)jingai Wrote:(2017-07-23, 03:22)grimmace92 Wrote:(2017-07-20, 05:09)jingai Wrote: Nope, it'll be fine.Thanks. I'm up and running and everything works but I have questions about multiple instances of Kodi. So I have three different htpc's with its own install of kodi that share an sql database. I have two dots. One dot will control two of the htpc's and the other dot will control 1 htpc. Do I need to run through the entire setup on each machine? Ok Thanks. Do you have to keep Kodi running for the skill to stay active? I came back to it this morning and Alexa was giving me a problem. I ran zappa update dev and its working again. Is there a setting to keep it active that I'm missing? RE: Amazon Echo skill for Kodi - safesinger - 2017-07-23 (2017-07-23, 03:30)blazeburna Wrote: @safesinger, open a command window in your kodi-alexa-master folder and run the following commands: Thank you so much! I greatly appreciate it:-) RE: Amazon Echo skill for Kodi - jingai - 2017-07-23 (2017-07-23, 13:45)grimmace92 Wrote: Ok Thanks. Do you have to keep Kodi running for the skill to stay active? I came back to it this morning and Alexa was giving me a problem. I ran zappa update dev and its working again. Is there a setting to keep it active that I'm missing? The skill doesn't really "stay active." It only runs when you issue a request. Kodi doesn't have to be running, but obviously most commands will fail if it's not. RE: Amazon Echo skill for Kodi - jingai - 2017-07-23 Guys, I really don't think it matters where you build the skill -- I think you probably just did something wrong the first time you built it on your C: drive. RE: Amazon Echo skill for Kodi - blazeburna - 2017-07-23 (2017-07-23, 18:22)jingai Wrote: Guys, I really don't think it matters where you build the skill -- I think you probably just did something wrong the first time you built it on your C: drive. I'm willing to admit when I'm wrong. @jingai is correct, it does not matter where you build the skill. Following the official guide from GitHub, these are the exact commands I used to deploy the skill on windows 10. First I opened a command window inside my 'Documents' folder by holding 'Ctrl' + 'Shift', right-clicking in an open space and selecting open command window here. Then I ran the following commands exactly as written: Code: C:\Python27\Scripts\pip.exe install awscli Leaving the command window open, I then I downloaded the 'kodi.config' file from the official guide into the 'kodi-alexa' folder that was cloned from git. I opened the file with 'Notepad++' , made my changes per the official guide, then click 'file' , 'save as' , changed 'file type' to 'all types' and saved. Then deleted the original text file, leaving the only the .config file. I then went back to the command window and ran the command: Code: zappa init Within zappa, I changed the name from 'dev' to 'lap' to name the skill for my laptop Then I accepted the remaining defaults Then I ran the command: Code: zappa deploy lap Followed the official guide to the tee after that. Correctly getting through this portion was my problem. The upside is I can get this done very quickly now. RE: Amazon Echo skill for Kodi - digiltd - 2017-07-25 After seeing all the zappa commands in recent posts, i thought some input into what they actually do might help people understand what is happening when they are copy and pasting these commands What the commands do zappa init is what you run very first time you set up the Skill, it generates a zappa_settings.json file which is used to deploy and update the Skill.. zappa deploy dev deploys the Skill onto AWS It packages all the dependencies and the Skill code, uploads them to AWS, sets up the Lambda ("virtual computer" that runs the code), creates an API gateway it uses to talk to Alexa, starts timers that trigger the Skill to keep it awake and other zappa specific tasks. Once it is deployed it is gonna be running on AWS constantly. Zappa uses a "keep warm" trigger that will automatically ping the skill every 4 minutes to keep the "virtual computer" awake. Your log will be a constant stream of four lines every four minutes, 24/7 forever. If you have been running `zappa init` and `zappa deploy` multiple times from different locations you might have a lot of versions of the Skill running on your AWS account that will never be used but are constantly running. It very important to "zappa undeploy dev" when you want to completely remove the Skill from AWS and start again. Unfortunately you can only undeploy from the folder it was deployed from (it needs the zappa_settings.json folder to know what to remove) so if you have deleted the folder then you will have clean up AWS manually (see https://forum.kodi.tv/showthread.php?tid=254502&pid=2604223#pid2604223). It is not the end of the world, but worth being aware of as it can cause problems. zappa update dev updates the Skill you have already deployed, putting everything in the right place and cleaning up after itself As long as you are working in the same folder you deployed it from (hint: it will have a zappa_settings.json file in it) and have activated the virtualenv, then zappa will know what to do. Put into practice When you first set up the Skill i.e. you have done everything the readme file you have been carefully following has told you to do (including activating your virtualenv (which is different depending on the platform you are working on)) you run: Code: pip install -r requirements.txt The first line downloads dependencies required by the kodi-alexa Skill, the second installs a dependency required by zappa, and the third installs zappa itself. The reason they are added separately and not simply included in the requirements.txt file is because they are not needed if installing on Heroku or anywhere else. You only need them for deploying to AWS. When you make a change to your kodi.config file (make the change and save the file (obviously)) then providing your virtualenv is activated, run Code: zappa update dev The https endpoint it spits out will the same that it originally created, so you don't need to change this in the amazon developer console. Updating the Skill to a new version see UPGRADING.md for details on how to do actually update the Skill it is assumed you have already updated the Skill to your local machine, now you want to push it to AWS Code: pip install -r requirements.txt First line: fetch and install any new versions of the dependencies used by the Skill (this is especially important as most of the "magic" in this Skill happens in one of those dependencies) Second line: zappa updates the Skill you have already deployed, putting everything in the right place and cleaning up after itself notes:
Hopefully that sheds a little light on the differences between the init, deploy and update commands for zappa. RE: Amazon Echo skill for Kodi - jingai - 2017-07-25 New release -- changes: v2.7.5 (07/25/2017)
When updating the skill for this release, it is highly recommended to regenerate your slot items too. RE: Amazon Echo skill for Kodi - grimmace92 - 2017-07-26 (2017-07-25, 07:25)jingai Wrote: New release -- changes: Library views works well. Are you taking requests for additional features? |