Platform: Raspberry Pi 3 B+ Node Version: 12.16.1 MagicMirror Version: 2.13.0-develop and also the current master branch Description: The calendar module shows 10 lines of the next dates. But in the config.js I have limited it to 5 entries. module: "calendar", header: "Kalender", position: "top_left", config: { titleReplace: { "Aichach": "", "in": "" }, fade: false, calendars: [ { symbol: false, maximumEntries: 5, url: "https://calendar.google.com/......} ] } Is there any idea what is wrong ?

Hi @ all i used this wunderfull projekt and it is really nice. but at the moment i had a problem. When i used the system language “de” some calendar events show “%s”. When i switch to “en” or “fr” it shows the right number. The following pictures shows what i mean: de: [image: 6ij45x5i.jpg] en: [image: egxbnhj8.jpg] fr: [image: yjwwac57.jpg] this is the modul config in the config file: { module: "calendar", header: "Gesetzliche Feiertage", position: "top_left", config: { maximumEntries : 5, colored: true, calendars: [ { color: "#f0ffff", symbol: "calendar-check", url: "webcal://abo.kleiner-kalender.de/ical/c48-feiertage-in-deutschland.ics" } ] } }, My used system: Platform: Raspberry Pi 4 Model B Rev 1.1 Node Version [ 0.12.13 or later ]: v10.19.0 MagicMirror Version [ V1 / V2-Beta ]: 2.12.0 NPM: 6.14.6

Thanks. That module don’t have a package.json and is probably using an old version of some kind of dependency then. I will remove the module completely as it has not been working anyway.

I am not sure how to solve this error? git pull & npm install are updated. Running docker image. {"log":"[2020-06-12 23:21:50.643] [ERROR] TypeError: Cannot read property 'pollution' of undefined\r\n","stream":"stdout","time":"2020-06-13T04:21:50.652110212Z"} {"log":" at Object.parseAIR (/opt/magic_mirror/modules/MMM-NOAA3/providers/ds.js:184:35)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.660031299Z"} {"log":" at Request._callback (/opt/magic_mirror/modules/MMM-NOAA3/providers/ds.js:176:28)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.666082512Z"} {"log":" at Request.self.callback (/opt/magic_mirror/modules/MMM-NOAA3/node_modules/request/request.js:185:22)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.672814787Z"} {"log":" at Request.emit (events.js:182:13)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.677541199Z"} {"log":" at Request.\u003canonymous\u003e (/opt/magic_mirror/modules/MMM-NOAA3/node_modules/request/request.js:1161:10)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.680968787Z"} {"log":" at Request.emit (events.js:182:13)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.684091324Z"} {"log":" at IncomingMessage.\u003canonymous\u003e (/opt/magic_mirror/modules/MMM-NOAA3/node_modules/request/request.js:1083:12)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.689258674Z"} {"log":" at Object.onceWrapper (events.js:273:13)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.692843212Z"} {"log":" at IncomingMessage.emit (events.js:187:15)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.699066149Z"} {"log":" at endReadableNT (_stream_readable.js:1094:12)\r\n","stream":"stdout","time":"2020-06-13T04:21:50.701166187Z"}

I have a problem with this module. The module itself runs fine, but this message is breaking my magic mirror, as it is flooding my log and creating huge docker logs files (4.1 tb). How do I suppress this message or make it go away? git pull & npm install do nothing Running docker image. {"log":"[2020-06-12 23:12:23.838] [ERROR] TypeError: Cannot read property 'retrieveCurrentlyPlaying' of undefined\r\n","stream":"stdout","time":"2020-06-13T04:12:23.841885149Z"} {"log":" at Class.retrieveCurrentSong (/opt/magic_mirror/modules/MMM-NowPlayingOnSpotify/node_helper.js:29:20)\r\n","stream":"stdout","time":"2020-06-13T04:12:23.847190262Z"} {"log":" at Class.socketNotificationReceived (/opt/magic_mirror/modules/MMM-NowPlayingOnSpotify/node_helper.js:22:14)\r\n","stream":"stdout","time":"2020-06-13T04:12:23.859870587Z"} {"log":" at Socket.\u003canonymous\u003e (/opt/magic_mirror/js/node_helper.js:113:11)\r\n","stream":"stdout","time":"2020-06-13T04:12:23.862610449Z"} {"log":" at Socket.emit (events.js:182:13)\r\n","stream":"stdout","time":"2020-06-13T04:12:23.864744237Z"} {"log":" at /opt/magic_mirror/node_modules/socket.io/lib/socket.js:528:12\r\n","stream":"stdout","time":"2020-06-13T04:12:23.867760099Z"} {"log":" at process.internalTickCallback (internal/process/next_tick.js:70:11)\r\n","stream":"stdout","time":"2020-06-13T04:12:23.868429924Z"}

@reemster you only do ONE to install also u should delete the existing MagicMirror folder first. the script is doing new install

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)