Posts made by drfukc

drfukc

Hi,
I am aware that there are multiple threads on troubleshooting the Google Assistant, but I did not find one on systematical troubleshooting. How do I test what is not working? Below please find my attempts, which may be a first start, but did not identify the root cause.
Now I am stuck with my MMM-AssistantMk2 and MMM-Hotword installation and configuration and look for step-by-step troubleshooting. When I started the Google Assistant installation, all installed MM modules are working fine, so I imaged the SD-card for an easy fallback.

My steps have been:

Installing MMM-AssistantMk2 + MMM-Hotword
Now I get a flashing bubble on the mirror and whenever I say the magic word: “smart-mirror” the string [“smart-mirror”] shows up next to the bubble on my Magic Mirror, but nothing seems to happen after (similar to the image on this page, just my hotword is not “Computer” but “smart mirror”: https://github.com/eouia/MMM-Hotword)

Maybe most of the things are successfully implemented but how do I get it to work?
I have no clue why or where it hangs, what are steps to identify where it stucks?

So far I have checked the following:

Version checks::
pi@raspberrypi:~/MagicMirror $ uname -a
Linux raspberrypi 4.19.34-v7+ #1211 SMP Mon Apr 8 22:56:37 BST 2019 armv7l GNU/L

pi@raspberrypi:~/MagicMirror $ vcgencmd version
Mar 27 2019 15:45:53
Copyright © 2012 Broadcom
version 2e98b31d18547962e564bdf88e57b3df7085c29b (clean) (release) (start)

pi@raspberrypi:~/MagicMirror $ node -v && npm -v
v10.15.3
6.9.0

These commands resulted in long outputs, but did not point me to anything useful:
pi@raspberrypi:~/MagicMirror/config $ npm start dev
pi@raspberrypi:~ $ dmesg -x -d -T

Audio checks:

Speaker check:
pi@raspberrypi:~ $ aplay -l
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: ALSA [bcm2835 ALSA], Gerät 0: bcm2835 ALSA [bcm2835 ALSA]
Sub-Geräte: 7/7
Sub-Gerät #0: subdevice #0
Sub-Gerät #1: subdevice #1
Sub-Gerät #2: subdevice #2
Sub-Gerät #3: subdevice #3
Sub-Gerät #4: subdevice #4
Sub-Gerät #5: subdevice #5
Sub-Gerät #6: subdevice #6
Karte 0: ALSA [bcm2835 ALSA], Gerät 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Sub-Geräte: 1/1
Sub-Gerät #0: subdevice #0

Microphone check:
pi@raspberrypi:~ $ arecord -l
**** Liste der Hardware-Geräte (CAPTURE) ****
Karte 1: AK5371 [AK5371], Gerät 0: USB Audio [USB Audio]
Sub-Geräte: 0/1
Sub-Gerät #0: subdevice #0

Audio Check:
arecord -D plughw:1,0 -d 3 test.wav && aplay test.wav
I hear myself speaking when the pm2 is stopped

Google Credentials and Setup check:
pi@raspberrypi:~/MagicMirror/modules/MMM-AssistantMk2 $ node auth_and_test.js
Type your request:
googlesamples-assistant-pushtotalk --project-id magicmirror-12345 --device-model-id magicmirror-12345-magicmirror-123456
Assistant Response:
Conversation Complete

This section highlights some findings:

pi@raspberrypi:~/MagicMirror $ npm run config:check

magicmirror@2.10.1 config:check /home/pi/MagicMirror
node tests/configs/check_config.js

Checking file… /home/pi/MagicMirror/config/config.js
Line 56 col 56 ‘arrow function syntax (=>)’ is only available in ES6 (use ‘esversion: 6’).
Line 57 col 55 Missing semicolon.

Note: fixing the [“Line 57 col 55 Missing semicolon.“]-issue does not make a difference, I copied-and-pasted this part from here: https://github.com/makepluscode/rpi-tutorial-advanced/tree/master/008-raspbian-magicmirror-google-assistant-latest
The audio/mic-settings in this sample seem to match my setup?

Does anybody have any idea what the next appropriate steps are to find where it hangs?
Any help is very much appreciated.

Cheers
Bob

drfukc

Hi all,
I feel quite happy with my Google Maps Traffic module but would like to increase the level of map details.
Some streets do not show, they are not displayed due to the zoom level.

Question:
Is there any (hidden?) trigger I can use to modify the level of details without changing the map-size or zoom-level?

drfukc

@sdetweil
yes, that’s the case, the module is running fine until it turns the monitor black (after several hours).
There are more people in different threads having the same issue.
The module author does not seem to respond.
My workaround is a regular cron job restarting the MagicMirror.

drfukc

I have the same issue. When I boot up the Magic Mirror in debug mode npm start dev & but the Chrome console tab tells me this nasty thing:

"You have included the Google Maps JavaScript API multiple times on this page." 
"This may cause unexpected errors."

However, everything looks perfectly nice on my MagicMirror.
All modules are successfully loaded, including “MMM-GoogleMapsTraffic”.

But on the next day, the latest my screen is entirely black.
It’s exactly the same thing as reported in this thread.

drfukc

@Mykle1

I am successfully running the MMM-ImageSlideshow module, but the images in my image directory are constantly changing. Looks like the images are all loaded from cached folder information.

How would I update the Dom to get my new images on the mirror?

Cheers

drfukc

Hi,
when trying to install the MMM-ImageFileWatcher module I get a warning that fsevents is not supported on this platform:

pi@raspberrypi:~ $ cd MagicMirror/
pi@raspberrypi:~/MagicMirror $ cd modules
pi@raspberrypi:~/MagicMirror/modules $ git clone https://github.com/basknol/MMM-ImageFileWatcher.git
Klone nach 'MMM-ImageFileWatcher' ...
remote: Enumerating objects: 33, done.
remote: Total 33 (delta 0), reused 0 (delta 0), pack-reused 33
Entpacke Objekte: 100% (33/33), Fertig.
pi@raspberrypi:~/MagicMirror/modules $ cd MMM-ImageFileWatcher/
pi@raspberrypi:~/MagicMirror/modules/MMM-ImageFileWatcher $ npm install
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

added 134 packages from 105 contributors and audited 2114 packages in 23.432s
found 0 vulnerabilities

pi@raspberrypi:~/MagicMirror/modules/MMM-ImageFileWatcher $

Is there any known solution for this?
Cheers

drfukc

Now I received feedback from Google, that confirms 28,000 MagicMirror map loads each month based on the $200 credit:

"Thank you for contacting Google Maps Platform Technical Support. My name is Xxx and I will gladly help you with your inquiry today.
Upon close inspection of your account, indeed, you have the Maps Javascript API correctly enabled.
Now, if you are using it to call Dynamic Maps, those 28,000 map loads are included within the $200 USD free monthly credit. Or, in other words, the $200 USD credit pays for the 28,000 map loads, ie, you get up to 28,000 map loads, for all intents and purposes, for free every month.

If you exceed the $200 threshold, then yes, your account will be charged according to the pricing sheet you will find at https://cloud.google.com/maps-platform/pricing/sheet/
That means that the monthly volume range above the 28,000 free map loads is 0.007 USD per each map load (or USD7 per 1000 map loads) up to 100,000 map loads.

If you want to make sure that you do not exceed the free monthly $200 threshold, you can cap your API usage [1] to a certain number of calls per day and/or set budget alerts [2].
We also provide an online calculator to estimate your usage at https://mapsplatformtransition.withgoogle.com/calculator.

I hope you find this information useful, and if you need further assistance or clarification on the documentation provided, please do not hesitate to let me know. I am happy to help!

Kind regards,
Xxx"

drfukc

Hi,
I have installed and configured the Google MMM-GoogleMapsTraffic module, but feel lost in the Google pricing concept.

Question:
Will I ever be charged by Google using the MMM-GoogleMapsTraffic module with the standard values?
The module is just calling a simple map with traffic information but no routing

I checked the Google pricing web-page here:
https://cloud.google.com/maps-platform/pricing/sheet/?_ga=2.265062860.216645122.1555664995-842763991.1553803912

My best guess is that I am using the Maps JavaScript API to call Google Dynamic Maps and I get 28000 loads for free each month.
In addition I get $200 credit to purchase additional loads. Since 100000 loads cost $7 I get another 2800000 loads on top.
In total I get 28000 + 2800000 = 2828000 for free each month.

Is my understanding correct?, hence I do not have to pay since Google already provides sufficient usage?

drfukc

@sdetweil
if you are the author of the RMV module its perfect, if you are not the author of this module it is perfect as well.
However, please accept that in my case the “MMM-RMV.js” requires auditing, otherwise it will not work.
I would be more than pleased if all editing can be done in the “config.js”, at least in my case it does not work.
The default values do not seem to be overriden.
Any idea why?

drfukc

@sdetweil
I have not edited the code, I have created a pull-request.
All I can see it that it is working in my environment with my proposed change but not with the default values.
In case other users have a similar issue, I suggest to give it a try.

drfukc

@sdetweil
I am unsure if we are talking about the same thing.
I understand you are referring to this file:

/home/pi/MagicMirror/config/config.js

I see the issue in this file:

/home/pi/MagicMirror/modules/MMM-RMV/MMM-RMV.js

To get it to work, both files need to be edited in the current version.

drfukc

@all
now I found the issue and created a Github pullrequest for the RMV module:

In addition to the regular config file, RMV ships by default with another file:
/home/pi/MagicMirror/modules/MMM-RMV/MMM-RMV.js

In this file you will find below variables that are prefilled with data that will in most cases not work for the average user:

stationId: '', // update required here
fDestination1: '', // update required here
fDestination2: '', // update required here

These variables need updates.
After a successful update, the RMV module does work nicely even with buses :-)

