Good day, I built my magic mirror a few month’s ago and was all working fine. I’ve been away on holiday with the device shut down, however when I plug it in, it boots, I see the beginning screens for the magic mirror but then it goes blank. Nothing on the screen, ALT and any other keys etc have no effect, it looks like it reboots but blank again. I tried putting the flash card into my computer but I can’t see any folders mentioning the magic mirror despite the mirror showing this at the initial stage. Any advice please, would I need to re-install/format, I don’t see any errors from what I can tell… Thanks in advance, Paul

Someone help me to make a module for share photo from dropbox to MagicMirror Thanks for your help

@flobbr said in Calendar displays time in 12h format, was 24: thank so very much, worked just fine :) Excellent! Enjoy your mirror

So it is definetly related to either pm2 or the MM application. If i stop the mirror with “pm2 stop mirror.sh” the normal pi desktop is shown and the screen does not go offline. The status light of the monitor is always “online”, even if there is no picture shown anymore. I can always revive the screen (for some minutes) with the above bash script. I really can’t get it, whats causing this. i checked the crontab -e file (also as sudo) there is just a @reboot script for the mirror to autostart after a reboot and two scripts for switching the monitor off at 10pm and switch on at 6.45am. This is working. Any suggestions? It started after testing with a pir sensor. This sensor is meanwhile disconnected physically.

I am trying to get a button trigger to work with this module, but no success. The push button is connected to GPIO16, wich is the native button 12, and I changed the config of AlexaPi to allow for this button trigger. No success ! Actually this is an AlexaPi problem and not MMM-AlexaPi, but if someone can show me a correct AlexaPi config, that would be great. Thanks.

@howi42 Yeah I’ve also noticed similar problems. For example, if there is a question where Alexa needs me to wait while checking something, I never get the final answer. For example: Me: “Alexa, is my back door locked?” Alexa: “Checking… hold on.” At this point the module just goes back to idle instead of telling me if the door is locked. Similarly multiple part conversations don’t work either. Say I needed a showtime for a movie but I didn’t specify what theatre or what movie. The conversation might go like this: Me: “Alexa, what time is the movie playing?” Alexa: “Which movie would you like to see?” Normally, a real Echo would go back to the prompt state expecting a response from me. But the module goes back to idle at this point. To be fair, I don’t think this is an issue with with MMM-AlexaPi, I think it is the underlying AlexaPi library that is causing this. I haven’t tried this specifically without Magic Mirror running, but I’d be willing to bet that the same issues would happen if I did. I’ve also noticed that Alexa will only respond reliably to my voice. It works only sometimes when my wife says “Alexa”, and practically never when either of my kids say it. They are aged 6 and 9, so I’m guessing that AlexaPi has a hard time recognizing higher pitched voices (or maybe it’s the $6 microphone I’m using :).

Resolved. Thanks

@yawns that’s exactly my point

I realize this is an old thread - but the rpi3 does have an OpenGL driver that you can install via raspi-config under “Advanced” It does have a GPU - “Broadcom Video Core” -Earle

@t3xastoast So apparently changing the port from 8080 to 8000 in the config.js fixed this. It works now.

Hi all: I had a fully functioning MM install on a Pi3 and I wanted to try to add Alexa functionality. I installed Alexa following: https://lifehacker.com/the-simplest-way-to-build-a-raspberry-pi-powered-amazon-1794218212 because I could not get the MMM-Alexa app through the Amazon sign-up. I was connected to the MagicMirror through an SSH and I had fixed the ip to 192.168.0.254 which was free and in my reserved area on my router. In working through the steps, it appeared that my USB sound card wasn’t working so I shifted to getting the sound card working for both recording and playback (I have one of those USB sound cards with both mic and headphone jacks). The very first step was to do an update and upgrade: $ sudo apt-get update $ sudo apt-get upgrade Well, it got through the update okay so I started the sudo apt-get upgrade command and left it alone. When I returned the SHH was disconnected and it seemed that an error had occurred somewhere. I rebooted and did an ipscan and I could not find my MagicMirror! No device at 192.168.0.254. It’s possible that in registering my Alexa app to Amazon (which was completed successfully) that the fixed ip had been overwritten to be a dhcp device but no other connected device appeared to be my magic mirror. I have TWO Echo dots and when I look at the devices on my router there are THREE Amazon devices. Does this mean that the Amazon registration redefined the ip address for the MM because I registered the Alexa app? I tried remotely logging into each of these devices but none replied, so I couldn’t login that way. So, I pulled the microsd card and put it in a new Pi3, connected a mouse, usb keyboard, hdmi monitor and a 2.5A, 5v microusb power connector to work on it directly. It boots up, opens my window environment and then the Magic Mirror. I get the captions but none of the internet content (its likely the machine is not connected to the internet). So I try to kill the Magic Mirror to get back to the windowing environment and it does not respond to any keystrokes or mouse clicks!! I’ve tried ctrl-c, ctrl-w, ctrl-q, ctrl-z, ctrl-x … and even the special functions keys that use to interrupt the MMM window so I could enter ctrl-c in it base window. In fact, even the caps-lock button does not even light up the LED on one of the keyboards … so it’s like the keyboard is not being recognized!! I’ve tried 2 keyboards, but neither allow me to interrupt. If the keyboard and/or mouse are not being recognized, how do I interrupt the boot sequence or the MM autostart before they start the MM? I really do not want to start over as I customized the MMM and had it where I wanted it configured. Any one have any magic to try to fix this??

So i was rereading the wiki and noticed the remote file needs to be in .json format while the script is in .js. I’m sure that will make things more difficult

@berlincount oh, I’ve tested both master and develop branches, and any non-opaque backgroundColor gives bad redraws on clocks etc - but no transparent background …

Answering myself here might help somebody with a similar problem. Thanks to the latest Issue 60 of The MagPi I checked the wireless network with the Wifi Analizer and I realized that I had to change the channel. Looks much better now :)

@jgrossrieder said in I only have a white command line after following the tutorial: also, I rebooted the Pi, and the mirror didn’t restart :( Here it is: https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror

Working my way through errors … I am able to get it to load ( in serveronly mode ) : After some time a message says : Register Alexa Java Client by navigating to https://localhost:5555/provision/xxxxxxxxxxxxxxxxxxxxxxx I have to do this manually to make the loading continue. It then throws an error message, tells me that the client is registered with a token, finishes loading and when I say mirror mirror, I can talk to Alexa and get an answer, but : the trigger works only once registering to get a token is fine, but not for each reboot/restart running not via serveronly will not work because of that Here is probably something still wrong. Any ideas ? Thanks Thanks

Romain can you please tell me how you were able to do that?

I’ve been ‘googling’ since posting and have found the solution (may not be the best solution, but it is now working). I’ll put it here as it may help someone, or someone else may have a better suggestion: targetTemperatureCell.insertBefore(frostCell, targetTemperatureCell.firstChild);

Can I set this to be shown in the background ? As it is now, it is always on top of everything. Thanks