@sdetweil - Thanks for both the update on the pm2 restart and on the reminder that the OP’s system structure is different.

OK, back to newsfeed behavior…

@foggy - @sdetweil may be onto something. I jsut added your url to my config.js file and I now get the BBC just fine.

I also wonder whether the "{ " and “}” brackets are required but missing in your feeds array? I have each feed url in its own brackets and it works for me. See my config below, modified to add your BBC url.

@sdetweil - related question: In the[recent] past my system has always restarted Magic Mirror when i commit a change to config.js using control-O, but lately it doesn’t and I have to manually restart MM. Is this expected behavior?

Here is the file MagicMirror/config/config.js now correctly displaying BBC news.

{module: "newsfeed",
     disabled: false,
     tableClass: "small",
     position: "bottom_center",    // bottom_center bottom_bar
     config: {
     feeds: [
        { title: "New York Times", url: "https://rss.nytimes.com/services/xml/rss/nyt/HomePage.xml" },
        { title: "BBC", url: "https://feeds.bbci.co.uk/news/world/rss.xml"},
        { title: "Las Vegas Review Journal", url: "https://www.reviewjournal.com/feed/" },
        { title: "Detroit Metro Times", url: "https://www.metrotimes.com/detroit/Rss.xml" },
           ],
           reloadInterval: 600000, // Content fetch interval - 600000 = 10 minutes
           updateInterval: 15000, //Display new headline interval - default = 10000 milliseconds / 10 seconds
           showSourceTitle: true,
           showPublishDate: true,
           broadcastNewsFeeds: false,
           broadcastNewsUpdates: false
                } },

@MMRIZE
OK - thanks. Maybe I will give it a try…

@MMRIZE
Do you know whether the install script developed and maintained by @sdetweil would install on various specified versions of Windows [E.G. Win7, Win 8, Win 8.1, Win 10 or Win 11]? if that script will install on the various implementations of Windows, that would likely solve this question of how to do it.

Kristian - do the links to the modules listed as numbers 7-10 need some validation? :)

@sdetweil - Sam, I know you don’t have the answer either. I guess I was partly venting, and partly trying to be complete so that others who are having issues or questions can see that various of you and us have tried to work this through.

@sdetweil – Hi Sam. I guess maybe my central point got lost in transit - which is I just want[ed] to know from openweathermap.org whether they can tell me if the API key they issued last year (around the time it became apparent ver 2 would be deprecated) is a ver 3 or ver 2 key. FWIW, I did try one final time and explicitly asked only whether they can tell me the version of key I have. They did respond to the email, but did not address the question.

Yes, I’m sure you are correct and it probably is simple from their point of view. However, the issue is that they are [apparently] currently servicing both the old and the new APIs, so from the user’s side it is not possible to do what they and you are suggesting and just see if calling with the old key generates an error.

If I run my MagicMirror and the API that openweathermap.org issued me last year is the old API the module will still work, so there is no diagnostic value there. Yes, I do see that when the point in future time comes that they shut down responding to calls using the ver 2 API and only respond to ver 3 - then all our modules that are calling with ver 2 APis and modules using old endpoints will fail.

My goal was to get ahead of this and avoid having the modules fail, or in the alternative having to replace the API keys in every module in every MagicMIrror where it is used - just in case they issued me a ver 2 API key last year.

Thanks again to you and Krisjan for all the help and support!

@KristjanESPERANTO - FWIW, openweathermap are not being very helpful in this transition.

I see in my notes the API key I am using is from 2023, but I have no record of what version it is, so I went on their site to see… They don’t specify, either.

I sent them an email requesting how to determine whether the key I have is already compliant, or i I need to start working on applications. The response email just repeated the warnings around them deprecating the old and people’s need to replace ver 2.5 keys with ver 3.0 keys.

I did send a follow-up email asking for a response to my specific question o how to know whether a particular key will work into the future, but received no response.

As such, I am beginning to experiment with my development instance to see what I need to do…

@KristjanESPERANTO - am I misreading or does MMM-OpenWeatherMapForecast appear on both the first and last list? THANKS for the thorough review!

@jbat66 - yes, it is frustrating to know or hear that severe weather is nearby, but the module seems incapable of being configured to display alerts as needed.

@Gjones93 - as the author, can you provide any input?