Read the statement by Michael Teeuw here.
MMM-CalendarExt cant get the calendar to show
-
okay here it is
pm2 log mmpi@MagicMirror:~ $ pm2 log mm --lines 1000 [TAILING] Tailing last 1000 lines for [mm] process (change the value with --lines option) /home/pi/.pm2/logs/mm-error-0.log last 1000 lines: 0|mm | 0|mm | npm ERR! Linux 4.9.52-v7+ 0|mm | npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start" 0|mm | npm ERR! node v6.11.4 0|mm | npm ERR! npm v3.10.10 0|mm | npm ERR! code ELIFECYCLE 0|mm | npm ERR! magicmirror@2.1.3 start: `sh run-start.sh` 0|mm | npm ERR! Exit status 1 0|mm | npm ERR! 0|mm | npm ERR! Failed at the magicmirror@2.1.3 start script 'sh run-start.sh'. 0|mm | npm ERR! Make sure you have the latest version of node.js and npm installed. 0|mm | npm ERR! If you do, this is most likely a problem with the magicmirror package, 0|mm | npm ERR! not with npm itself. 0|mm | npm ERR! Tell the author that this fails on your system: 0|mm | npm ERR! sh run-start.sh 0|mm | npm ERR! You can get information on how to open an issue for this project with: 0|mm | npm ERR! npm bugs magicmirror 0|mm | npm ERR! Or if that isn't available, you can get their info via: 0|mm | npm ERR! npm owner ls magicmirror 0|mm | npm ERR! There is likely additional logging output above. 0|mm | 0|mm | npm ERR! Please include the following file with any support request: 0|mm | npm ERR! /home/pi/MagicMirror/npm-debug.log 0|mm | [811:1006/062246.323684:FATAL:bus.cc(1197)] D-Bus connection was disconnected. Aborting. 0|mm | #0 0x00000139f0c0 0|mm | #1 0x0000013ae0be 0|mm | #2 0x0000009d3172 0|mm | 0|mm | [812:1006/064303.600583:FATAL:bus.cc(1197)] D-Bus connection was disconnected. Aborting. 0|mm | #0 0x00000139f0c0 0|mm | #1 0x0000013ae0be 0|mm | #2 0x0000009d3172 0|mm | 0|mm | [807:1006/065119.128269:FATAL:bus.cc(1197)] D-Bus connection was disconnected. Aborting. 0|mm | #0 0x00000139f0c0 0|mm | #1 0x0000013ae0be 0|mm | #2 0x0000009d3172 0|mm | /home/pi/.pm2/logs/mm-out-0.log last 1000 lines: 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXWLP] SCANNING: /home/ 0|mm | [DBXWLP] SCANNING: /home/Apps/ 0|mm | [DBXWLP] SCANNING: /home/Apps/background_pi_magicMirror 0|mm | [DBXWLP] SCANNING: /Apps/background_pi_magicMirror 0|mm | [DBXWLP] SCANNING: /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXWLP] SCANNING: /home/Apps/background_pi_magicMirror 0|mm | [DBXWLP] SCANNING: /Apps/background_pi_magicMirror 0|mm | [DBXWLP] SCANNING: /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXWLP] DOWNLOAD_ERROR /background_pi_magicMirror 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox. 0|mm | [DBXPIC] No scanned images in Dropbox.and
npm, start devpi@MagicMirror:~ $ npm start dev npm ERR! Linux 4.9.52-v7+ npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start" "dev" npm ERR! node v6.11.4 npm ERR! npm v3.10.10 npm ERR! path /home/pi/package.json npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent npm ERR! Please include the following file with any support request: npm ERR! /home/pi/npm-debug.log -
@glitchgod
First. All of error messages[DBX...]are not related with CalendarExt. For clearer test, disable DropboxWallpaper.(and all other modules except for CalendarExt)
Second,npm start devshould be run onyour magic mirror directory(It might be~/MagicMirror, not~/)
So, Just check again.cd ~/MagicMirror npm start devIt could show your MM and an additional window for developer console. You might find error mark (red circled X mark and numbers, if exists). In that case, move to tab
Console, you could see errors. -
@Sean said in MMM-CalendarExt cant get the calendar to show:
r
alright ran the dev mode in the proper directory
the screen that showed up looks like the Chrome’s “F12” optionThere were no errors or issues highlighed or showing the X on them, however the calendar somewhat showed up in a weird way after i commented out everything but the calendar.
It showed up in the bottom left with only "Tuesday /Wensday/ Thurday/ Friday " and a single calendar line.
Im still running with the Default script
{ module: 'MMM-CalendarExt', position: "top_left", config: { calendars: [ { url: "http://mlb.am/tix/mariners_schedule_full" } ] } },SSSoo some progress
After letting the SSH run for a few minutes an error did show up
Starting MagicMirror: v2.1.3 Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: MMM-CalendarExt All module helpers loaded. Starting server on port 8080 ... Server started ... Connecting socket for: MMM-CalendarExt Sockets connected & modules started ... Whoops! There was an uncaught exception... { Error: listen EADDRINUSE 127.0.0.1:8080 at Object.exports._errnoException (util.js:1050:11) at exports._exceptionWithHostPort (util.js:1073:20) at Server.setupListenHandle [as _listen2] (net.js:1263:14) at listenInCluster (net.js:1304:12) at doListen (net.js:1428:7) at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:10) code: 'EADDRINUSE', errno: 'EADDRINUSE', syscall: 'listen', address: '127.0.0.1', port: 8080 } MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues Launching application. pm2 log mm -
Ok, we are progressed.
Try this. And you can know what was problem. ;)config: { system: { show: ['month'], }, views: { month: { position:'bottom_bar', }, }, calendars :[ { url:"http://mlb.am/tix/mariners_schedule_full" }, ] } -
Ok. I tell you the truth.
there is no more schedule for Seatle Mariners in this month. That is why empty frame is shown.
Try this url : https://ics.fixtur.es/v2/eintracht-frankfurt.icsAnd, Port error is not related with modules (I think)
-
Alright it’s up and running.
Thank you Sean
the steep by steep fix you have given was excellent :) -
After re enabling all the modules it seems
“MMM-ethereum”
causes it not to show up.
The way i found out is commenting out each module one by oneJust for future
-
This post is deleted! -
@Sean said in MMM-CalendarExt cant get the calendar to show:
pm2 log mm
So i set a a new installation of MM 2.1.3
i can’t get the calendar to show up.pi@raspberrypi:~ $ pm2 log mm [TAILING] Tailing last 15 lines for [mm] process (change the value with --lines option) /home/pi/.pm2/logs/mm-error-0.log last 15 lines: 0|mm | ERROR! Could not validate main module js file. 0|mm | /home/pi/MagicMirror/modules/MMM-CalendarExt/MMM-CalendarExt.js:182 0|mm | addCalendars: async function() { 0|mm | ^^^^^^^^ 0|mm | SyntaxError: Unexpected token function 0|mm | at Object.exports.runInThisContext (vm.js:76:16) 0|mm | at Module._compile (module.js:528:28) 0|mm | at Object.Module._extensions..js (module.js:565:10) 0|mm | at Module.load (module.js:473:32) 0|mm | at tryModuleLoad (module.js:432:12) 0|mm | at Function.Module._load (module.js:424:3) 0|mm | at Module.require (module.js:483:17) 0|mm | at require (internal/module.js:20:19) 0|mm | at Class.loadModuleDefaultConfig (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:254:17) 0|mm | at /home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:211:10 /home/pi/.pm2/logs/mm-out-0.log last 15 lines: 0|mm | Connecting socket for: MMM-NOAA 0|mm | Starting module: MMM-NOAA 0|mm | Connecting socket for: MMM-MyCommute 0|mm | ====================== Starting node_helper for module [MMM-MyCommute] 0|mm | Connecting socket for: MMM-SystemStats 0|mm | Connecting socket for: newsfeed 0|mm | Starting module: newsfeed 0|mm | Connecting socket for: MMM-CalendarExt 0|mm | Sockets connected & modules started ... 0|mm | Launching application. 0|mm | Create new calendar fetcher for url: xxx - Interval: 300000 0|mm | Create new calendar fetcher for url: http://i.cal.to/ical/61/nrw/feiertage/71e91ccb.83fad41c-d19fda68.ics - Interval: 300000 0|mm | Create new news fetcher for url: http://www.tagesschau.de/xml/rss2 - Interval: 300000 0|mm | [RCREPO] Repository scanning... 0|mm | [RCREPO] modules.json is updated.pi@raspberrypi:~/MagicMirror $ npm start dev > magicmirror@2.1.3 start /home/pi/MagicMirror > sh run-start.sh "dev" Starting MagicMirror: v2.1.3 Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: MMM-Remote-Control Initializing new module helper ... Module helper loaded: MMM-Remote-Control-Repository Initializing new module helper ... Module helper loaded: MMM-PIR-Sensor Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. Initializing new module helper ... Module helper loaded: calendar Initializing new module helper ... Module helper loaded: MMM-NOAA Initializing new module helper ... Module helper loaded: MMM-MyCommute Initializing new module helper ... Module helper loaded: MMM-SystemStats No helper found for module: MMM-GoogleMapsTraffic. Initializing new module helper ... Module helper loaded: newsfeed Initializing new module helper ... Module helper loaded: MMM-CalendarExt All module helpers loaded. Starting server on port 8080 ... You're using a full whitelist configuration to allow for all IPs Server started ... Connecting socket for: MMM-Remote-Control Starting node helper for: MMM-Remote-Control Connecting socket for: MMM-Remote-Control-Repository Connecting socket for: MMM-PIR-Sensor Connecting socket for: updatenotification Connecting socket for: calendar Starting node helper for: calendar Connecting socket for: MMM-NOAA Starting module: MMM-NOAA Connecting socket for: MMM-MyCommute ====================== Starting node_helper for module [MMM-MyCommute] Connecting socket for: MMM-SystemStats Connecting socket for: newsfeed Starting module: newsfeed Connecting socket for: MMM-CalendarExt Sockets connected & modules started ... Whoops! There was an uncaught exception... { Error: listen EADDRINUSE 0.0.0.0:8080 at Object.exports._errnoException (util.js:1026:11) at exports._exceptionWithHostPort (util.js:1049:20) at Server._listen2 (net.js:1253:14) at listen (net.js:1289:10) at net.js:1399:9 at _combinedTickCallback (internal/process/next_tick.js:77:11) at process._tickCallback (internal/process/next_tick.js:98:9) at Module.runMain (module.js:592:11) at run (bootstrap_node.js:402:7) at startup (bootstrap_node.js:157:9) code: 'EADDRINUSE', errno: 'EADDRINUSE', syscall: 'listen', address: '0.0.0.0', port: 8080 } MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection? If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues Launching application. ERROR! Could not validate main module js file. /home/pi/MagicMirror/modules/MMM-CalendarExt/MMM-CalendarExt.js:182 addCalendars: async function() { ^^^^^^^^ SyntaxError: Unexpected token function at Object.exports.runInThisContext (vm.js:76:16) at Module._compile (module.js:528:28) at Object.Module._extensions..js (module.js:565:10) at Module.load (module.js:473:32) at tryModuleLoad (module.js:432:12) at Function.Module._load (module.js:424:3) at Module.require (module.js:483:17) at require (internal/module.js:20:19) at Class.loadModuleDefaultConfig (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:254:17) at /home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:211:10Any idea?
-
@cruunnerr
Async functions are not supported by Node versions older than version 7.6. -
@Sean
U think i need to do an update of node?So u wanna hear a fun fact?
On my Mirror itself nothings shows up.
BUT, when i go to the MagicMirror website via browser or the MMM-RemoteControl it is right there!Can anyone explain that?
the config i test it:
{ module: 'MMM-CalendarExt', position: "bottom_bar", config: { system: { show: ['month'], }, views: { month: { position:'bottom_bar', }, }, calendars :[ { url: "https://ics.fixtur.es/v2/eintracht-frankfurt.ics" }, ] } },
-
I just ran an update this morning and I am having the exact problem.
Same error, and it works through a web browser…
Have you found a resolution?
Did updating node help? If so, how do you update it?
Thank you for your help,
Major -
I’m having the same issue for the past few days.
Updated to the latest release of MM today hoping it would solve it somehow but no luck.
-
Quick update. I hacked around some updates to Node, npm etc, but nothing seemed to work.
So I removed the async and the await from the addCalendars function so it looks something like this (file: MMM-CalendarExt.js)
addCalendars: function() { var self = this for (var c in this.CurrentConfigs.calendars) { self.addCalendar(self.CurrentConfigs.getCalConfig(c)) sleep(1000) } },Seems to work for now. But looking back through github I don’t see that these are recent additions so I don’t know why this started failing now. Hopefully somebody smarter than I will figure it out.
-
Significantly Changes in the new update is the use of electron 1.4.15.
I used it already before the update, but i don’t want to update (cause of the CPU trouble thing…) to check if it is the reason.
but that is the only thing that comes to my mind, since you both got the problem when updating to the newest MM-Version -
I doubt MM has downgraded its node version of electron for some reason.
Unfortunately, ‘async function’ is not working on the lower version of node. I think that is the reason for this issue.
I’ll check and patch this for some time. Sorry, I should do my job first before this. Plz wait for a while. -
@Sean
If I read this right:
Changed
* Calender week is now handled with a variable translation in order to move number language specific. * Reverted the Electron dependency back to 1.4.15 since newer version don’t seem to work on the Raspberry Pi very well.MM has indeed downgraded…
-
yeah, its all discussed in this thread: https://forum.magicmirror.builders/topic/4684/electron-cpu-usage?page=1
I had the problem, too. CPU Usage above 80%.
When i downgrade to electron 1.4.15 the CPU usage went to nearly 0% !But then i went to the Problem that the CalendarExt Module only shows in an external web browser and not on the MM itself.
Think we have to hope, that Sean will find a solution. :D
(Or the electron Problem is gone…) -
@cruunnerr Did you try the solution I suggested here? https://forum.magicmirror.builders/topic/6047/calendar-module-won-t-show-all-events/4
-
Yeah i saw this and tried it. Works great :) Thank you
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login