Posts made by MyMirror

MyMirror

@mickecarlsson
Thanks for your hint.

i actually had 2 blank lines at the end of the list.
But nothing changed, no matter if there were 2, 1 or no blank lines at the end of the list (not even after a restart of the MM or of the whole Pi.

Jens

MyMirror

@sdetweil

And the output of your script (test run):

pi@MM3:~/MagicMirror $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
No LSB modules are available.

doing test run = true, NO updates will be applied!

update log will be in /home/pi/MagicMirror/installers/upgrade.log
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v16.9.1
Installed Node version: v16.13.2
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V7.11.2
Installed npm version: V8.1.2
No npm upgrade necessary.

saving custom.css
upgrading from version 2.18.0 to 2.18.0
fetching latest revisions
there are 2 local files that are different than the master repo

   installers/mm.sh
   package.json

do you want to save these files for later   (Y/n)?
Checking for modules with removed libraries
 
	 require for request in module MMM-SystemStats not found in package.json package.json for module MMM-SystemStats
 
		  bypass installing request for module MMM-SystemStats , doing test run
processing dependency changes for active modules with package.json files

processing for module MMM-MyWastePickup please wait
----------------------------------
skipped processing for MMM-MyWastePickup, doing test run
processing complete for module MMM-MyWastePickup

processing for module MMM-Fuel please wait
----------------------------------
skipped processing for MMM-Fuel, doing test run
processing complete for module MMM-Fuel

restoring custom.css
test run, restoring files stashed
pi@MM3:~/MagicMirror $

MyMirror

@sdetweil
Hi Sam,

i’ve downgraded node but without success. MMM-MyWastePickup is still “Loading”

pi@MM3:~ $ node -v
v16.13.2
pi@MM3:~ $ npm -v
8.1.2

The content (test entries) of my schedule_custom.csv:

Calendar,WeekStarting,GreenBin,Garbage,Recycling,YardWaste,ChristmasTree
Custom,02/07/22,0,1,0,0,0
Custom,02/08/22,0,0,1,0,0
Custom,03/02/22,0,1,0,0,0
Custom,03/09/22,0,1,0,0,0
Custom,03/10/22,1,0,0,0,0

Aus der Config.js:

                {
                        module: "MMM-MyWastePickup",
                        position: "top_center",
  //                    header: "M&uuml;llabfuhr",
                        header: "WASTE",
                        config: {
                                collectionCalendar: "Custom",
                                weeksToDisplay: "2"
                        }
                },

pm2 log:

pi@MM3:~/MagicMirror $ pm2 log
[TAILING] Tailing last 15 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 15 lines:
PM2        | 2022-02-06T22:00:22: PM2 log: PM2 version          : 5.1.2
PM2        | 2022-02-06T22:00:22: PM2 log: Node.js version      : 17.4.0
PM2        | 2022-02-06T22:00:22: PM2 log: Current arch         : arm
PM2        | 2022-02-06T22:00:22: PM2 log: PM2 home             : /home/pi/.pm2
PM2        | 2022-02-06T22:00:22: PM2 log: PM2 PID file         : /home/pi/.pm2/pm2.pid
PM2        | 2022-02-06T22:00:22: PM2 log: RPC socket file      : /home/pi/.pm2/rpc.sock
PM2        | 2022-02-06T22:00:22: PM2 log: BUS socket file      : /home/pi/.pm2/pub.sock
PM2        | 2022-02-06T22:00:22: PM2 log: Application log path : /home/pi/.pm2/logs
PM2        | 2022-02-06T22:00:22: PM2 log: Worker Interval      : 30000
PM2        | 2022-02-06T22:00:22: PM2 log: Process dump file    : /home/pi/.pm2/dump.pm2
PM2        | 2022-02-06T22:00:22: PM2 log: Concurrent actions   : 2
PM2        | 2022-02-06T22:00:22: PM2 log: SIGTERM timeout      : 1600
PM2        | 2022-02-06T22:00:22: PM2 log: ===============================================================================
PM2        | 2022-02-06T22:00:22: PM2 log: App [mm:0] starting in -fork mode-
PM2        | 2022-02-06T22:00:22: PM2 log: App [mm:0] online

/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines:
0|mm       |     at /home/pi/MagicMirror/modules/MMM-MyWastePickup/node_helper.js:36:9
0|mm       |     at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)
0|mm       | [06.02.2022 21:37.41.484] [ERROR] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm       | [06.02.2022 21:37.41.485] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
0|mm       | [1468:0100/000000.525475:ERROR:connection.cc(66)] X connection error received.
0|mm       | [07.02.2022 06:05.42.345] [WARN]  The module 'weatherforecast' is deprecated in favor of the 'weather'-module, please refer to the documentation for a migration path
0|mm       | [1440:0207/060546.132881:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|mm       | [1483:0207/060547.287531:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|mm       | [1502:0207/060550.327609:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
0|mm       | [07.02.2022 06:05.57.254] [ERROR] Whoops! There was an uncaught exception...
0|mm       | [07.02.2022 06:05.57.264] [ERROR] TypeError: parse is not a function
0|mm       |     at /home/pi/MagicMirror/modules/MMM-MyWastePickup/node_helper.js:36:9
0|mm       |     at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)
0|mm       | [07.02.2022 06:05.57.266] [ERROR] MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
0|mm       | [07.02.2022 06:05.57.267] [ERROR] If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

/home/pi/.pm2/logs/MagicMirror-out.log last 15 lines:
0|mm       | [07.02.2022 06:05.42.349] [LOG]   Starting node helper for: newsfeed
0|mm       | [07.02.2022 06:05.42.350] [LOG]   Sockets connected & modules started ...
0|mm       | [07.02.2022 06:05.43.840] [LOG]   Launching application.
0|mm       | [07.02.2022 06:05.56.764] [LOG]   Create new newsfetcher for url: https://rss.nytimes.com/services/xml/rss/nyt/HomePage.xml - Interval: 300000
0|mm       | [07.02.2022 06:05.56.895] [INFO]  Checking git for module: MMM-MyWastePickup
0|mm       | [07.02.2022 06:05.57.216] [INFO]  Checking git for module: MMM-Fuel
0|mm       | [07.02.2022 06:05.57.294] [INFO]  Checking git for module: MMM-OpenWeather24Hours
0|mm       | [07.02.2022 06:05.57.357] [INFO]  Checking git for module: default
0|mm       | [07.02.2022 06:05.58.648] [INFO]  Newsfeed-Fetcher: Broadcasting 61 items.
0|mm       | [07.02.2022 06:10.59.278] [INFO]  Newsfeed-Fetcher: Broadcasting 62 items.
0|mm       | [07.02.2022 06:15.59.864] [INFO]  Newsfeed-Fetcher: Broadcasting 62 items.
0|mm       | [07.02.2022 06:21.00.369] [INFO]  Newsfeed-Fetcher: Broadcasting 62 items.
0|mm       | [07.02.2022 06:26.00.875] [INFO]  Newsfeed-Fetcher: Broadcasting 62 items.

BR
Jens

MyMirror

Anyone, any idea?
Who else uses MyWastePickup with Bullseye/MM2.18?

BR
Jens

MyMirror

@mayfield
I have the same problem.
I just get “loading” …

During npm install in “MMM-MyWastePickup” i get following:

pi@MM3:~/MagicMirror $ cd modules/
pi@MM3:~/MagicMirror/modules $ cd MMM-MyWastePickup/
pi@MM3:~/MagicMirror/modules/MMM-MyWastePickup $ npm install

up to date, audited 222 packages in 6s

11 packages are looking for funding
  run `npm fund` for details

3 moderate severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
pi@MM3:~/MagicMirror/modules/MMM-MyWastePickup $ npm audit fix
npm WARN audit fix ansi-regex@5.0.0 node_modules/npm/node_modules/cli-table3/node_modules/ansi-regex
npm WARN audit fix ansi-regex@5.0.0 is a bundled dependency of
npm WARN audit fix ansi-regex@5.0.0 npm@8.4.0 at node_modules/npm
npm WARN audit fix ansi-regex@5.0.0 It cannot be fixed automatically.
npm WARN audit fix ansi-regex@5.0.0 Check for updates to the npm package.
npm WARN audit fix ansi-regex@3.0.0 node_modules/npm/node_modules/string-width/node_modules/ansi-regex
npm WARN audit fix ansi-regex@3.0.0 is a bundled dependency of
npm WARN audit fix ansi-regex@3.0.0 npm@8.4.0 at node_modules/npm
npm WARN audit fix ansi-regex@3.0.0 It cannot be fixed automatically.
npm WARN audit fix ansi-regex@3.0.0 Check for updates to the npm package.
npm WARN audit fix strip-ansi@4.0.0 node_modules/npm/node_modules/string-width/node_modules/strip-ansi
npm WARN audit fix strip-ansi@4.0.0 is a bundled dependency of
npm WARN audit fix strip-ansi@4.0.0 npm@8.4.0 at node_modules/npm
npm WARN audit fix strip-ansi@4.0.0 It cannot be fixed automatically.
npm WARN audit fix strip-ansi@4.0.0 Check for updates to the npm package.
npm WARN audit fix string-width@2.1.1 node_modules/npm/node_modules/string-width
npm WARN audit fix string-width@2.1.1 is a bundled dependency of
npm WARN audit fix string-width@2.1.1 npm@8.4.0 at node_modules/npm
npm WARN audit fix string-width@2.1.1 It cannot be fixed automatically.
npm WARN audit fix string-width@2.1.1 Check for updates to the npm package.

up to date, audited 222 packages in 6s

11 packages are looking for funding
  run `npm fund` for details

# npm audit report

ansi-regex  >2.1.1 <5.0.1
Severity: moderate
 Inefficient Regular Expression Complexity in chalk/ansi-regex - https://github.com/advisories/GHSA-93q8-gq69-wqmw
fix available via `npm audit fix`
node_modules/npm/node_modules/cli-table3/node_modules/ansi-regex
node_modules/npm/node_modules/string-width/node_modules/ansi-regex
  strip-ansi  4.0.0 - 5.2.0
  Depends on vulnerable versions of ansi-regex
  node_modules/npm/node_modules/string-width/node_modules/strip-ansi
    string-width  2.1.0 - 4.1.0
    Depends on vulnerable versions of strip-ansi
    node_modules/npm/node_modules/string-width

3 moderate severity vulnerabilities

To address all issues, run:
  npm audit fix

How can i fix this?
Did you solve your problem?

Thanks

MyMirror

MMM-Fuel problem solved.

My problem was:
UnhandledPromiseRejectionWarning: Error: Cannot find module ‘geolib’

so i use

npm install geolib

And i get the mudul running.

Cheers
Jens

MyMirror

@sdetweil

Hi Sam,

my provider is Tankerkoenig …

Jens

MyMirror

I forgot the MMM-Fuel modul:

                {
                        module: "MMM-Fuel",
                        position: "top_left",
                        config: {
                                api_key: "57ae...................2e",
                                lat: xx.xxxxxxxx,
                                lng: y.yyyyy,
                                types: ["E5"],
                        }
                },

Jens

MyMirror

@sdetweil

Hi Sam,

after my old MM didn’t work properly and this was apparently also due to the very old Jessie, I started a new mirror based on a PI4 with Bullseye.

For the initial installation I also took your script. But before that I manually updated Node to the latest version.

The mirror worked in the basic version. The first modul “MMM-Fuel” has then unfortunately no data delivered and I thought that your script possibly correct necessary dependencies.

Currently I do not know how to fix these problems soon:

there are 2 local files that are different than the master repo

   installers/mm.sh
   package-lock.json

Regarding MMM-Fuel I have to search something because of the certificate etc., right?

Jens

MyMirror

Hi all,
i’ve installed MM on a new pi4 (bullseye) with sdetweil’s script.
Everything ok, node version 17.3.0 and npm at 8.3.0.
After the first start, i have cloned MMM-Fuel and modified the config.js (with api-key and lat/lng).

The mirror starts but i didn#t get infos from MMM-Fuel.
Then i tried the sdetweil’s update script.
I get following:

pi@pi4:~ $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
No LSB modules are available.

doing test run = true, NO updates will be applied!

update log will be in /home/pi/MagicMirror/installers/upgrade.log
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v16.9.1
Installed Node version: v17.3.0
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V7.11.2
Installed npm version: V8.3.0
No npm upgrade necessary.

saving custom.css
upgrading from version 2.18.0 to 2.18.0
fetching latest revisions
there are 2 local files that are different than the master repo

   installers/mm.sh
   package-lock.json

any *-lock.json files do not need to be saved
do you want to save these files for later   (Y/n)?n
skipping restore for installers/mm.sh, doing test run
skipping restore for package-lock.json, doing test run
Checking for modules with removed libraries
processing dependency changes for active modules with package.json files

processing for module MMM-Fuel please wait
----------------------------------
skipped processing for MMM-Fuel, doing test run
processing complete for module MMM-Fuel

restoring custom.css

How can i fix this?
Thanks for helping me.

MyMirror

@sdetweil
Hi Sam,

yes i know :-( … very old.

in the meantime I got the system on “Stretch” and wanted to take the next step to “Buster”.
But I get the following error (on german):
PGP error: http://ftp.de.debian.org/debian buster InRelease: The following signatures could not be verified because their public key is not available …

How can I adjust/correct this?
Thanks a lot

MyMirror

Hi Sam,

I have a similar problem.
My memory card is defective and I had to revert to an older backup.
Unfortunately, I have been a little lax with the backup, as I always have to get the mirror off the wall a bit awkwardly to back up the SD card.

I am with the mirror still on Jessie.
When I stop the MagicMirror with “pm2 stop mm” and also stop node with killall node, I get a message from your scipt (test mode) that node and npm need to be updated.
How do I get them to the latest version?

I am rather beginner in Linux - so have understanding for simple queries.
Can you help me?

BR
Jens

MyMirror

Hi all,

are there any known issues with MMM fuel?
I don’t get a display anymore - just says “Loading …”.
So far the module was running fine, didn’t change anything.

Thanks for tips and tricks

MyMirror

… or he can share a directory and mount it on the PC. I also do this with the MMM-MyWastePickup to edit the new entries in the “schedule_custom.csv” with Excel.

MyMirror

@sezer84
Moin aus Hamburg,

meine Einträge zu kopieren macht wenig bis keinen Sinn, denn
es sind alte Daten (aus 2020) und ich habe sicher andere Abfuhrdaten.
Schick mir mal deine Rufnummer per PN und lass uns drüber sprechen.

Gruß
Jens

MyMirror

Hallo Sezer84,

die csv Datei muss im MMM-MyWastePickup Verzeichnis liegen.
Dort kann es immer nur eine aktuelle “schedule_custom.csv” Datei geben.
Ich habe mir eine weitere, alte Datei als Backup hingelegt (schedule_custom_kopie.csv).

Das Verzeichnis habe ich mir freigegeben und unter Windows als Laufwerk eingebunden, damit
ich sie csv mit Excel besser bearbeiten kann.

Dabei muss die erste Zeile bestehen bleiben!
Beispiel:

Calendar,WeekStarting,GreenBin,Garbage,Recycling,YardWaste,ChristmasTree
Custom,08/26/20,0,1,0,0,0
Custom,08/27/20,1,0,0,0,0
Custom,09/2/20,0,1,1,0,0
Custom,09/9/20,0,1,0,0,0
Custom,09/10/20,1,0,0,0,0
Custom,09/16/20,0,1,0,0,0
Custom,09/23/20,0,1,0,0,0

Nach dem Datum werden die jeweilgen Tonnen mit einer 1 als “aktiv” gekennzeichnet.
In meinem Beispiel oben wäre das also
Custom,08/26/20,0,1,0,0,0
am 26.8.2020
Grüne Tonne : Nein
Restmüll: Ja
Blaue Tonne: Nein
Gartenabfall: Nein
Tannenbaum: Nein

Gruß
Jens

MyMirror

@pablousavilla
Great - thanks for the detailed explanation.
I will have a closer look at the weekend.

Have a nice day and stay healthy.

MyMirror

Very well made.
I like that the mirror has no frame.
For the MMM chart, how did you integrate the data from opensensemap.org? Can you show us that part?

MyMirror

@ashishtank
works as described and shown.
So I have a workaround for now and can deal with the actual svg problem again later.

Great, thanks a lot!

MyMirror

I have changed the color of the trash can and saved the SVG in the MMM-MyWastePickup directory.
Is this call correct then?

.waste-pickup-icon.recycle {
  background-image:url('file:///home/pi/MagicMirror/modules/MMM-MyWastePickup/recycle-bin2.svg');
}