drfukc

@sdetweil
Thanks a lot, - this helped :-) , it is so much easier if things are done right straight from the beginning :-D

In addition I also found the root cause for above reported “EADDRINUSE” error.
Simple again: I have enabled MagicMirror autostart in /home/pi/MagicMirror/installers/mm.sh, but don’t see it since I use a Remote Desktop connection (RDP) that gives me a different X-Window in comparison to the native Raspberry desktop.
Now launching Magic Mirror a second time on a different desktop and the same port causes the issue.
Since I disabled MM autostart Magic Mirror boots up without these errors.
Maybe I should get back from XRDP and switch to the preinstalled VNC to avoid having multiple desktops.

Again, thanks a lot for your support :-)

drfukc

Thanks for your advise. After launching the mirror I do a pm2 list with the following result:

pi@raspberrypi:~/MagicMirror $ pm2 list
+-------------------------------------------------------+
¦ Name        ¦ id ¦ mode ¦ status ¦ ? ¦ cpu ¦ memory   ¦
+-------------+----+------+--------+---+-----+----------¦
¦ MagicMirror ¦ 0  ¦ fork ¦ online ¦ 0 ¦ 0%  ¦ 2.5 MB   ¦
+-------------------------------------------------------+
 Use `pm2 show <id|name>` to get more details about an app

