@anhanyoung I am using a raspberry pi3+

The This site can’t be reached error message could happen on Windows 8, Windows 10, Linux, Chrome OS or Android devices. No matter why Chrome browser shows this message, but it needs to fix permanently. Here are some possible solutions, these solutions will try to minimize or remove the error completely and takes you to your desired website in your Chrome browser. Clear browser cache, history and cookies Reset Chrome browser settings Reset Wi-Fi Modem Restart DNS client Reset the Chrome profile Sync Remove browser extension from Chrome Scan your device for malware Reinstall Chrome Install another web browser

Hey Guys! it works now! i did it as described with the mm script here: https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror thank you for all your replies! Regards Dario

SO, the workaround… NEVER call updateDom() without a minimum count of 2 (as the code divides by 2 inside) it does a hide/update/show) (hide/show each get 1/2 the time specified, ie 2/2 =1 each.

Can somebody help me with these error logs? 0|mm | (node:23821) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'refs' of undefined 0|mm | at /home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:238:31 0|mm | at /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/git.js:780:18 0|mm | at Git.<anonymous> (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/git.js:820:18) 0|mm | at done (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/git.js:1432:21) 0|mm | at /home/pi/MagicMirror/modules/MMM-Remote-Control/node_modules/simple-git/src/git.js:1457:16 0|mm | (node:23821) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) 0|mm | (node:23821) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. 0|mm | ATTENTION: default value of option force_s3tc_enable overridden by environment. My remote control module works very well. Is there something I must do?

@mykle1 So at some point my MM did go black again. I commented out my iframe module and then restarted it and now it has been stable for 6+ hours with no issues. This leads me to think it is something with iframe. // { // module: 'MMM-iFrame', // position: 'bottom_center', // This can be any of the regions. // config: { // // See 'Configuration options' for more information. // url: ["http://192.168.1.132:81/livestream.htm?cam=Cam1"], // as many URLs you want or you can just ["ENTER IN URL"] if single URL. // updateInterval: 0.5 * 60 * 1000, // rotate URLs every 30 seconds // width: "1280", // width of iframe // height: "720", // height of iframe // frameWidth: "640" // width of embedded iframe, height is beeing calculated by aspect ratio of iframe // } // }, I am not sure what else could be causing it, or else I would try to do some more troubleshooting myself.

