MagicMirror Forum

Richard238

Sure, it’s in /home/pi/MagicMirror/css/custom.css

 * Changes to this files will be ignored by GIT. *
 *****************************************************/

 body {
 	
 }

 
 .fa.fa-calendar-check-o {
  color: #00d2ff; /* Blue */
}

 .fa.fa-trash-o  {
  color: #C97F7F; /* Brown */

Richard238

Thanks, it was that, and a missing } close curly bracket.

Richard238

Noticed earlier that my MM had crashed for whatever reason - it’s not been ~~touched~~ changed in weeks.

On reboot, it wanted 44 updates.
pm2 start mm then showed nothing, with the logs giving an error:

0|mm       | [10532:0127/132321.643138:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/pi/MagicMirror/node_modules/electron/dist/chrome-sandbox is owned by root and has mode 4755.

I did

sudo chown root /home/pi/MagicMirror/node_modules/electron/dist/chrome-sandbox
sudo chmod 4755 /home/pi/MagicMirror/node_modules/electron/dist/chrome-sandbox

This seems to have fixed it, with MM now starting correctly.

What’s caused this, and is the chown/chmod the correct thing todo?

Richard238

@sdetweil

renamed MM to MM.JAN22

renamed MM.save to MM

All good, thank you.

Richard238

@sdetweil Weather module changes worked.
They needs adjusting, but it is now showing something so it’s a good start I can work from.

Richard238

I now have coloured icons in the calendar:

Code now looks like this:

/* Calendar: config.js set to  symbol: 'fa-light fa-calendar', */ 
.calendar .fa-calendar-day {
  color: #00d255 /* 55=Green FF=Blue */
}

/* Calendar: config.js set to  symbol: 'fa-light fa-trash-can', */ 
.calendar .fa-trash  {
  color: #C97F7F /* Brown */
}

Richard238

Just a couple of probably very quick-n-simple queries regarding the default weather module

Firstly, current weather does not show location yet it’s all in the code

		{
			module: 'weather',
			header: 'Current weather for: ',			
			position: 'top_right',
			config: {
				type: 'current',
				location: 'My_Place',
				locationID: '1234567',  //ID from https://www.openweathermap.org
				apiKey: '####################'
			}
		},

Next, forecast does show location, but how do I remove the “,GB” part of the location?
(And I’ll do the same for current weather too.)

		{
			module: 'weather',
			position: 'top_right',
			header: 'Weather Forecast for: ',
			config: {
				type: 'forecast',
				location: 'My_Place',
				locationID: '1234567',  //ID from https://www.openweathermap.org
				apiKey: '####################'
			}
		},

Thank you.

Richard238

@sdetweil I’m WFH most of the week and don’t notice any internet interruptions.

Richard238

@sdetweil

Interesting, it’s using the wifi from the router that’s not 3 metres across the room.
I’ll look at hard wiring it at some point.

Richard238

MM has crashed several times recently.
Inspection of MagicMirror-error.log shows a tonne of EAI_AGAIN errors which may or may not have anything to do with it.

Here’s an example, it’s not just sky news, it’s all news feeds, calendars etc., etc…

}
[01.08.2022 22:46.21.463] [ERROR] Newsfeed Error. Could not fetch newsfeed:  http://feeds.skynews.com/feeds/rss/world.xml FetchError: request to http://feeds.skynews.com/feeds/rss/world.xml failed, reason: getaddrinfo EAI_AGAIN feeds.skynews.com
    at ClientRequest.<anonymous> (/home/pi/MagicMirror/node_modules/node-fetch/lib/index.js:1491:11)
    at ClientRequest.emit (node:events:526:28)
    at Socket.socketErrorListener (node:_http_client:442:9)
    at Socket.emit (node:events:526:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'EAI_AGAIN',
  code: 'EAI_AGAIN'
}

Google search suggests a DNS error, but MM shows DNS working OK.

pi@magicmirror:~ $ nslookup www.google.co.uk
Server:         208.67.222.222
Address:        208.67.222.222#53