With this information I stop the MagicMirror by the following command: pm2 stop 0

pi@raspberrypi:~ $ pm2 stop 0
[PM2] Applying action stopProcessId on app [0](ids: 0)
[PM2] [MagicMirror](0) ?
+------------------------------------------------------+
¦ Name        ¦ id ¦ mode ¦ status  ¦ ? ¦ cpu ¦ memory ¦
+-------------+----+------+---------+---+-----+--------¦
¦ MagicMirror ¦ 0  ¦ fork ¦ stopped ¦ 0 ¦ 0%  ¦ 0 B    ¦
+------------------------------------------------------+
Use `pm2 show <id|name>` to get more details about an app

By surprise the running MagicMirror survives and I kill the Electron instance with kill
After the MagicMirror instance is terminated I relaunch MagicMirror again with npm start &
The funny thing is that the naughty EADDRINUSE message is gone by now, but the calendar is still not working:

pi@raspberrypi:~/MagicMirror $ npm start &
[2] 1279
[1]   Fertig                  npm start
pi@raspberrypi:~/MagicMirror $ 
> magicmirror@2.7.1 start /home/pi/MagicMirror
> sh run-start.sh

Starting MagicMirror: v2.7.1
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.
Initializing new module helper ...
Module helper loaded: calendar
Initializing new module helper ...
Module helper loaded: newsfeed
All module helpers loaded.
Starting server on port 8081 ... 
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started ...
Launching application.
Create new calendar fetcher for url: http://www.calendarlabs.com/templates/ical/US-Holidays.ics - Interval: 300000
Create new news fetcher for url: http://www.tagesschau.de/xml/rss2 - Interval: 300000

OK, as said above I have relaunched the mirror by npm start & and try to evaluate what is going on with pm2 list:

pi@raspberrypi:~ $ pm2 list
+------------------------------------------------------+
¦ Name        ¦ id ¦ mode ¦ status  ¦ ? ¦ cpu ¦ memory ¦
+-------------+----+------+---------+---+-----+--------¦
¦ MagicMirror ¦ 0  ¦ fork ¦ stopped ¦ 0 ¦ 0%  ¦ 0 B    ¦
+------------------------------------------------------+
 Use `pm2 show <id|name>` to get more details about an app