Yes, another RTSPStream issues thread! Long story short, I’ve been running RTSPStream for years without a problem. About a month ago I wiped out my pi and started fresh with Stretch, reconfigured and even used the same config file as prior with no problems ( using the same camera and same http: link to camera). Now I have issues with my stream going blank randomly. It will work fine for a while when MM boots up then randomly will just go blank. I have spent the past couple weeks digging through this forum researching and reading all the other issue threads related but I am officially out of ideas. This is the troubleshooting I have done so far: Disabled GL drivers Tweaked config based on suggestions on other threads Verified Omxplayer is updated Verified stream works fine via VLC Tested with both low and high-quality feeds Increased GPU memory to 120 As for logs, I can’t seem to capture any errors or red flags popping up regarding RTSPStream from the ‘mm-out.log’. The only thing I could verify is when the stream is working, omx_stream1 shows online, and offline when it goes blank. If I try to perform ‘pm2 start omx_stream1’ it will revert back to online, but the stream is still blank. If anyone has any idea or guidance for me I would greatly appreciate it. It seems the issue happened when switching to Stretch as everything worked perfectly with Jessie. Maybe there are more logs I don’t know of that can help pinpoint this issue? Here is the latest from the logs, this is current from today after waiting for the stream to go blank. All the previous logs are the same, just repetitive: Starting MagicMirror: v2.6.0 Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. No helper found for module: currentweather. No helper found for module: MMM-windy. Initializing new module helper ... Module helper loaded: MMM-WatchDog Initializing new module helper ... Module helper loaded: MMM-WunderGround Initializing new module helper ... Module helper loaded: mmm-nest-status Initializing new module helper ... Module helper loaded: calendar Initializing new module helper ... Module helper loaded: MMM-MyCommute Initializing new module helper ... Module helper loaded: MMM-History Initializing new module helper ... Module helper loaded: mmm-systemtemperature No helper found for module: MMM-pihole-stats. Initializing new module helper ... Module helper loaded: MMM-News Initializing new module helper ... Module helper loaded: MMM-RTSPStream All module helpers loaded. Starting server on port 8080 ... Server started ... Connecting socket for: updatenotification Connecting socket for: MMM-WatchDog Starting module helper: MMM-WatchDog Connecting socket for: MMM-WunderGround MMM-WunderGround helper started ... Connecting socket for: mmm-nest-status Starting node_helper for module [mmm-nest-status] Connecting socket for: calendar Starting node helper for: calendar Connecting socket for: MMM-MyCommute ====================== Starting node_helper for module [MMM-MyCommute] Connecting socket for: MMM-History Starting module: MMM-History Connecting socket for: mmm-systemtemperature Starting node helper: mmm-systemtemperature Connecting socket for: MMM-News Connecting socket for: MMM-RTSPStream Sockets connected & modules started ... Launching application. WatchDog started. Maximum timeout: 10s. GET_WUNDERGROUND Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/ketz%40gmail.com/private-2d9/basic.ics - Interval: 300000 Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/en.usa%23holiday%40group.v.calendar.google.com/public/basic.ics - Interval: 300000 [NEWS] Initialized. [NEWS] Articles are aggregated : 10 Starting stream stream1 with args: [ "--avdict", "rtsp_transport:tcp", "--win", "63, 1043, 843, 1543", "--live", "--video_queue", "4", "--fps", "30", "rtsp://admin:xxxxxxxx@192.168.0.7:554/h264Preview_01_main" ] PM2: omx_stream1 already running. Stopping old instance... Starting PM2 for omx_stream1 PM2 started for omx_stream1 [NEWS] Articles are aggregated : 10 2019-02-13T15:09:40-05:00 6 MMM-WunderGround: null [NEWS] Articles are aggregated : 10 2019-02-13T15:19:42-05:00 6 MMM-WunderGround: null [NEWS] Articles are aggregated : 10 [NEWS] Articles are aggregated : 10 [NEWS] Articles are aggregated : 10 [NEWS] Articles are aggregated : 10 and the config: { module: "MMM-RTSPStream", position: "bottom_bar", config: { autoStart: true, rotateStreams: false, rotateStreamTimeout: 10, moduleWidth: 780, moduleHeight: 500, localPlayer: 'omxplayer', remotePlayer: 'none', showSnapWhenPaused: false, remoteSnaps: false, stream1: { name: 'Front', url: 'rtsp://admin:xxxxxx@192.168.0.7:554/h264Preview_01_sub', frameRate: undefined, hdUrl: 'rtsp://admin:xxxxxxx@192.168.0.7:554/h264Preview_01_main', width: 780, height: 500,o omxRestart: 24, }, } }, Thanks in advance!

@bkeyport Actually found a workaround using iframe and a HLS stream from blue iris. Have a new issue now that I am trying to figure out.

Problem was outdoor module battery was poor (however, was reported at 67% by netatmo). If data is missing from netatmo the netatmo module will stop updating and keep the old temperatures. If MM is restarted a spinning wheel will be shown. Hope that the new batteries did the trick.

SO… the problem is the calculation uses the local hour to determine from now… but users see days… so the fix is to truncate NOW to the start of the day…, then the comparison is start of day to start of day… instead of this // uses hours/mins/seconds of now.. timeWrapper.innerHTML = this.capFirst(moment(event.startDate, “x”).fromNow()); do this // uses only date, time is 00:00:00, fullday events also start at 00:00:00 timeWrapper.innerHTML = this.capFirst(moment(event.startDate, "x").from(moment().format("YYYYMMDD")));

@binog if you don’t want to wait any longer backup your ‘modules’ folder, the config and delete the whole MagicMirror directory. When you reinstall you will have the latest version (remember to restore then your backups).

i posted an update for the MMM-Voice repo that implements the mic sharing via voice command and cross module notifications… still need a fallback mechanism in case no other module claims the mic, right now I have a hard coded 10 second timer just to prove it works

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