Non-authoritative answer:
Name:   www.google.co.uk
Address: 172.217.169.35
Name:   www.google.co.uk
Address: 2a00:1450:4009:823::2003

Richard238

Good news! This was OK after a reboot, but how do you restart MM manually now?

pi@magicmirror:~ $ cd MagicMirror
pi@magicmirror:~/MagicMirror $ pm2 stop all
[PM2] Applying action stopProcessId on app [all](ids: [ 0 ])
[PM2] MagicMirror â
ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ
â id â name â mode â âº â status â cpu â memory â
ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼âââââââââââ¤
â 0 â MagicMirror â fork â 1 â stopped â 0% â 0b â
ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ
pi@magicmirror:~/MagicMirror $ git pull && npm install
From https://github.com/MichMich/MagicMirror
a2d7cdcf…30d5bfe5 master -> origin/master

[new tag] v2.20.0 -> v2.20.0
Updating a2d7cdcf…30d5bfe5
Fast-forward
.eslintrc.json | 2 ±
.github/{FUNDING.yml => FUNDING.yaml} | 0
.github/{codecov.yml => codecov.yaml} | 0
.github/dependabot.yaml | 6 +
.github/{stale.yml => stale.yaml} | 0
…/{automated-tests.yml => automated-tests.yaml} | 7 ±
…ov-test-suites.yml => codecov-test-suites.yaml} | 6 ±
…nforce-changelog.yml => enforce-changelog.yaml} | 5 ±
CHANGELOG.md | 27 ±
fonts/package-lock.json | 28 ±
fonts/package.json | 4 ±
fonts/roboto.css | 19 ±
js/defaults.js | 3 +
js/electron.js | 2 ±
js/fetch.js | 20 +
js/server.js | 4 ±
modules/default/calendar/calendar.js | 26 ±
modules/default/calendar/calendarfetcher.js | 2 ±
modules/default/calendar/calendarutils.js | 3 ±
modules/default/newsfeed/newsfeedfetcher.js | 11 ±
modules/default/weather/weather.js | 9 +
modules/default/weather/weatherobject.js | 17 +
package-lock.json | 5217 +++++++±----------
package.json | 41 ±
tests/e2e/env_spec.js | 6 ±
tests/e2e/fonts.js | 6 ±
tests/e2e/global-setup.js | 7 ±
tests/e2e/ipWhitelist_spec.js | 10 ±
tests/e2e/modules/alert_spec.js | 4 ±
tests/e2e/modules/calendar_spec.js | 4 ±
tests/e2e/modules/clock_es_spec.js | 4 ±
tests/e2e/modules/clock_spec.js | 4 ±
tests/e2e/modules/compliments_spec.js | 4 ±
tests/e2e/modules/helloworld_spec.js | 4 ±
tests/e2e/modules/newsfeed_spec.js | 4 ±
tests/e2e/modules/weather_spec.js | 4 ±
tests/e2e/modules_display_spec.js | 4 ±
tests/e2e/modules_position_spec.js | 4 ±
tests/e2e/port_config.js | 10 ±
tests/e2e/vendor_spec.js | 6 ±
tests/e2e/without_modules.js | 4 ±
vendor/package-lock.json | 14 ±
vendor/package.json | 2 ±
43 files changed, 2482 insertions(+), 3082 deletions(-)
rename .github/{FUNDING.yml => FUNDING.yaml} (100%)
rename .github/{codecov.yml => codecov.yaml} (100%)
create mode 100644 .github/dependabot.yaml
rename .github/{stale.yml => stale.yaml} (100%)
rename .github/workflows/{automated-tests.yml => automated-tests.yaml} (90%)
rename .github/workflows/{codecov-test-suites.yml => codecov-test-suites.yaml} (84%)
rename .github/workflows/{enforce-changelog.yml => enforce-changelog.yaml} (77%)
create mode 100644 js/fetch.js
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/console@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/core@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/environment@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/expect@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/expect-utils@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/fake-timers@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/globals@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/reporters@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/schemas@28.0.2’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/source-map@28.0.2’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/test-result@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/test-sequencer@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/transform@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘@jest/types@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘babel-jest@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘babel-plugin-jest-hoist@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘babel-preset-jest@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘diff-sequences@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘expect@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-changed-files@28.0.2’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-circus@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-cli@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-config@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-diff@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-docblock@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-each@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-environment-node@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-get-type@28.0.2’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-haste-map@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-leak-detector@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-matcher-utils@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-message-util@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-mock@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-regex-util@28.0.2’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-resolve@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-resolve-dependencies@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-runner@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-runtime@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-snapshot@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-util@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-validate@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-watcher@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘jest-worker@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘pretty-format@28.1.1’,
npm WARN EBADENGINE required: { node: ‘^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0’ },
npm WARN EBADENGINE current: { node: ‘v16.1.0’, npm: ‘7.11.2’ }
npm WARN EBADENGINE }

