@sdetweil Yes, I’m not quite sure what the weatherforecast.js change was, but that’s blown away now. As you say, the new module is fine with a little tweaking via custom.css.

It was the package.json file that screwed things up, and that I know I have never touched and have no idea what it was and why it got out of sync.

Anyway I learned a bit of stuff about GitHub and stashing, so that’s a bonus and we’re up and running again fine (after swapping out the depreciated weather modules too).

@sonicgoose - Note the (mis)spelling of the config parameter for columns - the config entry is “showDeviceColums”, not “showDeviceColumns”. It is missing an n, and needs it removed to work (or the script corrected for it).

See my config example above, which works. Yours is wrong as (ironically) it’s spelt correctly!

For reference, this is one of the entries in my config.js (I use the module twice, once for now and once for forecast):

        {
            module: "weather",
            position: "top_left",
            config: {
                type: "current",
                location: "Manchester",
                locationID: "", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
                apiKey: "#####f59935f34cea0bf3c1aa82#####",
                units: "metric",
                degreeLabel: true,
                showHumidity: true,
                tableClass: "medium"
                }
        },

Where the #'s in the apiKey are actually other letters and numbers (full key redacted).

@Canguingo said in New Weather Module - Migration:

apiKey: “abcde12345abcde12345abcde12345ab” //this is the old appi that i had

Is that really your actual key, or did you just put that as a redaction of your actual key?

Just to ask a basic question, as that doesn’t look like a valid key to me.

As the others have noted, all you should need to do is change the module name and swap the key label from appid: to apiKey: , The key value itself is valid for both.

@Canguingo Nothing needs to be done in the module, it should already have been there in parallel to the old ones for the last few versions of MM.

All you need to do is make the changes in config.js as detailed on the migration/depreciation part of the documentation. That will switch you over from the old modules to the new one.

What has happened with the 2.19 update is the old modules have basically been removed and just replaced with the notification that you see on the mirror screen now (and that will also presumably be removed going forward).

The config.js entry should look something like the template version you posted originally, except of course you will need to use your own specific API key rather than the abcde12345 placeholder and your specific location (unless you happen to be in Amsterdam).

@mumblebaj Just tried it (copy/paste from your code above) and whilst the yellow works, the font-size didn’t for me.

@sdetweil And we have a winner

That one worked as you say, thanks Sam!

So yesterday’s learning was GitHub, today’s is CSS

@sdetweil So looks like the element is p as you correctly surmised before, but for some reason the custom.css entry is getting overwritten or somehow blocked (you can see it’s there in the inspector, but struck through)?

Here now I have no idea, aside from breaking rule 1 and just editing the js file directly…

The config.js setting for the module is:

        {
            module: "MMM-network-signal",
            position: "bottom_right",
            config: {
                server: "8.8.8.8",
                showMessage: true,
                flexDirection: "row-reverse",
                scale: 0.35
            }
        },

And the custom.css entry is :

.MMM-network-signal p {
  font-size: 1.5em;
}

I also tried fontSize: as per your original suggestion, but that didn’t work either.

Better picture, having set up client/server:

@sdetweil I’ve dug a bit deeper and can see that the custom.css is there, but seems to be being overwritten (it’s crossed out)?

Here’s a screenshot of the mirror (apologies for quality, it’s via phone). Can you guide where I should be looking or clicking for this?

@sdetweil I’m not sure I’m doing this right.

I’ve pressed ctrl+shift+i and got the inspector window up, then selected the elements tab (although it’s the default selection anyway) then clicked on the mouse pointer icon at top-left and then clicked onto the message text in the main mirror window.

When I do that I get the sub-window at the bottom of the inspector with div and P tabs, with the P tab selected. There I can see element.style with the text-align and font-size sub-entities plus user agent and main.css items.

P I take it from the code is the paragraph entity I need to be resizing, and from the top of the code the module name is .MMM-network-signal but it’s the rest of the top line to go into custom.css that I’m struggling to identify.

I’m not sure what you’re referring to by top-right box? I can see an icon for a computed styles sidebar, but there’s nothing much in there that isn’t in the other window area? This is on a Pi3 in a PiTop Ceed, so whilst I have keyboard/mouse connected up, my screen size is not so large to display everything without restricted menus (so I might be missing something here)

@sdetweil I can see the two entries (text-align and font-size) in there under element.style when I select the message text.

I’m not sure how this helps us though? Is that what I should be looking to find, the element.style tag?