@darrenhill BBC seems to be working fine.

Not sure why yours is not pulling anything. I am using the following config.

                        module: "MMM-NewsAPI",
                        header: "news",
                        position: "bottom_bar",
                        pages: {"sport": "bottom_bar"},
                        config: {
                                apiKey: "API_KEY",
                                type: "horizontal",
                                choice: "everything",
                                pageSize: 20,
                                sortBy: "publishedAt",
                                drawInterval: 1000*30,
                                templateFile: "template.html",
                                fetchInterval: 1000*60*60,
                                query: {
                                        country: "",
                                        category: "",
                                        q: "",
                                        qInTitle: "",
                                        sources: "",
                                        domains: "bbc.co.uk",
                                        excludeDomains: "",
                                        language: ""
                                        }
                                }
                },```

@darrenhill I tested the config that you provided and I am getting results returned from it. MMM-News is still around and can be found here:
MMM-News. MMM-NewsApi is a lightweight version of MMM-News.

Do you see any errors in the terminal or the pm2 logs or in the Dev Window (shift+ctrl+i)?

@darrenhill Your domains are incorrect. Should be all lowercase. Did you also run npm install in the MMM-NewsApi folder?

@fantasmic78 MMM-page-indicator works with MMM-pages and gives you the ability to select pages manually if you like. You would see the below on the page depending on how many pages you have and it is clickable.

@hango Wow, interesting stance you have, I thought this is a learning forum not a feeding scheme. Maybe I will just others who have with replies like these not participated or helped other in need anymore. Go for GOLD @hango

@hango Yeah, got you. Just thought it easier to get the div id rather than adding a class to config.

@mmuser I would suggest that you grab the module_id from the Developer Window|Elements Tab. then use the div id for the module and assign the CSS as per @hango using the div id. If I had 2 instances of MMM-SweepClock in my config it would be assigned module_0_MMM-SweepClock and module_1_MMM-SweepClock

@mlhote I just clicked the link in your Error and it directs to the below.

It seems to be working fine for me though

@mlhote Did you run npm install in the MMM-OlympicGames folder?

@halpi-thousand You need to be in the MagicMirror folder to run npm start. cd ~/MagicMirror then npm start

@kedoth Nicely done. Looks neat.

@sdetweil I would assume that the user may have installed a newer version. MM requires 2.6.6 which is not the ES version I think they changed from v3 onwards.

@extra said in Help. MM doesn't work Anymore:

[23.01.2022 14:55.17.502] [ERROR] Error [ERR_REQUIRE_ESM]: require() of ES Module /home/pi/MagicMirror/node_modules/node-fetch/src/index.js from /home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js not supported.
Instead change the require of index.js in /home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js to a dynamic import() which is available in all CommonJS modules.

This is the wrong version of node-fetch that is installed on MM. You need to downgrade node-fetch to v2.6.1 or something earlier than v3 where the module was change to an ES module. I would uninstall node-fetch and check which module uses it and what specific version and install the correct version.

@landaisbenj I have seen this error before. It comes from installing the latest version of node-fetch whereas the module uses an older version of node-fetch. The latest version is an ES module and must be import’d instead of require’d in the node_helper.

@sdetweil Sorry, mind was thinking “force” but the fingers overwrote with “apply” :-)

@plainbroke There you go. Use the upgrade script by @sdetweil with the apply option and it should sort out your modules’ missing dependencies. If you still have issues then post the logs so we can see what else is wrong.

@sdetweil That is true. But he already upgraded to latest. Not sure if your scripts will fix after the fact?

@plainbroke So, you may want to supply us the error messages that you are getting when you start the mirror. Either the content from the terminal when you start the mirror with npm or if you start the mirror with pm2 then pm2 log --lines 100. There are underlying issues with the modules that you have installed. To get you up and running on 2.18 then you need to provide us with the log output so we can see how to assist. Rolling back to older version of MM may not be the right thing to do. Let’s see if we can resolve the issues.

@onis_uk You would probably have to comment out the code that adds the image in the MMM-Rocketlaunch.js. Lines 232 - 252. Would be best to request a change from the developer of the module on the module Github page to make the image an optional feature.

@thebassfly said in Problems after updating MMM-Homematic:

[ERROR] WARNING! Could not load config file. Starting with default configuration. Error found: Error: Cannot find module ‘request’

The above is your error:

Please see the below for solutions:
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later