magicmirror@2.20.0 install
echo "Installing vendor files …
" && cd vendor && npm install --loglevel=error

Installing vendor files …

changed 1 package, and audited 10 packages in 8s

found 0 vulnerabilities

magicmirror@2.20.0 postinstall
npm run install-fonts && echo "MagicMirrorÂ² installation finished successfully!
"

magicmirror@2.20.0 install-fonts
echo "Installing fonts …
" && cd fonts && npm install --loglevel=error

Installing fonts …

changed 2 packages, and audited 3 packages in 6s

found 0 vulnerabilities
MagicMirrorÂ² installation finished successfully!

magicmirror@2.20.0 prepare
[ -f node_modules/.bin/husky ] && husky install || echo no husky installed.

husky - Git hooks installed

added 467 packages, removed 2 packages, changed 96 packages, and audited 731 packages in 9m

82 packages are looking for funding
run npm fund for details

3 moderate severity vulnerabilities

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.
npm notice
npm notice New major version of npm available! 7.11.2 -> 8.13.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.13.2
npm notice Run npm install -g npm@8.13.2 to update!
npm notice
pi@magicmirror:~/MagicMirror $ pm2 start mm
[PM2][ERROR] Script not found: /home/pi/MagicMirror/mm
pi@magicmirror:~/MagicMirror $ pm2 restart mm
Use --update-env to update environment variables
[PM2][ERROR] Process or Namespace mm not found
pi@magicmirror:~/MagicMirror $ pm2 start mm.sh
[PM2][ERROR] Script not found: /home/pi/MagicMirror/mm.sh
pi@magicmirror:~/MagicMirror $

Richard238

@sdetweil More by luck than skill, but thank you for your help and patience with this.

Richard238

I now have coloured icons in the calendar:

Code now looks like this:

/* Calendar: config.js set to  symbol: 'fa-light fa-calendar', */ 
.calendar .fa-calendar-day {
  color: #00d255 /* 55=Green FF=Blue */
}

/* Calendar: config.js set to  symbol: 'fa-light fa-trash-can', */ 
.calendar .fa-trash  {
  color: #C97F7F /* Brown */
}

Richard238

Not coloured (even changing solid to light), but it’s an icon

.calendar .fa-solid fa-calendar {
  color: #00d255 /* 55=Green FF=Blue */
}


.calendar .fa-light fa-trash-can  {
  color: #C97F7F; /* Brown */
}

The other icons used to work, pre update.
Did MM change which fa library they use?
The fa libraries ought to be backwards compatible, no?

More tomorrow, I need sleep.

Richard238

class? element? I try, but I’m not much of a coder. I’m hopelessly lost, as I’m sure you can tell.

I appreciate your efforts but sadly this is way beyond my skills.

I’ll live without the icon for now and perhaps revisit another day.

Richard238

Even though the icon is fa-calendar-check-o
https://fontawesome.com/v4/icon/calendar-check-o

we omit the -o ?

Richard238

@Richard238

Best posts made by Richard238

Latest posts made by Richard238