@zman3 no, that’s not the point, he uses the config library, we don’t. They mentioned some good points, such as “OSX makes node_modules readable only by the user so AWS cannot read it”, so you need to check the permission of your node_modules folder. And also make sure the node_modules inside the zip file is not empty.

@Journeytojah @zman3 see whether this thread helps you.
https://github.com/lorenwest/node-config/issues/275

@savage_gr1nd you can setup AlexaPi to run automatically after reboot

@savage_gr1nd yeah, but it requires a physical pushbutton. I’m using AlexaPi with my own wake word, so I can activate Alexa by saying “Mirror mirror”.

@Journeytojah that’s weird, like @savage_gr1nd said, the problem is usually on how you zip the files and folders inside src folder. It has nothing to do with RPi, or your zip file name, mine is the default ‘Archive.zip’. Assume you didn’t change the handler setting in Lambda, which should be ‘index.handler’. So you have to recreate the problem for me, show me how you do it step by step.

@savage_gr1nd that’s awesome!!! I’ll try to add a timeout on the module, it’s just that videos have different lengths, but I’m sure it can be done. To change font, you can add some css in MMM-MirrorMirrorOnTheWall.css.

@savage_gr1nd ok, so there are few places you can check.

1. the skill should console log the api response, so check it in Lambda. see whether ‘items[0].id.videoId’ is still the right way to get the video ID
2. use AWS IoT to check whether that video ID is published to channel “MagicMirror:new-video”
3. check your mirror module, see whether it received that video ID.

@Journeytojah ok, remember to change the region setting in MirrorMirror.js in both folders. (line 16 below)

@Journeytojah I think the region is why some people couldn’t get it to work. Right now, Lambda only works with US East regions. So better use US East for every AWS services needed here.

Just out of curiosity, which cities are you guys in? I’m in New York.