Hello, thank you for the answer, by dint of searching … it’s gone but I still have errors and even if I make orders as he asks git pull fix --force there is always stuff out of date but I think the main thing is done, I got a return for the download of 2.11. Thank you

I have not. I will certainly do so when I pick this project back up next week sometime. Thanks for the reply, and I’ll let you know.

@sdetweil Good to note that it don’t always work, FWIW… like it don’t help my situation, but, I only have to restart once in a great while now, so, I don’t see it nearly as much… now if I could get OMX to stop freezing so I don’t have to restart it every half hour (😭😭😭 not a magic mirror problem, Running it on top of MM to avoid RTSPStream bugs)

@sdetweil I do it manually, now I use your script to fix it, And the mirror back to normal again thank you Sam

@bhepler said in ENOENT yet the file exists within the Magic Mirror folder:

They’re pretty much one and the same. You already have git installed. Open a terminal in the modules folder, clone the module repository into it, follow the module’s instructions on installing & configuring.

Thank for the advice.

This should be PRd to the develop branch then!

@sbonn13 open a terminal window (ssh is ok too)

do

cd ~/MagicMirror/modules # search all module source for error string find . | grep -v node_modules | grep \.js$ | grep -i connection # search all module dependencies for error string find . | grep node_modules | grep \.js$ | grep -i connection

My mirror’s time can get late for the system time. Everything within the MM environment works by that late time, e.g the default clock and scheduled commands (MMM-ScriptScheduler items). The only scenario I can recreate this manually is stopping the mirror by “pm2 stop mm” and then rebooting it. After reboot there is about a 12 second latency.

Video: Spot time displayed by the clock module and in the top line of htop.

Performing a (shutdown)-(waiting)-(starting the system) procedure extends this interval. The more the RPi stays switched off the more the time difference will be. Refreshing the browser with Ctrl-R corrects the problem.

I have 3 mirrors running at the moment. (Actually, only one of them is a physical mirror :-) but let’s call them like that.)

mirror1: RPi4 4GB, MM v2.10.1, node v10.19.0, LAN mirror2: Rpi3B+, MM v2.10.1, node v10.19.0, LAN mirror3: Rpi3B+, MM v2.9.0, node v10.17.0, WiFi

Only mirror1 and mirror2 (the PRi’s with MM v2.10.1) can be forced to the above 12 sec delay.

All of them run the same config on 16GB SD cards. Modules:

MMM-ScriptScheduler MMM-GoogleMapsTraffic calendar clock MMM-LocalTemperature (with DHT22 sensor) currentweather weatherforecast plus the MagicMirror-Display-Controller python program (with RCWL-0516 sensor)

@max64 with release 2.10, all you have to do is set serverOnly: local in config.js
And it will do that split mode for you.

We are running such an old electron version.

@Clubjack and others,

I noticed this problem too.
For instance my birthday lasted 2 days ( only got presents once though) and my wedding-day is one day forward (which will upset my wife).
The entries were made using Google Calendar (so not a calendar app that synchronizes with Google).
I notice this since 2020, but that does not mean it did not happen before, could have overlooked it.
When I ran a test with a dummy entry, it worked fine.
When I toggle a „faulty“ entry from repeating to not repeating and then back to repeating, the entry is shown correct.
I collected some data and will post it when I sorted it out a bit.

@benjay Unfortunately the GIT status is still reporting issues (same as before)

those aren’t issues

the package-lock.json is generated by the npm install, so its new and changed.

the 0 is a bug from the installer once
and the core is some dump from npm/node crashing at some time.

all is good…
(git status in the MagicMirror folder should show the same output after reboot)

@sdetweil said in Calendar Doesn't Honor custom.css for Background:

@ember1205 said in Calendar Doesn't Honor custom.css for Background:

the Developer options with a real browser

electron is a real browser, so you can do this ON the mirror,
or from your desktop if the config parms allow remote system access.

I always forget that I can use local browser to view developer window

Now that you mention it, I have used the developer options directly on the appliance and should have remembered that. Thanks for the reminder!

@sdetweil

Sigh. Thanks. :)

@Artech do this

cd ~/MagicMirror git checkout modules/node_modules/node_helper/index.js

My mistake was that I had chossen to auto-start Desktop but not Autologin, after I changed to Autologin with Desktop everything was fine again.

@pedromrsantos
A workaround could be to use separat calendar for meetings and presentations only.
AxLED