Hello - I’ve been using MMM-OpenWeatherForecast successfully for a while, but noticed the temperature is significantly different from the actual temp in my location. I’ve used latlong.net to get the right Latitude and Longitude, but it’s still not right. When I navigate to openweathermap.org, I see the correct temperature for my location (New Jersey, USA).

Any idea what could cause this? I don’t think the config allows anything other than lat/long to determine the location (e.g., no zip code, or location ID).

@MarcLandis Thanks - this one works well. Just need to reconfigure the custom CSS. I appreciate the suggestion!

@sdetweil Thanks… yes, looks like the module hasn’t been updated in a while.

@mumblebaj Yes, it was working fine on my previous mirror. However, it stopped working after upgrading to a new RPI/updated OS.

I’m doing a new install of my Mirror and replicating my previous apps. However, I’m getting the following error for MMM-Reddit, which worked fine on my previous Mirror. Any ideas?

npm warn old lockfile
npm warn old lockfile The package-lock.json file was created with an old version of npm,
npm warn old lockfile so supplemental metadata must be fetched from the registry.
npm warn old lockfile
npm warn old lockfile This is a one-time fix-up, please be patient…
npm warn old lockfile
npm warn deprecated set-value@2.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated osenv@0.1.5: This package is no longer supported.
npm warn deprecated mixin-deep@1.3.1: Critical bug fixed in v2.0.1, please upgrade to the latest version.
npm warn deprecated is-data-descriptor@0.1.4: Please upgrade to v0.1.5
npm warn deprecated is-accessor-descriptor@0.1.6: Please upgrade to v0.1.7
npm warn deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version.
npm warn deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated is-accessor-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated is-data-descriptor@1.0.0: Please upgrade to v1.0.1
npm warn deprecated rimraf@2.6.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm warn deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm warn deprecated are-we-there-yet@1.1.5: This package is no longer supported.
npm warn deprecated glob@6.0.4: Glob versions prior to v9 are no longer supported
npm warn deprecated source-map-url@0.4.0: See https://github.com/lydell/source-map-url#deprecated
npm warn deprecated glob@7.1.2: Glob versions prior to v9 are no longer supported
npm warn deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm warn deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm warn deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm warn deprecated gauge@2.7.4: This package is no longer supported.
npm warn deprecated source-map-resolve@0.5.2: See https://github.com/lydell/source-map-resolve#deprecated
npm warn deprecated har-validator@2.0.6: this library is no longer supported
npm warn deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm warn deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm warn deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated request@2.79.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated har-validator@4.2.1: this library is no longer supported
npm warn deprecated fstream@1.0.11: This package is no longer supported.
npm warn deprecated tar@2.2.1: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm warn deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm warn deprecated node-sass@4.9.0: Node Sass is no longer supported. Please use sass or sass-embedded instead.
npm error code 1
npm error path /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/node-sass
npm error command failed
npm error command sh -c node scripts/build.js
npm error Building: /usr/bin/node /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm error gyp info it worked if it ends with ok
npm error gyp verb cli [
npm error gyp verb cli ‘/usr/bin/node’,
npm error gyp verb cli ‘/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/node-gyp/bin/node-gyp.js’,
npm error gyp verb cli ‘rebuild’,
npm error gyp verb cli ‘–verbose’,
npm error gyp verb cli ‘–libsass_ext=’,
npm error gyp verb cli ‘–libsass_cflags=’,
npm error gyp verb cli ‘–libsass_ldflags=’,
npm error gyp verb cli ‘–libsass_library=’
npm error gyp verb cli ]
npm error gyp info using node-gyp@3.7.0
npm error gyp info using node@22.9.0 | linux | arm
npm error gyp verb command rebuild []
npm error gyp verb command clean []
npm error gyp verb clean removing “build” directory
npm error gyp verb command configure []
npm error gyp verb check python checking for Python executable “python2” in the PATH
npm error gyp verb which failed Error: not found: python2
npm error gyp verb which failed at getNotFoundError (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:13:12)
npm error gyp verb which failed at F (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:68:19)
npm error gyp verb which failed at E (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:80:29)
npm error gyp verb which failed at /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:89:16
npm error gyp verb which failed at /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/isexe/index.js:42:5
npm error gyp verb which failed at /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/isexe/mode.js:8:5
npm error gyp verb which failed at FSReqCallback.oncomplete (node:fs:197:21)
npm error gyp verb which failed python2 Error: not found: python2
npm error gyp verb which failed at getNotFoundError (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:13:12)
npm error gyp verb which failed at F (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:68:19)
npm error gyp verb which failed at E (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:80:29)
npm error gyp verb which failed at /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/which/which.js:89:16
npm error gyp verb which failed at /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/isexe/index.js:42:5
npm error gyp verb which failed at /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/isexe/mode.js:8:5
npm error gyp verb which failed at FSReqCallback.oncomplete (node:fs:197:21) {
npm error gyp verb which failed code: ‘ENOENT’
npm error gyp verb which failed }
npm error gyp verb check python checking for Python executable “python” in the PATH
npm error gyp verb which succeeded python /usr/bin/python
npm error (node:4599) [DEP0060] DeprecationWarning: The util._extend API is deprecated. Please use Object.assign() instead.
npm error (Use node --trace-deprecation ... to show where the warning was created)
npm error gyp verb check python version /usr/bin/python -c "import platform; print(platform.python_version());" returned: “3.9.2\n”
npm error gyp ERR! configure error
npm error gyp ERR! stack Error: Python executable “/usr/bin/python” is v3.9.2, which is not supported by gyp.
npm error gyp ERR! stack You can pass the --python switch to point to Python >= v2.5.0 & < 3.0.0.
npm error gyp ERR! stack at PythonFinder.failPythonVersion (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/node-gyp/lib/configure.js:501:19)
npm error gyp ERR! stack at PythonFinder. (/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/node-gyp/lib/configure.js:483:14)
npm error gyp ERR! stack at ChildProcess.exithandler (node:child_process:413:7)
npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28)
npm error gyp ERR! stack at maybeClose (node:internal/child_process:1104:16)
npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:304:5)
npm error gyp ERR! System Linux 6.1.21-v8+
npm error gyp ERR! command “/usr/bin/node” “/home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/node-gyp/bin/node-gyp.js” “rebuild” “–verbose” “–libsass_ext=” “–libsass_cflags=” “–libsass_ldflags=” “–libsass_library=”
npm error gyp ERR! cwd /home/burgerson/MagicMirror/modules/MMM-Reddit/node_modules/node-sass
npm error gyp ERR! node -v v22.9.0
npm error gyp ERR! node-gyp -v v3.7.0
npm error gyp ERR! not ok
npm error Build failed with error code: 1
npm error A complete log of this run can be found in: /home/burgerson/.npm/_logs/2024-10-04T10_51_38_463Z-debug-0.log

@MarcLandis Thanks… I was running a very old version of Raspian and wasn’t able to update Node. Setting up a new version now :-)

Just updated my module to use the v3.0 API, but getting the following error:

[ERROR] [MMM-OpenWeatherForecast] 30-Sep-24 20:15 ** ERROR ** ReferenceError: fetch is not defined

Any idea why that is? When I copy/paste the URL into the browser, I get a response.

@sdetweil Thanks :-) I didn’t realize the link had changed. All working now!

Thanks, @mumblebaj for the fix!

@mumblebaj said in MMM-Reddit "No valid posts to display":

https://github.com/mumblebaj/MMM-Reddit

Thanks for looking into this and making the changes. How would I be able to use your version, do I need to switch to the new fork? Thanks

Hi All - out of the blue, my MMM-Reddit module is displaying the following error:

No valid posts to display
Check the console for a full description of error.

Note that I can’t find any error in the logs, nor did I make any changes to the module.
Could this be an outdated backend dependency or certificate? Any help troubleshooting this issue is appreciated.