@sdetweil yeah that’s what I ended up doing. Thank you again for all your help the last few days! Glad to have everything back to normal.
Read the statement by Michael Teeuw here.
Latest posts made by angeliKITTYx
-
RE: Version 2.30.0 weather module, stuck loading, worked fine before upgrade
-
RE: Version 2.30.0 weather module, stuck loading, worked fine before upgrade
you can see on the right module it says “America/New_York” which is my timezone city, but my lat/lon is set to my home many states south. They used to both say that, but I added the “appendLocationNameToHeader” parameter to the left one to see what it would look like.
Before the API update, it would properly display my home city. I’m pretty sure it’s displaying the correct weather information, but we surprisingly have similar weather to NY right now so it’s hard to confidently confirm.
-
RE: Version 2.30.0 weather module, stuck loading, worked fine before upgrade
@sdetweil not going to lie, but I don’t see anywhere saying we have to use /onecall as the endpoint, but that worked for me for both of my current and forecast modules. The location is stating my time zone city (which is 8 hours north) , but the information seems to be correct when comparing it to a weather website. Thank you for the help.
-
RE: Version 2.30.0 weather module, stuck loading, worked fine before upgrade
@sdetweil After 24 hours, I’m still stuck at “loading…” could you confirm if I have the config set up properly? I signed up for the Onecall 3.0 API subscription, and it says it’s active.
{ module: "weather", position: "top_left", config: { weatherProvider: "openweathermap", apiVersion: "3.0", type: "forecast", weatherEndpoint: "/forecast", lat: "xxx", lon: "-xxx", apiKey: "cxxx", roundTemp: true, showPrecipitationAmount: true, tableClass: "medium", colored: true, } }, { module: "weather", position: "top_right", config: { weatherProvider: "openweathermap", apiVersion: "3.0", type: "current", weatherEndpoint: "/weather", lat: "xxx", lon: "-xxx", apiKey: "cxxx", showWindDirectionAsArrow: true, showSun: false, roundTemp: true, } },
-
RE: Version 2.30.0 Calendar fix for clipping broadcast events
@sdetweil not sure what happened, but I added events to the calendars that weren’t showing up to try and troubleshoot, and now they’re all populated properly… Thanks for all your help with this. Now it’s on to fixing the weather widget.
-
RE: Version 2.30.0 Calendar fix for clipping broadcast events
@angeliKITTYx said in Version 2.30.0 Calendar fix for clipping broadcast events:
@sdetweil I used the command on the MM documents page
git pull && npm run install-mm
But I always had to remove the package-lock.json and package.json too
I just tried it now and it’s not working since I’m in the fix clipping branch. It’s asking me to confirm branch.
-
RE: Version 2.30.0 Calendar fix for clipping broadcast events
@sdetweil I used the command on the MM documents page
git pull && npm run install-mm
But I always had to remove the package-lock.json and package.json too
-
RE: Version 2.30.0 Calendar fix for clipping broadcast events
@sdetweil I deleted it off my Pi and then followed the Manual Install. Then I reinstalled all of my modules. It was a fresh install - I didn’t upgrade it.
-
RE: Version 2.30.0 Calendar fix for clipping broadcast events
@sdetweil I deleted it off my Pi and then followed the Manual Install. Then I reinstalled all of my modules. It was a fresh install - I didn’t upgrade it.
-
RE: Version 2.30.0 Calendar fix for clipping broadcast events
@sdetweil It’s on pi.
I used these instructions, and I also did the “Not Working?” section.