Read the statement by Michael Teeuw here.
Alexa Goes Handsfree!
-
I’ve jsut set up an Amazon dev account and installing the Alexa pi code to have a play with.
During the install, I see
Configuration file ‘/etc/lightdm/lightdm.conf’
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer’s version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** lightdm.conf (Y/I/N/O/D/Z) [default=N] ?I think I should answer ‘Y’ to keep the installer happy, but thought it worth checking - @d3r can I ask what you chose?
-
@darrene I would say press D to see what the difference is then you’ll have a better idea on how to proceed.
Edit:
I just ran an update on my pi and got the same prompt. lightdm is a display manager and not directly related to alexa.
https://wiki.debian.org/LightDM -
Ah, thtat’s great. Thanks @d3r.
All good now -
@darrene Nice. Alexa is working now?
-
@d3r not quite - I’m almost there but trying to login to my AWS mirror profile after authorising it and I’m failing their ridiculous ‘type the characters you see in this image’ challenge :)
Edit: At last! through…
-
It’s awesome :)
I’ve had Alexa tell me the day, a joke and asked her a maths question.
The detection is spot on and the response time is pretty acceptable
The sooner this can get made into a module the better :)
-
The changes to the lightdm config file is probably what it’s warning you about. Remember during the MM installation, you should’ve edited that file to turn off the screen blanking. So you should always do a comparison between what your file looks like and what the vendor is releasing and apply the changes as needed.
-
That’s what it was. Thanks @KirAsh4!
-
Didn’t look into this very much, so maybe one of you can answer this: is it possible to let Alexa execute commands or code? So we can incorporate it into MagicMirror²?
-
I don’t think it can from what I’ve seen @MichMich - I could be wrong, but it isn’t obvious that it could.
Running the Alexa sample requires 3 terminal sessions -
one runs the companion service which stores the application token information and runs a listener on port 3000
one runs the java client under maven
One runs the wake word agent, running one of two engines - kitt_ai or sensory (I opted for kitt_ai)I can’t tell at the moment, what information is returned by AVS, so it’s difficult to know if and how usable it is. It does support IFTTT however. Combining it with the MMM-IFTTT module, whilst not elegant, may be a workaround?
For what it’s worth, the install, whilst lengthy was fully automated and incredibly trouble free - it worked straight out of the box on a fresh Raspian install which already had a barebones MagicMirror2 install.
Also of note, every time I need to restart the java client, I am required to re-authenticate my device to get a new bearer/autentication token. These tokens do not seem to last that long and the authentication process involves logging into Amazon through a web page with an image security verification. No doubt that’s down to how this sample is implemented but might be worth knowing about
