• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

MMM-MirrorMirrorOnTheWall installation issue

Scheduled Pinned Locked Moved Unsolved Troubleshooting
138 Posts 11 Posters 130.2k Views 10 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    richland007 @OceanK
    last edited by Dec 10, 2018, 4:18 AM

    @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

    1 Reply Last reply Reply Quote 0
    • O Offline
      OceanK
      last edited by Dec 11, 2018, 3:40 PM

      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 =)

      1 Reply Last reply Reply Quote 1
      • B Offline
        blackpanda
        last edited by blackpanda Dec 31, 2018, 8:22 PM Dec 31, 2018, 8:20 PM

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

        R O 3 Replies Last reply Jan 2, 2019, 2:46 AM Reply Quote 3
        • R Offline
          richland007 @blackpanda
          last edited by richland007 Jan 2, 2019, 2:56 AM Jan 2, 2019, 2:46 AM

          @blackpanda Hey thank you for reviving the topic and happy new year.
          Quick question were do i find the ‘AWS IoT>Secure>Policies’
          so i can make the necessary changes at??

          Is it over on the MirrorMirrorOnTheWallSkill i have a aws-iot-device-sdk folder under src/node_modules but there is no Secure sub folder in it!!!

          D

          B 1 Reply Last reply Jan 2, 2019, 3:44 AM Reply Quote 0
          • B Offline
            bhepler Module Developer @richland007
            last edited by Jan 2, 2019, 3:44 AM

            @richland007 said in MMM-MirrorMirrorOnTheWall installation issue:

            Quick question were do i find the ‘AWS IoT>Secure>Policies’

            Policies are modified via the Amazon Web Services (AWS) management console.

            You can update the policy by submitting JSON through the API. Or you can use the management console and just duplicate the settings posted above.

            1 Reply Last reply Reply Quote 0
            • O Offline
              OceanK @blackpanda
              last edited by Jan 2, 2019, 8:39 AM

              @blackpanda thanx bro! I will try this later today, I will report back. @richland007 did it work for you?

              1 Reply Last reply Reply Quote 0
              • O Offline
                OceanK @blackpanda
                last edited by Jan 2, 2019, 10:17 AM

                @blackpanda SO you got this to work? I still have problem =( When building the model could you paste your interactionmodel? the one that goes into the json editor…

                R 1 Reply Last reply Jan 4, 2019, 5:04 AM Reply Quote 0
                • R Offline
                  richland007 @OceanK
                  last edited by Jan 4, 2019, 5:04 AM

                  @oceank I haven’t gotten the chance to give it another try but i will soon :)
                  Did you do the changes that @blackpanda suggested ?? whats it telling you now??

                  @blackpanda It took me a while to realize that it says MagicMirror but on our MirrorMirror.js file the ClienId is MirrorMirror so i changed that and i uploaded on Lambda and i made the appropriate policy changes on the IoT to reflect my arn:aws and my number nut just copy paste yours
                  but when i test Lambda now i get this error: The applicationIds don’t match: amzn1.ask.skill.[unique-value-here] and amzn1.ask.skill.e0223a06-d061-48bd-9b1c-3XXXXa950fcf

                  And the app ID has not changed?? And also when i go to test the skill now on the Alexa developer side now i dont even get"Hello My queen…" i used to get it just goes straight to there was a problem with the requested skills response.

                  What else do i need to change cause i doubt there is anything major …has the syntax changed again appID or aplicationId etc???

                  Thank you any help is greatly appreciated
                  D

                  B 1 Reply Last reply Jan 5, 2019, 12:20 AM Reply Quote 0
                  • B Offline
                    blackpanda @richland007
                    last edited by Jan 5, 2019, 12:20 AM

                    @richland007 so you changed the clientId in the lambda function and uploaded it. Did you change the client id in the module as well? Can you post your security policy? You should also define your queues (modules) there.

                    The app id is defined in index.js of the skill. APP_ID is defined in a variable near the top of the file.

                    Looks like this currently:

                    alexa.appId = APP_ID
                    

                    Also, you can verify what your skill id is by checking in the amazon developer console then selecting ‘endpoint’ (it’s an option on the left pane under interaction model and interfaces).

                    1 Reply Last reply Reply Quote 0
                    • B Offline
                      blackpanda
                      last edited by blackpanda Jan 5, 2019, 12:38 AM Jan 5, 2019, 12:33 AM

                      pro-tip:

                      A way to check and see if you’re actually subscribing to the topics that are publishing search results:

                      if you run the following command from a remote putty session…

                      cd ~/MagicMirror
                      Display=:0 npm start
                      

                      you should eventually see that you’re subscribing to the topics!

                      0_1546647936057_ee77adc1-bc3d-485e-b41a-8db53529a743-image.png

                      Initially, the misconfigured security policy was preventing this from happening and authorization errors were being thrown in the background (had to dig into cloudwatch logs for this). In putty, the command would simply hang at “Attempt to connect to AWS”

                      Basically your youtube api search results will be published to the “new-video” queue…and if your aren’t subscribed to that queue then you wont see anything change on your monitor. Same for your google image searches and “new-images”. and so on.

                      R 1 Reply Last reply Jan 5, 2019, 9:19 PM Reply Quote 0
                      • 1
                      • 2
                      • 6
                      • 7
                      • 8
                      • 9
                      • 10
                      • 13
                      • 14
                      • 8 / 14
                      • First post
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy