Read the statement by Michael Teeuw here.
MMM-MirrorMirrorOnTheWall - Alexa voice control to hide/show modules and display text/images
-
@Gunwoody sorry to hear that. This is quite advanced as you have to setup AWS IoT, Lambda and Alexa skill, so it does need you to have some experiences with programming and using AWS services. I’m thinking about how to simplify this and get it to work with multiple users, but thanks for trying.
-
I do not get why this is not working the src.zip has a layout of folders and in the root of zip I have index.js MirrorMirror.js and package.json
but i still get
START RequestId: dbde411d-ecaa-11e6-8bd7-9b2096d559c7 Version: $LATEST 20:28:46 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 ( 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 (module.js:343:32) at Function.Module._load (module.js:300:12) at Module.require (module.js:353:17)which looks like what it’s not finding index.js ?
-
@joanaz I haven’t really had much of an issue with Lambda, IOT etc. It’s more the local install on the pi. I think because your instructions jump from area to area it’s easy to miss or misintrepet a step. I might just do a full clean install and start from scratch. It’s just a shame because MagicMirror itself runs perfectly with any module i try. It’s just your that is determined to thwart me lol :)
-
@zman3 you don’t have certs and node_modules?
-
@Gunwoody i’ve never seen another mirror module which works with a Alexa skill
-
yes i have those folders in the zip
-
For people struggling with setting up Lambda and Alexa Skill, here’s a good visual instructions for a different Skill. Use your judgment when dealing with differences with my skill.
https://github.com/alexa/skill-sample-nodejs-calendar-readerHere’s Amazon’s instructions for setting up a AWS IoT device, it’ll also be slightly different when you setup your own device, but it’s good enough.
http://docs.aws.amazon.com/iot/latest/developerguide/iot-console-signin.html
-
So exactly which files need to be in the zip?
And also, when testing on the lambda site I get an error about alexa-sdk not being detected… are there other steps for installation? I’ve hit a wall -
So redid everything. Same thing. When I test with my device and try to invoke it says there was a problem with the requested skills response…
-
@savage_gr1nd you need to include node_modules in the src folder. run ‘npm install’ inside src folder.
-
Yea I did that. Then made the zip. The zip was too large and my page kept crashing so I used s3. Or will that not work?
-
And one more thing I’m confused on and it might be why, when putting the path to certs to keys.json is it the FULL path /home etc…?
-
@savage_gr1nd the zip shouldn’t be too large, mine was 5.1MB. I’m not sure what you are saying about path to certs and keys.json. have a look of my folder structure
-
I figured out the path problem.
But every module ever is in my folder. Which are required so I can delete the rest. -
I’m sorry lol
More specific in my node_modules folder -
Okay I’m really sorry for bugging.
But literally got everything figured out except why my file is too large. I deleted node_modules and redid npm installs on all 4 dependencies. The node folder alone is 69mb…
How is yours 5.1mb…?Since mine is so big. The only error I get now in lambda is time out. I just don’t understand why mine is so large.
-
@Journeytojah did you ever get yours to work? That’s about the same error I was getting
-
@savage_gr1nd my node_modules is 24.2MB. How are you testing the lambda function? try something simple, like the hello intent first
-
@joanaz that’s what I was doing.
Also testing after uploading the code from the console.
After work I want to try npm depues to see if that helps.
But I also see you have latest define for the dependencies. What versions do you have installed so I can’t edit my package.json to install those smaller versions? -
@savage_gr1nd this is my npm list
├─┬ alexa-sdk@1.0.6 │ ├─┬ aws-sdk@2.9.0 │ │ ├─┬ buffer@4.9.1 │ │ │ ├── base64-js@1.2.0 │ │ │ ├── ieee754@1.1.8 │ │ │ └── isarray@1.0.0 │ │ ├── crypto-browserify@1.0.9 │ │ ├── jmespath@0.15.0 │ │ ├── querystring@0.2.0 │ │ ├── sax@1.1.5 │ │ ├─┬ url@0.10.3 │ │ │ └── punycode@1.3.2 │ │ ├── uuid@3.0.0 │ │ ├── xml2js@0.4.15 │ │ └─┬ xmlbuilder@2.6.2 │ │ └── lodash@3.5.0 │ ├── i18next@3.5.2 │ └── i18next-sprintf-postprocessor@0.2.2 ├─┬ aws-iot-device-sdk@1.0.14 │ ├── crypto-js@3.1.6 │ ├── minimist@1.2.0 │ ├─┬ mqtt@1.11.2 │ │ ├─┬ commist@1.0.0 │ │ │ └── leven@1.0.2 │ │ ├─┬ concat-stream@1.6.0 │ │ │ ├─┬ readable-stream@2.2.2 │ │ │ │ ├── buffer-shims@1.0.0 │ │ │ │ ├── process-nextick-args@1.0.7 │ │ │ │ └── util-deprecate@1.0.2 │ │ │ └── typedarray@0.0.6 │ │ ├─┬ end-of-stream@1.1.0 │ │ │ └─┬ once@1.3.3 │ │ │ └── wrappy@1.0.2 │ │ ├── help-me@0.1.0 │ │ ├── inherits@2.0.3 │ │ ├─┬ mqtt-connection@2.1.1 │ │ │ ├── reduplexer@1.1.0 │ │ │ └── through2@0.6.5 │ │ ├── mqtt-packet@3.4.7 │ │ ├── pump@1.0.2 │ │ ├─┬ readable-stream@1.0.34 │ │ │ ├── core-util-is@1.0.2 │ │ │ ├── isarray@0.0.1 │ │ │ └── string_decoder@0.10.31 │ │ ├── reinterval@1.1.0 │ │ ├─┬ split2@2.1.1 │ │ │ └─┬ through2@2.0.3 │ │ │ └── readable-stream@2.2.2 │ │ └── xtend@4.0.1 │ └─┬ websocket-stream@3.3.3 │ ├─┬ duplexify@3.5.0 │ │ ├── end-of-stream@1.0.0 │ │ ├── readable-stream@2.2.2 │ │ └── stream-shift@1.0.0 │ ├─┬ through2@2.0.3 │ │ └── readable-stream@2.2.2 │ └─┬ ws@1.1.1 │ ├── options@0.0.6 │ └── ultron@1.0.2 ├─┬ google-images@2.0.0 │ └─┬ got@6.7.1 │ ├─┬ create-error-class@3.0.2 │ │ └── capture-stack-trace@1.0.0 │ ├── duplexer3@0.1.4 │ ├── get-stream@3.0.0 │ ├── is-redirect@1.0.0 │ ├── is-retry-allowed@1.1.0 │ ├── is-stream@1.1.0 │ ├── lowercase-keys@1.0.0 │ ├── safe-buffer@5.0.1 │ ├── timed-out@4.0.0 │ ├── unzip-response@2.0.1 │ └─┬ url-parse-lax@1.0.0 │ └── prepend-http@1.0.4 └─┬ youtube-node@1.3.0 ├── colors@1.0.3 ├─┬ prompt@0.2.14 │ ├── pkginfo@0.4.0 │ ├─┬ read@1.0.7 │ │ └── mute-stream@0.0.7 │ ├── revalidator@0.1.8 │ ├─┬ utile@0.2.1 │ │ ├── async@0.2.10 │ │ ├── deep-equal@1.0.1 │ │ ├── i@0.3.5 │ │ ├─┬ mkdirp@0.5.1 │ │ │ └── minimist@0.0.8 │ │ ├── ncp@0.4.2 │ │ └─┬ rimraf@2.5.4 │ │ └─┬ glob@7.1.1 │ │ ├── fs.realpath@1.0.0 │ │ ├── inflight@1.0.6 │ │ ├─┬ minimatch@3.0.3 │ │ │ └─┬ brace-expansion@1.1.6 │ │ │ ├── balanced-match@0.4.2 │ │ │ └── concat-map@0.0.1 │ │ └── path-is-absolute@1.0.1 │ └─┬ winston@0.8.3 │ ├── colors@0.6.2 │ ├── cycle@1.0.3 │ ├── eyes@0.1.8 │ ├── pkginfo@0.3.1 │ └── stack-trace@0.0.9 └─┬ request@2.53.0 ├── aws-sign2@0.5.0 ├── bl@0.9.5 ├── caseless@0.9.0 ├─┬ combined-stream@0.0.7 │ └── delayed-stream@0.0.5 ├── forever-agent@0.5.2 ├─┬ form-data@0.2.0 │ └── async@0.9.2 ├─┬ hawk@2.3.1 │ ├── boom@2.10.1 │ ├── cryptiles@2.0.5 │ ├── hoek@2.16.3 │ └── sntp@1.0.9 ├─┬ http-signature@0.10.1 │ ├── asn1@0.1.11 │ ├── assert-plus@0.1.5 │ └── ctype@0.5.3 ├── isstream@0.1.2 ├── json-stringify-safe@5.0.1 ├─┬ mime-types@2.0.14 │ └── mime-db@1.12.0 ├── node-uuid@1.4.7 ├── oauth-sign@0.6.0 ├── qs@2.3.3 ├── stringstream@0.0.5 ├─┬ tough-cookie@2.3.2 │ └── punycode@1.4.1 └── tunnel-agent@0.4.3
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login