you can put this into css/custom.css file:

.newsfeed-desc {
  display: none;
}

concerning the duplicate weather alerts and mix up between german and english I got an answer from openweathermap.org:

Currently we receive data in such format from the provider. The development team is working on the new version of alerts, which should eliminate such behavior.

@oberfragger said in MMM-OpenWeatherForecast - Replacement for MMM-DarkSkyForecast:

label_sunsetTimeFormat

there is no property label_sunsetTimeFormat, only label_sunriseTimeFormat, remove the not existing one …

@oberfragger

label_sunriseTimeFormat: "k:mm",

@j-e-f-f

I don’t think there is much I can do here.

yes, I’m aware of this. Sent a mail to openweathermap.org and will let you know if I ever get a response …

@codac all these modules have the same position top_right?

For the warnings module you could use custom.css and overwrite the text-align: left; in the module css with text-align: right;

You can also play with css in the browser, e.g. see this thread.

so now i catched the situation where the alerts are in english and in german:

the data is coming directly from openweathermap, here the json-part:

@oberfragger

Still inspecting the storm warning in german…

same problem here, saw meanwhile some of this warnings in german but mostly in english. Looks like a problem on the provider side, when inspecting the called url in the browser the retrieved data is in english.

So this can’t be solved by the module.

there is already a pull request which includes the update to 11.3.0, should be merged within the next days into develop

should be 23 (not 16)

you can do it with or without docker, thats your choice.

With docker you have to use different config.js files, they can be placed in the same folder and must be mapped into the right container.

You could use only one modules folder for all instances by installing all modules there.

Updating the core is done by using a new docker image (same for all instances).

The one-modules-folder may also could be established with the classic setup, you could use symlinks from a central place into the modules folder of the several instances (never tested this!).

2 more things:

• the new branch you are using should start on the mm-branch develop (not master)
• when creating the PR on github you have to manually change the base branch from master to develop

These rules are specific to the mm-repo. Because of quarterly releases the master branch only changes 4 times in a year. The development between the releases is done on develop.

@sdetweil no :crying_face:

may using esm library is one approach as described e.g. here https://blog.logrocket.com/how-to-use-ecmascript-modules-with-node-js/

@lavolp3

• rename node_helper.js to node_helper.mjs

worked in my test (did not do anything with the imported axios, but mm starts).

Link should work now, forgot to make it public :man_facepalming_light_skin_tone:

Hi,

this is my first MM module and may others find it useful :)

Download and infos: MMM-RepoStats

It’s about repository statistics for Docker, GitHub or GitLab repositories:

GitLab with private data (access token needed):

Let me know if something is missing or not solved in the right way, any feedback is appreciated.

Thanks,

Karsten.

@florianrd The komoot api is not public so I asked them to get a key. They answered that the api is only available for partners and provided a website for becoming a partner.

So I sent another mail to the partner mail adress (2 weeks ago) and never got an answer …

@sdetweil I think he deleted here as much as possible intentionally. He left in anger and is starting a new one man show here

everything o.k., the : was a typo here …

you could use a proxy https://cors-anywhere.herokuapp.com/https://dd.weather.gc.ca/citypage_weather/xml/ON/s0000326_e.xmll, there is already such a line in the PullRequest merged today.