@KristjanESPERANTO said in Automatic checking of all MagicMirror² modules:

karsten13 has already suggested the GitHub API and I have tested it, but if you make requests for 1000 modules you’ll got blocked quickly. I haven’t found another good approach yet.

2 ideas:

• did you try to authenticate with a user before making the api requests? AFAIR we solved a similar problem at work with authentication …
• if first idea doesn’t work an ugly solution is to work with e.g. a timer or sleep statement because these infos are not changed very often this could be a long running nightly job

@KristjanESPERANTO

from your todo list

Is there also a GitLab API?

yes, as example you can look at MMM-RepoStats

Another thing is what the source of the list should be, still the wiki (which is very error prone since anyone can edit things).

Alternatively, you could store a list in your repo and we need something for users to add to their repo (e.g. as a PR in the repo or with website functionality).

But maybe there are even better ideas.

title of this thread has nothing to do with the problem

@KristjanESPERANTO said in Automatic checking of all MagicMirror² modules:

After you showed me the examples, I tinkered a bit with a simple frontend (without dependencies): check it out. I just have to fill it with real data.

cool, exactly what I thougth of …

looking at your example json

  {
    "name": "MMM-PublicTransportHafas",
    "image": "https://raw.githubusercontent.com/KristjanESPERANTO/MMM-PublicTransportHafas/main/img/Goerdelerring_all.png",
    "maintainer": "KristjanESPERANTO",
    "link": "https://github.com/KristjanESPERANTO/MMM-PublicTransportHafas",
    "category": "Traffic",
    "tags": ["Schedule", "Public Transport", "Traffic", "HAFAS"],
    "text": "This module displays real-time departure times for public transportation.",
    "description": "Stay informed about the upcoming departures from your local public transit stations."
  },

there are only a few things which are not available via github api (image, category).

category and tags are similar, do we still need a category?

tags are similar to api topics (may without magicmirror key words)

@KristjanESPERANTO

it would be better to reveal the last update date or the number of unresolved issues

as most modules are hosted on github: You can get such info’s over their api.

As example you can look at https://api.github.com/repos/MichMich/MagicMirror

@fischi87

out of my head (untested):

cd ~/magicmirror/run
docker-compose up -d --force-recreate

@james3xyx3

maybe better explained with

laMax: Northern edge latitude
laMin: Southern edge latitude
loMin: Western edge longitude
loMax: Eastern edge longitude

@KristjanESPERANTO

there was a discussion long ago here about 3rd party modules because the current format is very ugly.

So maybe this could be also a starting point to have the module list as e.g. yaml output with all current stuff and your analysis results. With such an input it would be possible to generate a website (as mentioned in the above issue, examples how this could look were https://tiny-helpers.dev/ or https://www.electronjs.org/apps) …

@KristjanESPERANTO

from the results:

.gitlab-ci.yml: Change file extention from .yml to .yaml: https://yaml.org/faq.html.

In this case the .gitlab-ci.yml is the default name of the gitlab pipeline definition file (users can change this but 99% will not) so if you really want to check yml vs. yaml you need a whitelist …

@Mats

issue was fixed upstream so I released a new (fixed) version

@Mats

the problem is caused by changes on the flightradar side, I already opened an issue: https://github.com/derhuerst/flightradar24-client/issues/36

A quick and dirty fix would be to go into the module folder (from mm folder) with cd modules/MMM-Flights and then edit the followoing file e.g. with nano nano node_modules/flightradar24-client/lib/radar.js and replace the line at the beginning of the file

const endpoint = 'https://data-live.flightradar24.com/zones/fcgi/feed.js'

with

const endpoint = 'https://data-cloud.flightradar24.com/zones/fcgi/feed.js'

Other possibilities:

• wait for a fix
• you can use another provider in MMM-Flights

@Mats

can confirm this error, will try to fix it later

@sdetweil

I tested language: "nl" and it works so this is no general problem

@sdetweil

yes … but the biggest impact for me is wayland because my docker images don’t run on the new Bookworm release. I need to take a closer look, but it’s too late now …

@sdetweil

Thanks!

Major change is the move from X11 to Wayland.

Legacy images are now bullseye, buster is not available anymore.

@sdetweil

MMM-MyCalendar is a mess, the author copied (meanwhile old) versions of our code into his repo, so the problem is calendarfetcher.js of the module.

@sdetweil

the missing node-fetch in package.json of MMM-RemoteControl was fixed 19h before so I think you installed the fixed version and rhbauman not …

@Freddy_boy

npm install node-fetch will install the latest version which is a v3.x

mm does not support typescript and so needs a v2.x version.

you have to look up the latest v2.x release and install this. This is a problem of MMM-Weather and should be fixed there.

@sdetweil

[03.10.2023 21:02.54.966] [ERROR] Error when starting node_helper for module MMM-Remote-Control:
[03.10.2023 21:02.54.969] [ERROR] Error: Cannot find module 'node-fetch'
Require stack:
- /opt/magic_mirror/modules/MMM-Remote-Control/scripts/download_modules.js
- /opt/magic_mirror/modules/MMM-Remote-Control/node_helper.js

so https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

@croc_dad72

looks like you are on deprecated node version, run node -v which must be >= v18