@sdetweil doing this in some of my own modules so I’m allowed to say this ;)

@swvalenti one addition: Only modules are affected which rely on that request is intalled in core mm (which is a dirty hack of the module developer), modules which install request on their own are not!

@0m4r we had similar discussions already here

could fix the black cursor with an entry in custom.css:

html {
  cursor: none !important;
}

Can you test if this works on your side? If so we should change this in main.css (will provide a PR then).

@majorc said in Cursor shown in v2.16.0:

Or do I have to wait for version 17?

In v2.16.0 we have electron v11, in current develop branch (which will become v2.17.0 in October) we have upgraded to electron v13.

@majorc said in MMM-RAIN-MAP (new: version 2.x):

Does anyone know a map, with transparent or light transparent background?

may not exactly what you want but I’m using this map

        mapUrl: "https://tiles.wmflabs.org/bw-mapnik/{z}/{x}/{y}.png",

which is nearly uncoloured.

@pat59 Wenn man selbst zu faul ist Google Translate zu benutzen dann sollte man sich nicht wundern, wenn man hier keine Antworten erhält.

I think we should open an issue in the github repo to discuss the moment stuff there, if it should be replaced and with what. Found this article.

In the current mm release 2.16.0 request is still a dev dependency but it is now totally removed on the develop branch (and so in the next release).

@Jalibu v2 LGTM.

But you have still an error in the README:

You want beer but you’re getting only coffee ;)

There are 2 use cases for which was https implemented:

• serveronly
• clientonly

This use case with output from the pi on the screen and accessing the mm url’s with https was never implemented.

The above hack from @rafhtl seems not to work with the current electron version.

You can get it working if you put the following lines under the line with mainWindow = new BrowserWindow(electronOptions); in js/electron.js:

mainWindow.webContents.session.setCertificateVerifyProc((request, callback) => {
    callback(0); //this means trust this domain
})

And electron must use https so you have to change the prefix in the following lines to https in the else section or put tls: true, in the config.js.

I’m interested in this usecase because I see nothing what could be protected with https. Everybody who knows your url e.g. https://192.168.0.33:8080/ has full access to your config calling https://192.168.0.33:8080/config/ and can see all your secrets, so I would never run MM in public without protection.