@Sean I’ve followed the guide to disable the screen saver and the power management for the Pi, so this shouldn’t be an issue.

Hello,

After all, disabling MMM-HASS and MMM-pihole-stats did not solve the problem.
Even after a fresh install without this modules, it still hapens. The strange thing is that if i access the MagicMirror via HTTP from my computer, the we page loads correctly with all the items, but on the mirror/Pi it’s a black page, only displaying correctly after a MM service restart. :(
Could it be something with the MM browser?

Best regards, Bruno

Thanks for the answer, but in “For each billing account, for qualifying Google Maps Platform SKUs, a $200 USD Google Maps Platform credit is available each month, and automatically applied to the qualifying SKUs.”, what do they mean for “qualifying Google Maps Platform SKUs”?

Best regards, Bruno

Hello,

I’m interested in using one or more modules that use the googleAPI, but from their billing page, i see that it could be very costly per month specially if we do several requests per day.
What do you guys use and how do you keep your usage low so that it don’t cost very much?
Is it a free version of the GoogleAPI with limits?

Many thanks for your help, Bruno

Hello,

I was trying to install MMM-RTSPStream today and npm fails everytime with ecstatic dependency not met:

pi@mdr-mm:~/MagicMirror/modules/MMM-RTSPStream $ npm install
npm WARN deprecated datauri@1.1.0: Datauri 2.0 released. See more in https://github.com/data-uri/datauri/releases/tag/v2.0.0
npm WARN deprecated mimer@0.3.2: Mimer 1.0 released. See more in https://github.com/data-uri/mimer/releases/tag/v1.0.0

MMM-RTSPStream@1.2.2 postinstall /home/pi/MagicMirror/modules/MMM-RTSPStream
sudo npm i -g http-server

npm ERR! code ETARGET
npm ERR! notarget No matching version found for ecstatic@^3.0.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn’t exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of ‘http-server’
npm ERR! notarget

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-05-02T21_57_30_835Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! MMM-RTSPStream@1.2.2 postinstall: sudo npm i -g http-server
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the MMM-RTSPStream@1.2.2 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2019-05-02T21_57_31_267Z-debug.log

I found out that ecstatic 3.x.x was removed and only version 4.1.2 exists, leaving me unable to install http-server:

pi@mdr-mm:~ $ npm view ecstatic versions --json
[
“4.1.2”
]

@shbatm , it it possible for you to update your code to overcome this problem?

Regards,

Bruno

I found out that it seams the MMM-HASS and MMM-pihole-stats are causing the problems.
Whe I use the “disabled” : true", the mirror works for hours without any problems, but when I load the modules, the chromium browser turns black (like without any info) until I restart MM.
Any ideas?

Regards, Bruno

Try this topic: https://forum.magicmirror.builders/topic/6291/howto-turn-on-off-your-monitor-time-based-pir-button-app

I got mine working from here and it has lots of options!

Regards,

Bruno

Also I fond this on “pm2 logs mm”:

0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | ERROR! Could not find main module js file for .AppleDouble
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.
0|mm | libGL error: MESA-LOADER: failed to retrieve device information
0|mm | ERROR! Could not find main module js file for .AppleDouble
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment.

Regards,

Bruno

Hello, I’ve installed several weeks ago MM 2.6.x on a Pi 3 B+ and had it on tests several days in a row without problems. I also implemented the MMM-PIR-Sensor with a RCWL-0516 (radar sensor) for disconnecting the monitor and it worked like a charm.
When I finally installed it on the wood Frame, hung it to the wall, upgraded to 2.7.0, added more modules and something weird started to happen: after several hours being on, I noticed two occurrences:

1st - the screen was off, when I approached it the sensor would send the signal for the MMM-PIR-sensor module turn on the monitor, but it appeared on but black, with the RB Pi responding to ping and ssh. When I hit F11, Chromium would show in window mode but without information. When I restarted the MM services (pm2 restart mm), everything is ok for a few hours.

2nd - the screen is off (could not detect connecition), approaching doesn’t turn on the monitor and nothing responds (keyboard, ping, etc). I do a power cycle and everything is ok for a few hours.

This only started to happen after I installed it on the frame, updated to 2.7.0 and installed some additional modules. Did anyone else had this kind of behaviour? How can I debug this?

Here are the modules I have installed:

MMM-AirQuality
MMM-Globe
MMM-HASS
MMM-ImageSlideshow
MMM-NetworkScanner
MMM-PIR-Sensor
MMM-Remote-Control
MMM-Tools
MMM-WorldTides
MMM-pihole-stats
octomirror-module

Best regards,

Bruno