MMM-MirrorMirrorOnTheWall - Alexa voice control to hide/show modules and display text/images

[savage_gr1nd]

@joanaz I’m in California.
And I could try if I can ever figure out why I can’t get video to pop up in the first place lol and no I can’t get images to work either. That tests error in alexa skill Console so I’m digging into you tube first. Which tests positive.
I say find a video of… and she responds and puts the text on screen. But the url window doesn’t show.

[Journeytojah]

I still didn’t get mine to work, I haven’t tried again to be honest…

I am in Spain, if that makes a difference.

I was trying out other options for voice control like Jasper, etc; no luck so far.

I might come back to this module tonight and try to get it running.

Should I try to set it up for the European region that supports Alexa skills? (which is Ireland afaik)

[joanaz]

@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.

[Journeytojah]

@joanaz said in MMM-MirrorMirrorOnTheWall - Alexa voice control to hide/show modules and display text/images:

@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.

I had US East selected, but maybe because I am not physically located in the US it somehow gets blocked by some ISP somewhere along the way.

To me thats what it looked like, a connectivity issue.

And I know Alexa Skills with Lambda are only supported in some regions, but that includes one European one, the one in Ireland, so ill try that one.

Anyway, after seeing how impossible it is to work with Jaster/So.nus and so on, I will go back and give this another try…

[savage_gr1nd]

@Journeytojah no that’s not it. I’m in the west coast and I got my lambda and skill to link. Only thing I don’t have working are the Google api and youtube api

[joanaz]

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

[savage_gr1nd]

@joanaz so no idea on the YouTube problem? Like I said. I know it’s hitting the api. It has a success message in Google console. Just nothing pops up in MagicMirror itself except the text.

[joanaz]

@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.

[savage_gr1nd]

@joanaz awesome. I’ll check that when I get home. At least I have a starting point.
Thank you.

[Journeytojah]

Well, i get the same error when entering a sample utterance:

The remote endpoint could not be called, or the response it returned was invalid.

and in Lambda when i test:

START RequestId: a70ecb9c-efe6-11e6-b979-693b99b365f9 Version: $LATEST
END RequestId: a70ecb9c-efe6-11e6-b979-693b99b365f9
REPORT RequestId: a70ecb9c-efe6-11e6-b979-693b99b365f9	Duration: 3003.26 ms	Billed Duration: 3000 ms 	Memory Size: 128 MB	Max Memory Used: 15 MB	
2017-02-10T23:14:23.605Z a70ecb9c-efe6-11e6-b979-693b99b365f9 Task timed out after 3.00 seconds

any help would be welcomed, its keeping me awake at night, would love to get it working :)

Interesting enough, when i run it locally it connects…
http://imgur.com/aecZ8af

Still playing around, no luck…

Saw this in the log now…

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.<anonymous> (/var/task/index.js:27:17)
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)

Much later edit: so i notice that Lambda runs NodeJS 4.3, i am running 7.5 on the RPi, could that be it?