I figured it out. I use the free plan, so I cannot use API version 3.0. I have to use API version 2.5. Furthermore I have to use the /weather endpoint.
I got it working again by adding these 2 settings:
apiVersion: '2.5'
weatherEndpoint: "/weather"
I figured it out. I use the free plan, so I cannot use API version 3.0. I have to use API version 2.5. Furthermore I have to use the /weather endpoint.
I got it working again by adding these 2 settings:
apiVersion: '2.5'
weatherEndpoint: "/weather"
@howest
You are not the only one. I’ve never heard of it before until it broke my mirror (I’m using x11).
I got it working again by switching to the V3.0 API on OpenWeatherMap.
And remove these two lines:
apiVersion: “2.5”,
weatherEndpoint: “/forecast”
I updated MagicMirror the other day.
But now there is an issue: the mirror does not get weather info
— config.js snippet —
{
module: “weather”,
position: “top_right”,
header: “weersverwachting”,
config: {
apiVersion: “2.5”,
lat: “52.xxxxx”,
lon: “6.xxxxx”,
apiKey: “xxxxx”,
appendLocationNameToHeader: false,
type: “forecast”,
decimalSymbol: “,”,
colored: true,
fade: false,
weatherEndpoint: “/forecast”
}
},
— end —
(lat, lon and apikey are obscured for privacy)
So I pressed Ctrl+Shift+i and filtered on weather.
I this message: [weather] provider initialized, location: null (weather.js:177)
@atwist
I know this may be a bit late, I had the same problem on my Raspberry Pi3 after I updated to the latest MM.
I spent some time trying to get Wayland running, but wasn’t really successful. Finally, I changed my mm.sh script to:#!/bin/bash
cd ~/MagicMirrornpm run start:x11
And that got it working again using: pm2 start|restart mm
I got something similar, my version of mm.sh:
#!/bin/bash
cd /home/pi/MagicMirror
DISPLAY=:0 node --run start:x11
I figured it out. I use the free plan, so I cannot use API version 3.0. I have to use API version 2.5. Furthermore I have to use the /weather endpoint.
I got it working again by adding these 2 settings:
apiVersion: '2.5'
weatherEndpoint: "/weather"
@sdetweil yes, still happening.
just noticed this second page, trouble shooting now. I get a 401 unauthorized error.
I have the same issue. These are my settings:
module: "weather",
position: "top_right",
config: {
lat: "52.262524",
lon: "6.797571",
apiKey: "****",
appendLocationNameToHeader: false,
type: "current",
degreeLabel: true,
decimalSymbol: ",",
showWindDirection: false,
showFeelsLike: false
I’ve copied all options and the calendar still works. Problem solved, but no clue what the problem was…
I’d like to thank everyone eho helped me figuring this out.
I’ve done some more testing and I figured out that must be some option in my config.js that causes my problem.
My calendar works when I load the config.js.sample and paste the url of my calendar in it.
Guess I’ll have to do troubleshooting to do…
(no worries about the calender link, I will change it after I’m done testing. It has some bogus appointments in it.)
{
module: "calendar",
header: "Agenda",
position: "top_left",
config: {
broadcastEvents: false,
calendars: [{
url: "https://calendar.google.com/calendar/ical/gjv.de.groot%40gmail.com/private-5652f141b7d1dbb385f50a786a34827a/basic.ics"
}],
dateFormat: "D MMMM YYYY",
fade: false,
getRelative: 0,
hidePrivate: true,
maximumEntries: 8,
maximumNumberOfDays: 7,
maxTitleLength: 50,
showEnd: true,
showLocation: true,
timeFormat: "absolute",
urgency: 1,
useRelativeDates: false
}
I cleared my entire calendar to be certain there were no appointments that would cause the problem, problem still occurs.
I can download basic.ics without a problem.