@ankonaskiff17 @sdetweil Found a new way scorch a Pi on this project.
Had a snap together case I put Pi in, snapped closed and I’ll admit, it to some muscle to snap case closed.
Shortly thereafter I caught the unmistakable odor of burning electronics.
I snapped the SD card so it was bent like 90°
The Pi did not like that.

@notacomputerguy I use weather.gov for both current and forecast per module @sdetweil mentions.
I wrote a marginal explainer over a year ago about how to use weather.gov as provider.
You have to do some pre-work on some pages in National Weather Service website to copy over to the config file weather module section.
I didn’t start messing the MM’s too far back and it is one of those type projects that you have an ah-ha lightbulb go off in your head where you feel like you’ve been fighting with MM and then it all comes together as a unified whole.
Hard part is persevering through and not quitting.

@sdetweil Found my first 3rd party module lacking “request”. Your tutorial worked like a charm

@sdetweil I was just reading the topic about fix for black screen and while I need to read several more times to get my arms around it, I was wondering if I can do those scripts on the files before I copy them over. Instead of ssh’ing in to Pi open terminal go to drive and see if they are problematic before moving?
I would back up exiting files in case I blew something up.

@sdetweil I did use your install script for the core installation and that is all fine and functional. I decided to give 64 bit a try because figured if the base MM didn’t like it, just reformat card and do 32 bit.
Hoping I can put MM SD card in laptop card reader and portable drive with files plug in to USB on laptop and it just be a copy/paste exercise in VSC.

Most of modules I use are pretty basic. I had found a setup I liked and hoping it’s plug and play.

@sdetweil Glad you made it out of hospital.

I’ve been out of loop for a good stretch between Covid & a sick elderly parent but ready to dive back in.

I saved different config and customCSS files which date on hard drive I saved them to are all dated around July 2021.

I have downloaded the base setup on to Pi 4B with the 64 bit Pi OS and it appears to be functioning alright. That was an initial concern and still is an open question as to whether all modules will function correctly.

My other question is whether I can copy/paste my 7/21 dated config.js and custom.css over or am I going to run in to version conflicts with modules that are making calls to 2021 vintage helper modules and other parts. Based on reading the forum email I get I think the answer is probably yes.

To avoid pulling of hair and gnashing of teeth is there a good/easy way to work through the 3rd Party modules I have configured to avoid wasted time and the dreaded “You messed up” screen.
Seems like the default modules should fine as they would have come when I did install script last week.
Issue might be with 3rd party modules that were fine a year ago might be a problem today.

@sdetweil

@mykle1 n66 -->Columbia, SC
Eastern Daylight Savings Time

@techlady Here is my project in progress. My intent is to mount Pi to back of TV and treat MM as another HDMI input.
As others have said, module writers that stick with the convention of using main.css to format their module make it real easy to format multiple modules by using the appropriate block of main.css and dropping it in custom.css.
Gets sticky when a module author does their own formatting top to bottom.

@sdetweil Anything to be done for it? When I have just MM running all is well .
Just seems to be a problem when editing.
So that is coming from the origin point of link?
It is national radar from NWS and I don’t update it locally in config.js
I’ll swag this and guess it generates that Vuex stuff locally when the NWS updates the radar image remotely?