@sdetweil OK thanks - clear.
I’ll have a quick play with the other providers, although the met office are also changing their API in September so probably one to also avoid if future-proofing is desirable.
As you say, so much fun…
Edited to add - swapped to the met office data hub one (not the main one, as that’s the one that’s expiring soonish) and was a fairly painless changeover after getting a new account and API key there. All good now.
@sdetweil Thanks Sam - I recall they were changing but wasn’t sure if that was the root cause here, given it worked prior to the 2.30 upgrade (ie this morning).
Is it worth doing anything for the moment (getting the new api key etc), or is the module code going to change and so maybe better to wait?
Or I see the module can do other providers - is there a recommended one for the UK (as I think the met office here are also screwing around with their API if I remember well)?
I’ve just updated from 2.28 to 2.30 using the script, and it looks to have broken the default weather module.
I run it twice on my display, and one (top-left) is now giving “invalid date” for the date and NaN for the temperature.
The other (top-right) is not showing up at all.
This is the config snippet for their config (api key redacted):
{
module: "weather",
position: "top_left",
config: {
type: "current",
location: "Crawley",
locationID: "2652053", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
apiKey: "redacted",
units: "metric",
degreeLabel: true,
showHumidity: true,
tableClass: "medium"
}
},
{
module: "weather",
position: "top_right",
config: {
type: "forecast",
appendLocationNameToHeader: false,
location: "Crawley",
locationID: "2652053", //ID from http://bulk.openweathermap.org/sample/city.list.json.gz; unzip the gz file and find your city
apiKey: "redacted",
units: "metric",
degreeLabel: true,
fade: false,
colored: true,
tableClass: "forecast"
}
},
MagicMirror-error.log shows this:
[2025-01-05 12:50:19.350] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
[2025-01-05 12:51:17.281] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
[2025-01-05 12:52:17.295] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
[2025-01-05 12:53:16.885] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
[2025-01-05 12:54:16.947] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
[2025-01-05 12:55:16.976] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
[2025-01-05 12:56:16.907] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
[2025-01-05 12:57:16.889] ^[[31m[ERROR]^[[39m ^[[31mError fetching feed: Error fetching feed: 401^[[39m
That’s after stopping the mirror and clearing the log. But looking in the old (massive) log, that error has been there for months.
Is this a known issue, or anything else I can provide to help fix it?
It’s running on a Pi3 (fully updated with apt), and the Mirror upgrade was done using the recommended script.
Rebooting and restarting doesn’t help either, to eliminate a basic…
OK, I think I have it.
Using the window I confirm that the home people are using the same class (whoishome) as the title window.
To get that to work properly, I changed the MMM-whoishome.js line 34 from
html = html + '<img class="person" src="' + this.config.TRACK[this.peopleArray[i][0]].image + '"> ' + this.peopleArray[i][0] + '<BR>';
to
html = html + '<img class="person" src="' + this.config.TRACK[this.peopleArray[i][0]].image + '"> <span class="person">' + this.peopleArray[i][0] + '</span><BR>';
and then the people who are home use class person, which can then be used to configure the colour separately to the header title.
@yedidia - is this something worth adding into the module for better flexibility?
Sorry I’m not good at GH, so have no idea how to submit a PR for it.
@sdetweil - Thanks Sam. Looks like a job for the weekend.
@yedidia - one more quick question.
As mentioned above, I’m trying to tweak the css to show the names for people who are present and away in different colours.
What I’ve done so far via custom.css is :
.whoshome {
color: lime;
}
.person-away {
color: red;
}
Which works, except it changes the title (the “Who’s Home”) as well.
Is there any way to do this and keep the title the original colour to match the rest of the mirror modules?
I tried changing .person rather than .whoshome, but then both the title and people who are home revert to the white that is defined in the css of the module itself.
@yedidia - just updated and also made all the MAC addresses lower case, and now looks to be working.
The colours are rather muted, so it’s difficult to tell at a glance who is actually home (aside from not having a last seen line).
Will look into it more tomorrow, just back from a business trip and rather tired. But thanks again for the good work and useful module!
@rewie85 - Not yet, but it has only been 24 hours since I posted (and installed) it.
Looked good and installed it, but can’t get it to work.
The list is showing up on the Mirror, but never actually sees anyone.
The MAC addresses are in and confirmed as correct, and randomisation iş turned off.
Install instructions also followed, with nmap installed as well.
Is there any easy way to help troubleshoot this?
@mumblebaj said in MMM-NewsAPI:
@DarrenHill Changes have been pushed. You can update the module now.
All up and running - that’s a fix from my side :D
Thanks again for that.
Might have a play with the layout as the pics etc are a bit small (and there’s space to expand things around them in my layout), but I can handle that.