@HeikoGr - What are you seeing for the header? Does it say [country]/[city] and if so, is it correct? Mine is saying “America/New York”, when I’m in Canton, Georgia.
Read the statement by Michael Teeuw here.
Posts
-
RE: v2.29.0 weather module issue
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
@sdetweil - Oh okay - I was wondering why you mentioned case. That was just a typo here on my part. When I was using it, it was “locationID”.
-
RE: 2.29.0 Weather Module w/api v3.0 works, sort of…
@sdetweil - Hi Sam! I’m not even calling locationID in my script.
Here’s what I have:
module: “weather”,
position: “top_center”,
config: {
weatherProvider: “openweathermap”,
type: “current:,
weatherEndpoint: ‘/onecall’,
lat: ‘34.17188’.
lon: ‘-84.57056’,
apiVersion: ‘3.0’,
apiKey: 'nunya” -
RE: v2.29.0 weather module issue
@dawookie1979 - just add it somewhere in the config for your weather module. I added "apiVersion: “3.0"” just above the apiKey.
I’d help you write yours, but I’m struggling with mine as well so you might get better assistance from the gurus here!
-
2.29.0 Weather Module w/api v3.0 works, sort of…
Updated MM2 today to v2.29.0. Learned quickly that the api change forces you subscribe to the One Call v3.0 and provide a payment method but no big deal as long as you stay under 1000 calls per day.
It took some configuration editing to get the current and forecast sections working, specifically adding the apiVersion parameter and of course the new api key. It still didn’t work, so I added weatherEndpoint ‘/onecall’ and this resolved the problem, but now the location header reads “America/New York”. If you use One Call , the location and locationId parameters are ignored. Just not sure why the first shows incorrectly.
Anyone else having this issue?
-
RE: v2.29.0 weather module issue
@dawookie1979 - Be sure to add apiVersion: ‘3.0’ to your config
-
RE: MM2 screen goes black after a couple of hours.
@Eli said in MM2 screen goes black after a couple of hours.:
@reilley
I See this happen also on my mirror from time to time.
I have not verified it, but to me it seems a memory issue.
I faced it often when loading many background pictures in short intervals. I changed my interval to a longer period and also resized some images.
That helped a lot.Hi Eli! I increased the time from every minute to every two minutes to see how that works out. I haven’t tried resizing the files but that sounds like a great idea.
Thanks!
Terry -
RE: MM2 screen goes black after a couple of hours.
@sdetweil said in MM2 screen goes black after a couple of hours.:
@reilley can u tell me what other modules you use?
easy list from the commandline
grep module: ~/MagicMirror/config/config.js | uniq | sort -hHi Sam! Sorry for the delay but I don’t get alerts from this board for some reason.
To answer your question, I use these modules:
Alert
Calendar
Clock
MMM-CalendarExt3
MMM-GoogleCalendar
MMM-Rain-Map (currently commented out)
MMM-SmartWebDisplay
MMM-Wallpaper
Newsfeed
Update notification
Weather -
MM2 screen goes black after a couple of hours.
Hello,
I’m on v2.28.0 , running on an RPi 3 model B rev 1.2 running Bullseye v11.
The screen saver is not activated on the Raspberry Pi and I don’t use screen blanking modules. I do use MMM-Wallpaper since sky setup is not a mirror. For some reason after a couple of hours, the MM screen will go black but I can see the mouse pointer. I can hit CTRL-Q and exit MM2 and then restart it, but it’s inconvenient to do that.
Has anyone else seen this issue and if so, how did you resolve it? I’m not seeing any error messages upon exit of the application.