Guys, like I said, the project is in early status! The tests so far should therefore be understood as a proof of concept. Maybe I could have made that a little clearer in my initial post.

In any case, thanks for the feedback! 😃

Categorizing the messages would certainly also make sense. Like: critical, warning and information.

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

things that depend of features no longer available in the os like vcgencmd

Is vcgencmd really no longer available? I don’t have the current OS version yet, but I can’t find any information about removing it in the documentation:
https://www.raspberrypi.com/documentation/computers/os.html

If so, what would be the alternative?

and omxplayer

Thanks. This is a solid suggestion, just like I was looking for! 😃 I have added this to the check list. There are a handful of modules which contain omxplayer.

I don’t have a concrete approach for your other suggestions.

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

There are also wrong checks. (For example, MMM-ModuleMonkeyPatch …

Ah, I used the module to provoke errors manually. I forgot to remove the folder 🤦. The checks themselves are not wrong.

dependency checking is information ordinary users …

Ordinary users are not the target group for this project. The project collects information about modules, the developers can do whatever they want with the information (even ignore it).

For the core developers it is certainly sometimes interesting (e.g. before breaking changes) which modules still depend on a core functionality.

it would be better to reveal the last update date or the number of unresolved issues to guess the module’s activation level or popularity

Those are good points, thank you! I put them on the to-do list.

Or, if you are going to parse package.json anyway, I think it could be used to organise installation methods, etc.

Yes, I had already thought about parsing the package.json. What do you mean by “organise installation methods”?

I started a small project. It’s still in its early stages and I don’t know where it’s going yet, but maybe it’ll be interesting for you.

Since the quality of the modules varies greatly, I thought about how to automatically detect easily recognizable issues (e.g. typos or dependencies on deprecated packages).

Basically it already works.

This is what it does:

1. Clone all modules from the wiki page: https://github.com/MichMich/MagicMirror/wiki/3rd-party-modules
2. Search each module according to certain criteria
3. Write the result to a file

This is the result of the last check: https://github.com/KristjanESPERANTO/MagicMirror-3rd-Party-Modules/blob/main/result.md

Do you have any ideas about useful checks?

Nice! I think the real-time clock is a useful new feature for the MM. With that we should be able to wake up the Raspberry Pi automatically without any external device.

@Hinge Can you please describe in more detail what you commented out?

@Hacksaw Looks nice. Good work! :smiley:

@Hacksaw There are good Websites that can translate texts - e.g. https://www.deepl.com/. Try again in English and describe more precisely what you want. This is not clear from your current text.

@onkelbobby

Try it with that addition to your CSS file:

.mmm-pth-platform-cell  {
width: 3ch;
}

I’ve never noticed the question mark before. I assume that this is displayed when no real time data is available. I just tried it with Adunistraße and didn’t see a question mark. The problem was probably only temporary on the API side.

Hi @onkelbobby,

nice that you use my fork :slightly_smiling_face:

The reason why the columns have different widths is that you enabled the platform in the first module and not in the others. The simplest option would be to display the column for the second and third module as well. But maybe that doesn’t make sense with this two stops, then you could try the approach of setting the width in your custom.css like this:

table.mmm-pth-table {
width: fit-content;
}

.mmm-pth-time-cell {
width: 10ch;
}

.mmm-pth-sign {
width: 6ch;
}

As @sdetweil says, without more information, no one can help you. Which modules? What error messages do you get? What did you change before the problem occurred?

@sangroma Out of curiosity: How come you used a browser version from 4 years ago?

@Volkae I was able to get the ID easily. I’ll write you a direct message as it doesn’t belong here with this module.

Are you sure that the problem is not the data stream from DB?

No, I’m not sure. You could contact the operator of the API and ask if he sees anything suspicious at the station.

How long did you test the stations?

Only 10 hours. At the moment I don’t have the possibility for longer tests.

It would be nice if we could find and eliminate the cause of the problem. I just don’t have the capacity to delve deeper into this at the moment. An alternative would be to switch to the following module for this station: https://github.com/KristjanESPERANTO/MMM-PublicTransportHafas

@Anthony Contrary to the instructions, you do not need to run npm install for this module. This would only install packages for development, these are not necessary for you to use the module.

The module has not been updated for a long time and has very old dependencies. There is a module that can also use a Rejseplanen API and is actively developed by me: https://github.com/KristjanESPERANTO/MMM-PublicTransportHafas

It looks like this:

This is the configuration of it:

    {
      module: "MMM-PublicTransportHafas",
      position: "top_left",
      config: {
        hafasProfile: "rejseplanen",
        stationID: "8600083",
        stationName: "Kolding St.",
        timeToStation: 5,
        showAbsoluteTime: false
      }
    },

A shot in the blue: Update your npm. I have version 9.6.1.

I have now run “Hamburg Elbgaustraße” for two hours without any problems.

Which version of MagicMirror, which of node (node -v) and which of npm (npm -v) do you use?

@Volkae Please try my fork:

git clone https://github.com/KristjanESPERANTO/MMM-DBF

Let me know if it runs more stable.

Nice! :thumbs_up:

Realy nice 👏 Thank you!

What might work: Install Firefox 47 (this version partially supports ES6 and runs on Android 2.3).

Another approach would be to find a custom ROM for your device. There won’t be an up-to-date version, but maybe at least one that allows you to use a somewhat newer browser.