MMM-MyWastePickup date problem

BravoOscar

In 2021 I war running MagicMirror 2.16 with MMM-MyWastePickup and everything was working just fine.

Here i 2022 I updated MagicMirror to 2.18 and updated MMM-MyWastePickup.

I then updated the schedule_custom.csv with 2022 dates, and now it dosent work, it just says Loading. If i change dates in schedule_custom.csv to 2021 or 2023, then i says “no schdule”

Have anybody a clue what to do?
Is it something with MM 2.18?

Working, says “No Schdule”

Calendar,WeekStarting,GreenBin,Garbage,Recycling,YardWaste,ChristmasTree
Custom,01/02/21,0,1,0,0,0
Custom,01/07/21,0,1,0,0,0
Custom,01/12/21,1,0,1,0,1

Not Working, Says “Loading”

Calendar,WeekStarting,GreenBin,Garbage,Recycling,YardWaste,ChristmasTree
Custom,01/02/22,0,1,0,0,0
Custom,01/07/22,0,1,0,0,0
Custom,01/12/22,1,0,1,0,1

mayfield

@bravooscar Check your csv file and make sure all the slashes and commas are in their right places. This happened to me last night with the MMM-MyGarbage module and I noticed some of my entries had commas in the dates instead of slashes.

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

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

BR
Jens

sdetweil

@mymirror you are on the wrong node version

need 14 or preferably 16
the steps outlined here might help
https://github.com/MichMich/MagicMirror/issues/2772

my mm install script does that as part of mm install

https://github.com/sdetweil/MagicMirror_scripts

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

@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 $

sdetweil

@mymirror said in MMM-MyWastePickup date problem:

! 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

the module is having a problem, I would report that to the module GitHub page

mickecarlsson

@bravooscar said in MMM-MyWastePickup date problem:

MMM-MyWastePickup

Make sure that you only have one (1) empty line after the last in the schedule_custom.csv. If you have more empty lines it will break.

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

UNSOLVED MMM-MyWastePickup date problem