Read the statement by Michael Teeuw here.
Default Weather module still not displaying
-
@sdetweil I added “npm audit fix” as there was 1 high severity vulnerability found. It didn’t solve the vulnerability (didn’t try “npm audit fix --force”), and I’m getting the same error.
Jarhead96097
-
@sdetweil Oh, okay. Let me try that updated string of commands…
Jarhead96097
-
@Jarhead96097 please never do audit… causes more problems than it fixes
-
@Jarhead96097 Rule of thumb is to never run npm audit fix.
-
@mumblebaj and we have found npm install parms to turn off the warning coming in next release, and already in my scripts.
-
@sdetweil That’s great
-
@sdetweil Good to know…that may be the root cause of all of this. After rebuilding my MM on 2.20.0, I did the npm audit fix. If we can’t get to a resolution in the next few minutes, I’ll chalk this up to a learning experience and do another rebuild.
-
May I ask how you are using
classes: "daytime_scheduler"Are there two instances of
daytime_schedulerI use
classes: “currentweather” type: “current”and
classes: “weatherforcast” type: “forecast”to replace the deprecated modules.
-
@Jarhead96097 use my install script
-
@sdetweil “On branch master,” and up to date with origin/master. I also meant to reply earlier that this is on a RPI 4B. Unfortunately, still getting the same error and the weather module is not displaying information.
I appreciate everyone’s time…but I’m going to cut to the chase and rebuild using your install script.
Thanks again for the time, you’re always very helpful, and I appreciate it.
