Hi, What if I have original Google AIY version 1 module, could GassistPi replace the custom image provided by Google, and would it work perfectly? Thanx, /TheStigh

@shawb91 said in SUDO NPM Install is erroring and NPM is not installing please help: Error: EACCES: permission denied Maybe try running ‘npm init’ before you run ‘npm install’ ? See this Stack Overflow: Error: EACCES: permission denied

@lpt2007 Have you read the readme of MagicMirror? Also note that: npm start does not work via SSH. But you can use DISPLAY=:0 nohup npm start & instead. This starts the mirror on the remote display. AxLED

@axled I removed too but since it is created for restarting the MM in case the UI crashes we may consider what the problem was and it was forcing watchdog to restart the app. Not everyone has the same problem from what I read in the forum. That’s why I posted my pm2 logs in case someone identifies the problem.

same problem here. Do you have a solution?

canon g10

@Klinge For using Paviros module MMM-PIR-Sensor your config is wrong. Instead of module: 'MMM-PIR', you have to use module: 'MMM-PIR-Sensor', Also the options “delay”, “turnOffDisplay” and “showCountdown” are not part of the module MMM-PIR-Sensor and so there are not working. AxLED

@link953 Are you sure there is no message? I had a similar problem where some css values where wrong, so the message had the same color than the background. Normally you can find out, if you try to mark the message with a mouse. AxLED

Hello everyone. I would like to ask what problems I may have if I downgrade my MM from latest v. 2.6.0 to v. 2.3.1. I am asking because I have installed MM and Mycroft on the same Rpi 3b+ and the creator of the Magic Mirror Voice Skill suggest this version because of the different versions of electron they use. Last version of MM uses a newer version of electron which causes extremely high CPU usage and will overheat the pi. My pi is in a case with heat sinks and a small fan over the main chip. It does not overheat but it freezes sometimes and I think that it may be electron’s fault. Any idea? Because I am a noob I maybe am wrong so any suggestions will be welcome. Thank you in advance.

@mykle1 :rolling_on_the_floor_laughing: :rolling_on_the_floor_laughing: :rolling_on_the_floor_laughing: yeah, realized the main issue was trying to get it to have a border and it just wouldn’t work with the wide screen monitor of the TV.

Hi everybody, I have an issue that I don’t realize how to solve it: My mirror has several modules, but particularly has MMM-ImageSlideshow to show images in an iterative way. Everything works fine, but now, I need to pass the images shown by ImageSlides with a button action (show previous or next image). At first, I tried to instance some ImageSlides modules (each module showing only one picture) and I tried to manage the visualization of each module with MMM-Carousel without success, because all instances of ImageSlides were shown in the mirror at the same time (not only one at time). So, I researched in the 3rd-party-modules but I didn’t find anything that can fit to my requirement. In summary, I’m looking for some way to pass images (previous and next) by a button action. I would be very nice to me if some of you have an idea how to do this. Also, if someone want to share a config file as an example I would be very grateful. Thank you very much. Regards! Agustin.

so there was one issue in each .js file, I ended up pasting the entire .js repository back in from the GitHub files, that seems it fixed it. for people having this issue when it black screens, run cd MagicMirror npm start dev that starts up magic mirror with dev options, go to the second tab, there will be files that have errors or security issues, that’s what it was for mine anyway… It’s fixed now, thanks a lot for helping.

@dgregory19 said in MMM-Astrology MagicMirror Crash: Thats the funny part. I did run the config:check and it found no errors That’s because the error wasn’t in the config.js file, as mentioned above. So now you don’t have to make the edit yourself. Simply run git pull in the MMM-Astrology directory then run your mirror

Thank you @lavolp3 and @sdetweil …IT WORKS!!!

Found it. https://forum.magicmirror.builders/topic/9707/save-performance-when-rotating-screen-e-g-on-raspberry-pi Looks like this is a better option. Will give it a try myself.

try this topi https://forum.magicmirror.builders/topic/9386/installing-on-a-pi-zero

@sdetweil does that mean the automatic setup doesn’t have it or the manual github setup doesn’t have it listed as a step? :thinking_face:

For anyone that encounters a similar issue, the “X-Frame-Options” header needed to be hidden: proxy_hide_header X-Frame-Options;

I posted this in another thread too. Hi, For beginners, the catchphrase is “JSON syntax”. There are many articles to be found, both short and lengthy. A small article would be: https://restfulapi.net/json-syntax/ The main things to look for in your config.js file are: does every [ have a matching ] are all arrays separated by a , (the last array does not need a ,) does every { have a matching } are all objects separated by a , (the last object does not need a ,) is every name value pair separated by a , The syntax checker will try to find out if this syntax is correct and tries to predict where the error could be. So, when it says it saw a [ and it cannot find a matching ] it tells you what was expected and what it saw. Try to format you config.js to make it more visible. For example this: [{},{}],[{},{[]}] is better written like this: [ {}, {} ], [ { }, { [ ] } ] Pairs of [ ]and { } are better visible like this. Good luck :-)

Hi, For beginners, the catchphrase is “JSON syntax”. There are many articles to be found, both short and lengthy. A small article would be: https://restfulapi.net/json-syntax/ The main things to look for in your config.js file are: does every [ have a matching ] are all arrays separated by a , (the last array does not need a ,) does every { have a matching } are all objects separated by a , (the last object does not need a ,) is every name value pair separated by a , The syntax checker will try to find out if this syntax is correct and tries to predict where the error could be. So, when it says it saw a [ and it cannot find a matching ] it tells you what was expected and what it saw. Try to format you config.js to make it more visible. For example this: [{},{}],[{},{[]}] is better written like this: [ {}, {} ], [ { }, { [ ] } ] Pairs of [ ]and { } are better visible like this. Good luck :-)