Posts made by DarrenHill

@mumblebaj Nothing I can see that’s relevant to MMM-NewsAPI:

http://paste.debian.net/1231616/

The config error (around line 98) was me trying a few different things in the set-up , and made a typo (forgot a comma).

Neither of the modules are giving any response for me. MMM-News was working about a week ago, and then just seemed to stop (or at least not display anything).

Has the BBC stopped making their feeds available to the API, I can’t see anything from them in the stream if I look via their website…

@mumblebaj - Thanks for the reply.

I corrected the case, but it’s made no difference.

Yes npm install ran on the folder after doing the git clone (and run again just now to check).

One thing I did notice when going onto the API site is that there doesn’t seem to be any content from the BBC in the feed. Shouldn’t affect the config above as it doesn’t use that domain for the moment, but may explain why the original MMM-News stopped working.

Also can I just confirm that MMM-News is now depreciated, and that MMM-NewsAPI is its successor (as you are author of both)?

I’m trying to set up this module on my mirror, as a replacement for the “MMM-News” one which seems to have stopped working.

I tried a few configs including the example ones (adding in my own API key) but all i get on the mirror is the title and nothing else?

The API key itself is working fine (tested via their website) but nothing is coming through to the mirror.

My config entry is below - can anyone see an issue?

                {
                        module: "MMM-NewsAPI",
                        header: "news",
                        position: "bottom_bar",
                        config: {
                                apiKey: "<redacted>",
                                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: "Cnn.com,Sky.com,News24.com",
                                        excludeDomains: "",
                                        language: ""
                                        }
                                }
                },

I used to have just BBC.co.uk in the old one and it worked fine, but now I can’t get anything to work?

@sdetweil - I did it via your update script, and it has updated Node from v10.x to v16.x (or at least that is what appears to have happened from what I could read).

It’s quite an old install that just sits on my desk and largely gets left to its own devices. It is in a PiTop Ceed rather than a true mirror, and basically the only thing it runs is MM (it’s actually a dual-boot via PINN also with RetroPie, but the Raspi OS partition is essentially only MM). So no need to keep things focussed to one app or anything like that - no issue of cross-contamination.

All is working fine after the update though, so no problems.

@sdetweil OK, thanks for the pointer.

Always kinda worried when that style of message pops up, for security and suchlike.

I see from the update that my node is very much out of date, so now just backing things up before setting the update script onto it to try and bring that up too.

Just wanted to say thanks for the fix here.

Did an update and hit exactly this with MMM-GmailFeed and the request module.

Installed it back (with an audit fix afterwards) and now all up and running again :)

Thanks, that makes sense, and indeed Chrome is happily remembering the setting too.

I wasn’t sure whether the zoom was being applied pre- or post-rendering. But your explanation makes sense, and the solution of doing it “manually” works fine.

My “mirror” is actually being used as a desktop display, running on a Pi-Top Ceed with a 14" display on it. Got it set up exactly as I want, using a config file zoom setting of 0.6. On the display it works perfectly.

Just now experimented with setting the mirror up as a server as well by tweaking the address and ipWhitelist, and whilst it’s also working I notice that it’s not taking the zoom config entry into account that way.

If I just connect to the mirror with Chrome on my PC everything is oversized and all the modules are covering each other. Changing the zoom in Chrome to either 50% or 67% makes it look fine (annoyingly Chrome can’t be set to 60%!).

Just thought I’d report it here anyway. Not a major issue at all, but for completeness towards making this excellent project perfect :grinning_face_with_smiling_eyes:

You’re welcome - glad it’s finally working for you :)

@sonicgoose - Note the (mis)spelling of the config parameter for columns - the config entry is “showDeviceColums”, not “showDeviceColumns”. It is missing an n, and needs it removed to work (or the script corrected for it).

See my config example above, which works. Yours is wrong as (ironically) it’s spelt correctly!