MMM-MirrorMirrorOnTheWall installation issue

OceanK

hey!

its not possible to build the alexa module with the intentmodel.json

The intentmodel.json is depricated, and I cannot build the model =(

what to do now?

OceanK

So im back again!

I started it all from scratch!

still getting this:

{
“errorMessage”: “In state: . No handler function was defined for event SessionEndedRequest and no ‘Unhandled’ function was defined.”,
“errorType”: “Error”,
“stackTrace”: [
“AlexaRequestEmitter.EmitEvent (/var/task/node_modules/alexa-sdk/lib/alexa.js:212:15)”,
“AlexaRequestEmitter.ValidateRequest (/var/task/node_modules/alexa-sdk/lib/alexa.js:181:23)”,
“HandleLambdaEvent.i18n.use.init (/var/task/node_modules/alexa-sdk/lib/alexa.js:123:29)”,
“/var/task/node_modules/i18next/dist/commonjs/i18next.js:190:9”,
“done (/var/task/node_modules/i18next/dist/commonjs/i18next.js:281:21)”,
“/var/task/node_modules/i18next/dist/commonjs/i18next.js:302:7”,
“I18n.loadResources (/var/task/node_modules/i18next/dist/commonjs/i18next.js:238:7)”,
“I18n.changeLanguage (/var/task/node_modules/i18next/dist/commonjs/i18next.js:301:10)”,
“load (/var/task/node_modules/i18next/dist/commonjs/i18next.js:186:14)”,
“I18n.init (/var/task/node_modules/i18next/dist/commonjs/i18next.js:195:7)”
]
}

OceanK

Something is not right with the lamda function.

OceanK

Nothing from your side @richland007 ?

richland007

nothing at all my friend

richland007

@oceank this looks very interesting to control themirror with alexa installed already likemy case is https://forum.magicmirror.builders/topic/9211/mmm-alexaonoff-simple-mirror-control-from-external-home-assistant-alexa-google-home-hass-io

D

OceanK

Hey!@richland007

thats i pretty cool! well I already can by voice show and hide every module individually actually and I do that offline. So I dont need any online module like an echo and so on to do this.

richland007

@oceank how do you hide and show all modules what do you use to do that via voice?? ??/ thats why i wanted mirror mirror for ?? doy you yse MMM-voices?? i can not use that cause it messes my Alexa Pi up

OceanK

Hey @richland007 !

I use this module: Helo Lucy: https://github.com/mykle1/Hello-Lucy

So im running aintel nuc with ubuntu to run the magicmirror with lucy. So I have one hidden microphone behind the mirror for that.

Then I have a raspberry pi with hidden microphone and speakers, running both Alexa and google assistant =)

https://github.com/shivasiddharth/Assistants-Pi

So now its running like I want it =)

blackpanda

@OceanK @richland007

Just a heads up –

I was running into the same issues as you both. After hours of research I eventually discovered that the AWS IoT security policy for your certificates must be properly configured…otherwise you’ll be hit with authorization issues when clients attempt to connect to the IoT thing for subscribing, publishing, connections, etc. Once i corrected this, I had no further issues with the installation.

The change I made to my policy in ‘AWS IoT>Secure>Policies’ is below:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "iot:Publish",
        "iot:Receive"
      ],
      "Resource": [
        "arn:aws:iot:us-east-1:543211234567:topic/sdk/test/java",
        "arn:aws:iot:us-east-1:543211234567:topic/sdk/test/Python",
        "arn:aws:iot:us-east-1:543211234567:topic/topic_1",
        "arn:aws:iot:us-east-1:543211234567:topic/topic_2",
        "arn:aws:iot:us-east-1:543211234567:topic/MagicMirror:new-text",
        "arn:aws:iot:us-east-1:543211234567:topic/MagicMirror:new-images",
        "arn:aws:iot:us-east-1:543211234567:topic/MagicMirror:change-module",
        "arn:aws:iot:us-east-1:543211234567:topic/MagicMirror:new-video"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "iot:Subscribe"
      ],
      "Resource": [
        "arn:aws:iot:us-east-1:543211234567:topicfilter/sdk/test/java",
        "arn:aws:iot:us-east-1:543211234567:topicfilter/sdk/test/Python",
        "arn:aws:iot:us-east-1:543211234567:topicfilter/topic_1",
        "arn:aws:iot:us-east-1:543211234567:topicfilter/topic_2",
        "arn:aws:iot:us-east-1:543211234567:topicfilter/MagicMirror:new-text",
        "arn:aws:iot:us-east-1:543211234567:topicfilter/MagicMirror:new-images",
        "arn:aws:iot:us-east-1:543211234567:topicfilter/MagicMirror:change-module",
        "arn:aws:iot:us-east-1:543211234567:topicfilter/MagicMirror:new-video"
      ]
    },
    {
      "Effect": "Allow",
      "Action": [
        "iot:Connect"
      ],
      "Resource": [
        "arn:aws:iot:us-east-1:543211234567:client/sdk-java",
        "arn:aws:iot:us-east-1:543211234567:client/basicPubSub",
        "arn:aws:iot:us-east-1:543211234567:client/sdk-nodejs-*",
        "arn:aws:iot:us-east-1:543211234567:client/MagicMirror*"
      ]
    }
  ]
}

Make sure your client id defined in MirrorMirror.js matches the wildcard (“MagicMirror” in this case) that was added to iot:Connect action of the policy. This needs to be modified locally in the module and also in the uploaded lambda function!

// Setup our AWS IoT device and receive messages
app.setup = function() {
  app.device = awsIot.device({
    keyPath: __dirname + "/certs/MagicMirror.private.key",
    certPath: __dirname + "/certs/MagicMirror.cert.pem",
    caPath: __dirname + "/certs/root-CA.crt",
    clientId: "MagicMirror" + (new Date().getTime()),
    region: "us-east-1",
    host: "YOURID.iot.us-east-1.amazonaws.com",
  });

Best of luck and happy new year!