@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

@sdetweil

the default weather module still uses 2.5 and it works

at the moment, yes.

I looked into their api stuff and onecall v2.5 is not mentioned anymore. The normal endpoints weather and forecast are still on v2.5.

Problem: For onecall 3.0 you need a special api key (as already mentioned here) with a subsciption where you have to give your payment data (1000 request free per day, limit is 2000 per day but you can set your limit to 1000 if you want it for free … ).

I think we will get problems/questions to this for the default weather module too.

So (for default weather module) if you use endpoints weather and forecast and old onecall v2.5 everthing works out of the box with old api keys, if someone use new onecall v3.0 he needs an api key for 3.0 and has to set apiVersion: "3.0", in the config …

@steak

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

@Ray said in updatenotification:

is it possible to instruct ignoremodules not to look for MagicMirror updates

looking at the sources this is not possible at the moment but it is easy to implement. Can you open an issue on github for this? Thanks.

@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)

@sdetweil

http://pirateweather.net

@wimthoelke

the module is untouched since 4 years which means dead.

You can try this fork https://github.com/KristjanESPERANTO/MMM-PublicTransportHafas

The “&nbsp” part is missing in the fork so may this is fixed there.

I’m trying to convert from MMM-OpenWeatherForecast to something else, but Openweather is confusing me with the API subscription.

same situation here. I like the above module but I don’t want to subscribe to the new openweather api.

First alternative was the mm weather module because it has several providers so you can switch easily. But the design is so far away from MMM-OpenWeatherForecast …

So next approach was to use the data from mm weather for an own module with better UI.

Thats the current output:

It is still a beta version and not published yet.

Another approach could be to extend the mm weather module with configurable njk templates and the cool skycons (which can be animated) …

@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.

@retroflex thank you, your’re right.

Checked this again with this unmerged pr. With this pr, the config.js is no longer reachable per browser, so we have to wait for the next release where this is hopefully merged.

@Jessendelft other possibilities:

• you can whitelist the ip adresses which are allowed to access the mirror
• you run 2 instances of the mirror, one private restricted to localhost access and one public with content everyone is allowed to see