It’s funny, pm2 list tells me that the Mirror has stopped, while it is still running, but I still do not recieve any Calendar updates.
What is wrong here?

drfukc

@sdetweil
Thanks for your comment.
First I changed the port as recommended in mm/config/config.js to 8081 and gave it a reboot.
After reboot and logon I checked the network connections by sudo netstat -lnptu:

pi@raspberrypi:~ $ sudo netstat -lnptu
Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:8081          0.0.0.0:*               LISTEN      836/electron.js     
tcp6       0      0 :::21                   :::*                    LISTEN      418/vsftpd          
tcp6       0      0 ::1:3350                :::*                    LISTEN      446/xrdp-sesman     
tcp6       0      0 :::3389                 :::*                    LISTEN      461/xrdp            
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           318/avahi-daemon: r 
udp        0      0 0.0.0.0:68              0.0.0.0:*                           348/dhcpcd          
udp        0      0 0.0.0.0:47216           0.0.0.0:*                           318/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                318/avahi-daemon: r 
udp6       0      0 :::34261                :::*                                318/avahi-daemon: r

I am surprised to see Electron already listening on port 8081, though I have not started the MagicMirror.
In the next step I launch Magic Mirror by calling: npm start &

Unfortunately I see again a EADDRINUSE message (port 8081):

Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started ...
Whoops! There was an uncaught exception...
{ Error: listen EADDRINUSE 127.0.0.1:8081
    at Server.setupListenHandle [as _listen2] (net.js:1330:14)
    at listenInCluster (net.js:1378:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
  errno: 'EADDRINUSE',
  code: 'EADDRINUSE',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 8081 }
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.

While the mirror is running I execute again sudo netstat -lnptu and get:

pi@raspberrypi:~/MagicMirror $ sudo netstat -lnptu
Aktive Internetverbindungen (Nur Server)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:8081          0.0.0.0:*               LISTEN      888/electron.js     
tcp6       0      0 :::21                   :::*                    LISTEN      435/vsftpd          
tcp6       0      0 ::1:3350                :::*                    LISTEN      450/xrdp-sesman     
tcp6       0      0 :::3389                 :::*                    LISTEN      465/xrdp            
udp        0      0 0.0.0.0:42644           0.0.0.0:*                           318/avahi-daemon: r 
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           318/avahi-daemon: r 
udp        0      0 0.0.0.0:68              0.0.0.0:*                           354/dhcpcd          
udp6       0      0 :::42148                :::*                                318/avahi-daemon: r 
udp6       0      0 :::5353                 :::*                                318/avahi-daemon: r

This is strange. The launch of the mirror npm start & tells me a multiple use of the port 8080 or 8081 (whatever it set in config.js) but netstat -lnptu does not know anything about a duplicate use.

As advised I also added below line right after if (event.type === “VEVENT”) { in ftp://192.168.178.36/home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js

console.log("have event title="+event.summary);

Unfortunately the console outcome again is: “EADDRINUSE”

Initializing new module helper ...
Module helper loaded: calendar
Initializing new module helper ...
Module helper loaded: newsfeed
All module helpers loaded.
Starting server on port 8081 ... 
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started ...
Whoops! There was an uncaught exception...
{ Error: listen EADDRINUSE 127.0.0.1:8081
    at Server.setupListenHandle [as _listen2] (net.js:1330:14)
    at listenInCluster (net.js:1378:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
  errno: 'EADDRINUSE',
  code: 'EADDRINUSE',
  syscall: 'listen',
  address: '127.0.0.1',
  port: 8081 }
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.

I feel a little bit lost … … …

drfukc

@sdetweil

Hi Sam,
the calendar entry I use for testing is the standard URL:

url: "webcal://www.calendarlabs.com/templates/ical/US-Holidays.ics"

As advised by you I searched up-and-down my calendarfetcher.js in:
/home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js

I can find the following string: if (event.type === “VEVENT”) {
But I cannot even find substring to uncomment such like this: console.log("have or event title or
Hence there seems to be nothing to uncomment

I rather believe my issue has something to do with to many Electron instances that kill several moduls.
Maybe you have an idea for this:

I boot up my raspberry 3b
Execute ‘ps -a’ to check the running processes
‘ps -a’ returns ‘ps’ as the only running processes
launching the mirror: ‘npm start &’
the console tells me uncaught exception since EADDRINUSE is already in use:

magicmirror@2.7.1 start /home/pi/MagicMirror
sh run-start.sh

Starting MagicMirror: v2.7.1
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.
Initializing new module helper ...
Module helper loaded: calendar
Initializing new module helper ...
Module helper loaded: newsfeed
All module helpers loaded.
Starting server on port 8080 ... 
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started ...
Whoops! There was an uncaught exception...
{ Error: listen EADDRINUSE 127.0.0.1:8080
    at Server.setupListenHandle [as _listen2] (net.js:1330:14)
    at listenInCluster (net.js:1378:12)
    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
  errno: 'EADDRINUSE',
  code: '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

Now I recheck my running processes and see *four instances of Electron. According to another thread it looks like I run two instances of MagicMirror in parallel, that have a conflict with each other and causing this EADDRINUSE message:

PID TTY          TIME CMD
 1176 pts/0    00:00:01 npm
 1187 pts/0    00:00:00 sh
 1188 pts/0    00:00:00 sh
 1189 pts/0    00:00:00 node
 1196 pts/0    00:00:30 electron
 1198 pts/0    00:00:00 electron
 1236 pts/0    00:00:00 electron
 1238 pts/0    00:00:15 electron
 1305 pts/1    00:00:00 ps

Checking PM2 by ‘pm2 list’ gives me only one instance:

pi@raspberrypi:~ $ pm2 list
+-------------------------------------------------------+
¦ Name        ¦ id ¦ mode ¦ status ¦ ? ¦ cpu ¦ memory   ¦
+-------------+----+------+--------+---+-----+----------¦
¦ MagicMirror ¦ 0  ¦ fork ¦ online ¦ 0 ¦ 0%  ¦ 2.5 MB   ¦
+-------------------------------------------------------+

For more details I try pm2 show 0

pi@raspberrypi:~ $ pm2 show 0
 Describing process with id 0 - name MagicMirror 
+--------------------------------------------------------------+
¦ status            ¦ online                                   ¦
¦ name              ¦ MagicMirror                              ¦
¦ version           ¦ 2.7.1                                    ¦
¦ restarts          ¦ 0                                        ¦
¦ uptime            ¦ 16m                                      ¦
¦ script path       ¦ /home/pi/MagicMirror/installers/mm.sh    ¦
¦ script args       ¦ N/A                                      ¦
¦ error log path    ¦ /home/pi/.pm2/logs/MagicMirror-error.log ¦
¦ out log path      ¦ /home/pi/.pm2/logs/MagicMirror-out.log   ¦
¦ pid path          ¦ /home/pi/.pm2/pids/MagicMirror-0.pid     ¦
¦ interpreter       ¦ bash                                     ¦
¦ interpreter args  ¦ N/A                                      ¦
¦ script id         ¦ 0                                        ¦
¦ exec cwd          ¦ /home/pi/MagicMirror                     ¦
¦ exec mode         ¦ fork_mode                                ¦
¦ node.js version   ¦ N/A                                      ¦
¦ node env          ¦ N/A                                      ¦
¦ watch & reload    ¦ ?                                        ¦
¦ unstable restarts ¦ 0                                        ¦
¦ created at        ¦ 2019-04-06T11:57:10.685Z                 ¦
+--------------------------------------------------------------+
 Revision control metadata 
+---------------------------------------------------------------------+
¦ revision control ¦ git                                              ¦
¦ remote url       ¦ https://github.com/MichMich/MagicMirror.git      ¦
¦ repository root  ¦ /home/pi/MagicMirror                             ¦
¦ last update      ¦ 2019-04-15T06:53:55.840Z                         ¦
¦ revision         ¦ b508a629e8a727358f1b88e3c7df842d14669ec4         ¦
¦ comment          ¦ Merge pull request #1632 from MichMich/fix-2.7.1 ¦
¦                  ¦                                                  ¦
¦                  ¦ Fix package.json version number.                 ¦
¦ branch           ¦ master                                           ¦
+---------------------------------------------------------------------+

Any ideas?

drfukc

Hi Dommer,
Quite similar with me. I have a fresh Raspberry installation on my Pi-3B, the only additional packages installed are vsftpd (FTP-tool) and xrdp (RDP-server to allow Windows Remote Desktop Connections). On this fresh installation I have installed MagicMirror² and default Weather- and News app are working fine receiving live data.
For some reason the calendar app does not work and I get the same error message for the calendar module as you in my log-file:

./home/pi/.pm2/logs/MagicMirror-error.log

ATTENTION: default value of option force_s3tc_enable overridden by environment.
TypeError: Cannot read property 'length' of undefined
    at eventDate (/home/pi/MagicMirror/modules/default/**calendar/calendarfetcher.js:69:25)
    at /home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js:90:22
    at Request._callback (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:11:5)
    at Request.self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
    at Request.emit (events.js:182:13)
    at Request.<anonymous> (/home/pi/MagicMirror/node_modules/request/request.js:1157:10)
    at Request.emit (events.js:182:13)
    at IncomingMessage.<anonymous> (/home/pi/MagicMirror/node_modules/request/request.js:1079:12)
    at Object.onceWrapper (events.js:273:13)
    at IncomingMessage.emit (events.js:187:15)

I reinstalled from scratch on another SD-card with the same result.

drfukc

Hi Sam,
thanks for your support, but unfortunately this takes me to the next issue when executing:

pi@magicmirror:~ $ npm -v
6.9.0

pi@magicmirror:~/MagicMirror $ npm install -g npm
npm WARN checkPermissions Missing write access to /usr/lib/node_modules
npm ERR! path /usr/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access

After, I changed permissions for /usr/lib/node_modules, but it simply took me to the next error.
I think I will re-start from scratch.
Cheers
ukc

drfukc

@sdetweil
partially it worked though the upgrade still terminates with this error message after running “sudo npm install” in the MM directory and all external modules that have a package.json file.
However, all of these have prompted me that they are already up-to-date.

These are my steps:

pi@magicmirror:~/MagicMirror $ sudo npm install
npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/eslint-8983ee3d/LICENSE'
npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/eslint-8983ee3d/README.md'

... tons of similar WARNINGS in between ... and removed here for better removed for better readability

npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/lastIndexOf.js'
npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/LICENSE'
npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/lodash.js'
npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.

npm ERR! err.code.match is not a function

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-04-05T07_27_16_446Z-debug.log

now I check “2019-04-05T07_27_16_446Z-debug.log” but unfortunately this does not help me either:

842 silly saveTree ├── valid-url@1.0.9
842 silly saveTree └─┬ walk@2.3.14
842 silly saveTree   └── foreachasync@3.0.0
843 warn acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
844 warn grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.
845 verbose stack TypeError: err.code.match is not a function
845 verbose stack     at BB.try.catch.err (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/with-tarball-stream.js:110:55)
845 verbose stack     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
845 verbose stack     at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
845 verbose stack     at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
845 verbose stack     at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
845 verbose stack     at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:690:18)
845 verbose stack     at _drainQueueStep (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:138:12)
845 verbose stack     at _drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:131:9)
845 verbose stack     at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:147:5)
845 verbose stack     at Immediate.Async.drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
845 verbose stack     at runCallback (timers.js:794:20)
845 verbose stack     at tryOnImmediate (timers.js:752:5)
845 verbose stack     at processImmediate [as _immediateCallback] (timers.js:729:5)
846 verbose cwd /home/pi/MagicMirror
847 verbose Linux 4.14.98-v7+
848 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "install"
849 verbose node v8.11.1
850 verbose npm  v6.9.0
851 error err.code.match is not a function
852 verbose exit [ 1, true ]

When opening MagicMirror it looks like I have v2.7.0 installed, since the upgrading message has disappeared and things seem functional.

However my feeling is that the upgrade is just in the middle of somewhere, though the mirror is working.

Cheers
ukc

drfukc

Hi MagicMirror fans,
I try to update my v2.6.0 installation to v2.7.0 with executing the following steps:

sudo apt-get update
sudo apt-get dist-upgrade
reboot

all steps above without errors, and now from inside the MagicMirror directory:

git pull && npm install

This throws me the following errors lines:

Aktualisiere de57daa..b508a62
error: Ihre lokalen Änderungen in den folgenden Dateien würden durch den Merge
überschrieben werden:
	package-lock.json
	vendor/package-lock.json
Bitte committen oder stashen Sie Ihre Änderungen, bevor sie mergen.

Please, commit your changes or stash them before you can merge.

Abbruch

Looks like a simple git issue, but what are the recommended steps to solve this issue?
How do I commit my changes?

running this command?

git commit -m

Hope you can help :-)

Cheers
ukc