Help with mmm-systemtemperature error messages

thartley

Hello,

I hope someone can provide some information on what I should check for what might be causing the errors shown below. The lines are from the Developer’s Window Console tab for the mmm-systemtemperature module. Magic Mirror 2 runs the same with or without this module active. The module itself seems to run because it puts the temperature on the Magic Mirror screen. But because of the errors I’m not sure the temperature is accurate though. The last error in the list “…Uncaught (in promise) TypeError:…” repeats every 5 seconds, which matches up to the “update Interval” configuration option fetch temperature value.

In case it matters, this module is listed before some of the other modules in my config file, but it is the last module to show up on the MM2 display when I start MM2.

Load script: modules/mmm-systemtemperature/mmm-systemtemperature.js
module.js:483 Module registered: mmm-systemtemperature
loader.js:137 Bootstrapping module: mmm-systemtemperature
loader.js:164 Load script: modules/mmm-systemtemperature/node_modules/lodash/lodash.js
:8080/modules/mmm-systemtemperature/node_modules/lodash/lodash.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
localhost/:1 Refused to execute script from ‘http://localhost:8080/modules/mmm-systemtemperature/node_modules/lodash/lodash.js’ because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.
loader.js:172 Error on loading script: modules/mmm-systemtemperature/node_modules/lodash/lodash.js

loader.js:27 Error when starting node_helper for module mmm-systemtemperature:
startModules @ loader.js:27

loader.js:28 ReferenceError: _ is not defined
at Class.getCommandExecutor (mmm-systemtemperature.js:76:3)
at Class.start (mmm-systemtemperature.js:23:31)
at startModules (loader.js:25:32)
at loadNextModule (loader.js:220:12)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)
at async loadNextModule (loader.js:213:6)

5mmm-systemtemperature.js:31 Uncaught (in promise) TypeError: this.commandExecutor is not a function
at Class.socketNotificationReceived (mmm-systemtemperature.js:31:9)
at module.js:234:9
at Socket. (socketclient.js:38:4)
at Emitter.emit (index.mjs:136:20)
at Socket.emitEvent (socket.js:498:20)
at Socket.onevent (socket.js:485:18)
at MMSocket.socket.onevent (socketclient.js:32:11)
at Socket.onpacket (socket.js:455:22)
at Emitter.emit (index.mjs:136:20)
at manager.js:204:18

sdetweil

@thartley you can do it now…

go to the module folder

cd ~/MagicMirror/modules/mmm-systemtemperature
npm install

then restart MagicMirror

from the module readme

In your terminal, go to your MagicMirror's Module folder:

cd ~/MagicMirror/modules
Clone this repository:

git clone https://github.com/MichMich/mmm-systemtemperature.git
Install dependencies:

this leaves out the important step

cd mmm-systemtemperature

then

npm install

sdetweil

@thartley did you
npm install
In the module folder after git clone?

thartley

@sdetweil - Thank you for the reply. I don’t know if I did or not because it was some time back. Is that a step I can do now without messing things up if it turns out I already did it earlier? Or is there a way to tell if the npm step was done previously before running it now?

sdetweil

@thartley you can do it now…

go to the module folder

cd ~/MagicMirror/modules/mmm-systemtemperature
npm install

then restart MagicMirror

from the module readme

In your terminal, go to your MagicMirror's Module folder:

cd ~/MagicMirror/modules
Clone this repository:

git clone https://github.com/MichMich/mmm-systemtemperature.git
Install dependencies:

this leaves out the important step

cd mmm-systemtemperature

then

npm install

thartley

@sdetweil - Thank you for the assistance. There are no longer any errors for that module. The system did need to update npm install to a newer version on my system first. After that it the remaining steps went just fine.

sdetweil

@thartley you did NOT need to update npm

thartley

@sdetweil - Maybe I misspoke when I used the word “update”. When I keyed in npm install per your instructions, it came back with several lines, each starting with “npm WARN old lockfile…”.

It took care of something, so maybe it was just doing some sort of cleanup?

thartley

@sdetweil - Hi. Please mark this as resolved since I don’t think I have rights to do that yet.

sdetweil

@thartley you do,

Find the post which best resolves the issue
Hit the 3 dots in the lower right corner
Select
Mark this post as the best answer

sdetweil

@thartley ok, understood. It upgraded the lock file format,
Useless user message in my opinion, as there is no way to fall back to an older npm which can’t use the new format