@JohnGalt Hello. I have the same issue not being able to map to a NAS drive using the Terminal commands. I can map to the drive using the Files GUI. I couldn’t get it to work either - the problem seems to between my chair and the keyboard. Even though I got it to map with the FM, I still couldn’t get the MMM_ImagesPhotos module to access the NAS, which in my case is a USB flash drive on my Windows router USB port. I didn’t test to see if the drive letter is persistent between reboots/power failures. -Thanks

@sdetweil Hello Sam. Thank you for the reply and confirmation. I had seen your post to another person’s CSS question where you shared that tool. I used it earlier today and it showed what you saw. I was hoping that due to my minimal skill with CSS I was overlooking something, but I guess I wasn’t.

Hello. I have a CSS question about the Current Temperature text size for the MMM-OpenWeatherForecast module fork from Tom Hirschberger.

About a month ago, Tom Hirschberger updated his fork of the MMM-OpenWeatherForecast module where he added a new “Feels Like” temperature option. According to the documentation, there are three options you can choose; to display only the actual temperature, or only the Feels Like temperature, or both, where the display shows in the format CURRENT (FEELS LIKE). The text size can be adjusted in the CSS file and I have figured that out, but as far as I can tell, it is the same text size for either temperature.

I don’t know enough about CSS to know if I can add something to a custom CSS file to set the text size for one to a different size than the other. Or if the module programming has the two temperatures set such that their sizes can be controlled separately.

I have also tried using two instances of the module, one with just the Current Temperature with all the other weather info suppressed, and then a second instance right below it with the Feels Like temperature along with the other weather info such as the forecast (similar to the default Weather module for displaying current and forecast info). This sort of works, but the two temperature displays are the same text size since I don’t think I can set a different CSS text size for each instance, can I?

Does anyone have any suggestions?

Thanks.

@plainbroke I’ve been using this make and model SBC for a few years now:

Le Potato AML-S905X-CC

Add the heat sink made for it. It might also need a little muffin fan, depending on the type of modules you’ll be running and how hard the CPU will be working. But that can be added later if you find it’s needed.

I think a few of the GPIO pins are in a little different order than the Raspberry Pi’s, but the rest of the board seems to match the footprint of the Raspberry Pi. I’m running Armbian Linux that I downloaded from the Libre website.

I started using this model during the pandemic when the R-Pi was not readily available and expensive when you could find one.

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

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

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

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

@Sam-0 Thank you for this module and the css code.

I like that the lights are partially covering the information that is already being displayed in the upper area, but the “twinkle” effect lets the information show through when the bulbs go into their dim phase. It is kind of a 3D effect.

I usually struggle with trying to modify css to tweak settings. Your comments/notes in your HolidayTemplate.css file explained things nicely for what the various parts do and how they control parts of the light string.

Using that information, I added a couple more colors (blue and orange) to a copy of the Christmas.css file. With all the examples you provided, I was able to copy code snippets from your other examples and paste them into my Christmas test copy, edit their position numbers, and add two more instances in the “.strand li:nth-child…” section of the css file. One thing that wasn’t notated in your documentation was what color name (ex: blue or red) each section creates, but you did tell us to go to https://www.colorhexa.com/ where we can get the information. From there it’s an easy task to get the color names and add a color name comment for each light in the css file.

I grabbed the code for the blue and orange from your Pride.css file. Blue is light #2, orange is light #5 from that css file.

One last comment - my normal MM setup is pretty basic. I can run my Le Potato with just a heat sink and the CPU temperature stays at 46C. With the Holiday Lights module running, it gets up to 67C so I reinstalled the 10cm fan that came with the case and it’s down to 49C.