-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outdated .json and to less Information in readme #5
Comments
I am also struggeling with the installation of this skill? Have you tried testing the skill in the alexa developer console? |
Ok... I could get it to work somehow (not everything works perfectly... however, I tested basic things and they seem to work) Have a look at my fork. There you will find a correct json for an interaction model (similar to yours above but without the intent named "Calexa") |
Hi all, 127.0.0.1 - - [25/Jul/2018 10:30:25] "POST / HTTP/1.1" 400 - I'm using the fork of @nikolauskrismer Thanks in advance. |
No... I did not experience that problem. BTW: |
I tried testing it with the amazon console. the return is an empty body: the console shows the above mentioned HTTP requests and status codes. |
Same here, I've also tried the fork from nikolauskrismer.
Alexa Console returns:
|
Same issue here. @nikolauskrismer do you also get the status code 400 line in the console? |
No... not that I remember |
What are you asking exactly? I always get either an error message or the message that there is nothing in my calendar. |
Hi, can I take as correct setup all of these settings? Thanks |
It looks like this conversation was years ago. I was really looking forward to setting this up on apache as well. Thanks for the comments everyone posted and shared. I hope someone comments more on a resolution here. @Garfonso @nikolauskrismer @Phil-Rei . This would be amazing to get working!! |
Yes, I agree |
Hi, I try to use this repository and confirm it works. I made some changes to use with docker and put code here https://git.cdp.li/polcape/calexa |
@polcape thanks for confirming. I do not have docker but I will try following their instructions on this repo and see if it works. I will only have apache. If you have any comments on problems you had to deal with please let me know. |
I never got it working... 🙁 Would like to try again. Will see with your setup. |
Hi @gstlouisgit , the only thinghs/problems I found was:
The docker image is based on python 3.6 in requirements.txt you find the compatible packages to install. Also pay attention to use ssl connection or ngrock |
Hi, today I tried to setup your docker. It does not work, I get the following error after the container build and it tried to start:
Could you have a look what is wrong with the container @polcape ? Did you get it to work @gstlouisgit? Any help would be appreciated. Thanks. //Edit:
It seeems flask currently is completely broken... it's sad that you did not publish your container... :-( Ok, after fidling a bit, it now works with falsk<2 requirement. Not sure I like that... |
Hi,
first of all I want to thank Martin Riedl for sharing his code.
I've tried to install it on my system and had several problems, but got pretty far (I guess almost 99%).
My System: Xubuntu 16.04, OwnCloud 10.0.8, Apache 2, Cert via Let's Encrypt
Step one: Alexa Skill on Amazon Dev:
It seems Amazon changed their syntax some time ago. The provided .json is not accepted as it is. I've transformed it to the following which already includes all speech_assets and customSlotTypes... So you basically only need to paste the .json and don't need to add these things manually any more.
Step two: Running calexa.py on same server
I've Downloaded calexa.py and conf/config.json
In the config I'm not sure the URL has to be
https://domain.de/remote.php/dav/calendars/USERNAME/default/
or
https://domain.de/remote.php/dav/principals/users/USERNAME/
So I've tried both (first is my default calendar, second one are all of my calendars).
I've also installed the dependencies via:
When I run python calexa.py this is the output:
So it seems to run. I've ignored the warning cause it only seems to be a speed issue.
Using a local Browser on http://127.0.0.1:5000 I get this:
Since there is no parameter I've expected some error at least.
Calexa.py Output in console add's the following line:
127.0.0.1 - - [25/Jul/2018 10:15:56] "GET / HTTP/1.1" 405 -
Step three: Reach Calexa fom outside
Activated proxy module for Apache
VirtualHosts:
Of course Port 433 has NAT forwarding to my server. I'm now able to access from outside, getting the same Method Not Allowed message.
Endpoint in Amazon Dev is: https://domain.de
This is what I get when I try to open Calexa with my Echo Dot. (Alexa starte Calexa)
I can see the requests reaching calexa.py as it outputs the following:
So it seems I'm almost done. Maybe my conversion of the .json is not correct or the calexa.py is configured wrong. Maybe someone can help and hopefully I can help others with my detailed descriptions.
The text was updated successfully, but these errors were encountered: