Read the statement by Michael Teeuw here.
MMM-MirrorMirrorOnTheWall - Alexa voice control to hide/show modules and display text/images
-
Hi,
I’ve succeeded in succesfully linking Alexa to the smart mirror. When I issue a command, the mirror responds automatically. It has automatic wake word detection, audio feedback, automatic authentication using a refresh token, connection through a mirror interface. In the background it uses Alexa Skills kit and DynamoDB to make the communication happen. Read about it on my blog :
[http://smartmirrorprojectblog.wordpress.com/](link url)
Go ahead and follow the blog to find out on the progression and further development.Tips and suggestions welcome of course.
-
@bartalluyn really nice work! but since you have to change the Alexa Java client app to get it to work, it wouldn’t work for our application, since we need to get it to work with off-the-shelf Alexa or Alexa Echo. Right now my Alexa skill can only be used by one user, so I’m thinking about how to get it to work with multiple users so I can publish this skill, so people don’t need to worry about setting up Lambda and Alexa skill.
-
@joanaz That’s indeed something that wouldn’t work in that case.
It sounds like you would need something like account linking. What if the smart mirror would publish a service that takes and gives account credentials to hook on using the account linking functionality of a custom skill?
Thinking out of the box right now?
Also, suppose it works. When people start to install your module, and use your skill, your 1 million free lambda calls might expire sooner than you think? That’s one of the reasons why I’m not considering putting any of my skills out there. -
well just went through the whole thing again she still says there was a problem with the requested skills response and when i type hello into the service simulator the output is
The remote endpoint could not be called, or the response it returned was invalid. -
this is in the logs
START RequestId: cc7bfdd1-ebfd-11e6-8d16-b56e041c9162 Version: $LATEST
23:49:57
Unable to import module ‘index’: Error at Function.Module._resolveFilename (module.js:325:15) at Function.Module._load (module.js:276:25) at Module.require (module.js:353:17) at require (internal/module.js:12:17) at Object. (/var/task/index.js:23:14) at Module._compile (module.js:409:26) at Object.Module._extensions…js (module.js:416:10) at Module.load (
23:49:58
2017-02-05T23:49:58.043Z cc7bfdd1-ebfd-11e6-8d16-b56e041c9162 connect -
@joanaz Hi, when i zip all those files and folders up and try to upload them to Lambda i get "The deployment package of your Lambda function “xxxxxxxxx” is too large to enable inline code editing. However, you can still invoke your function right now. any ideas - it’s driving me mad. I thought it must be that i shouldn’t include the node_modules folder - can you confirm exactly what should be in the zip. Thanks
-
@Gunwoody you should definitely include node_modules, but my zip file is 5.1MB, I think the limit is 50MB. it’s not an error, you can ignore it.
-
@joanaz Hi - thanks for the super quick reply :). Yes, my zip is also 5.1mb. I’ve tried several times but still get the same message.
“The deployment package of your Lambda function “xxxxxxxxxxx” is too large to enable inline code editing. However, you can still invoke your function right now.”
You say i can ignore it - but how do i know if the zip has uploaded ok?
-
@Gunwoody it says you can invoke your function right now. if it’s not ok, it would give you a red error message. Anyways, you can click on the test button, see whether your function works. but before that, you need to setup a test case
-
@joanaz Thanks again. I think it’s uploaded ok - not that it’s helped me get it working. I can get just about any other module running on MagicMirror but not this one. I think it’s just a case of i’m not sure what folders should be where. When i run it with the module in the config file i just get a white screen and can’t ‘alt’ out of it - Pi seems to crash. I think i’ll just have to give up as i’ve been trying for 3 days to get this running :(
