I have been using the MMM-OpeningHours module for a few years now and it has always been working great and probably still works for all users of the modules by @Menturan . Thanks for an awesome module.

Google has replaced the library @google/maps with a newer library @googlemaps/google-maps-services-js. I must mention that the old library still works.

I have updated the module to use the latest library from google and have refactored the node_helper.js code a bit. I have also update the package.json and the README and have opened a PR. As the module has been last updated about 3 years ago I am not sure if it is still maintained.

If anybody want to switch to the newer version you are welcome to use my fork. I just love this module as I can track all my fav places.

You can find the fork here: MMM-OpeningHours

@sdetweil A few things:

The main issue being:
MagicMirror is now using a flat npm config, and the start scripts are handled differently, node --run start:x11 is not a valid Node.js command — unless you are using a custom wrapper or an internal script, this will fail silently or do nothing.

As Crontab runs in a minimal environment, so any graphical (X11) application must explicitly export DISPLAY. Previously I had the command as DISPLAY=:0 npm start. Now, I had to export DISPLAY=:0 first and then start MM.

@sdetweil Stupid question, how do I mark this as resolved?

@sdetweil Hi Sam. I have always used npm. I have just been reading through the PR-3764 and i agree with your arguments in that it could have breaking affects for how we do things as both users and devs. Case in point.

However, the forum is about new things and moving forward, so I agree with @KristjanESPERANTO on that point of view as well.

I have now resolved my script issue and am now able to launch from the cron again. 😉

For somebody who may have the same issue, this is how I solved for it.

export DISPLAY=:0
cd ~/MagicMirror
npm run start:x11

The above has solved it for me now.

@KristjanESPERANTO Thanks Kristjan. But I don’t see how updating MM could cause this. I only updated MM with Sam’s upgrade script. Don’t see how that has changed anything with regards to how Crontab works. Maybe it is related to changing the launch to node --run start. I can see the command being fired in the log but it does not launch MM like it did before the upgrade.

Anyhow, I manually launch it for now till I find a suitable solution.

@karsten13 Understood. Will do the add blocker thingy…

@sdetweil Yep, only MM update. Let me try start: node --run start:x11 and see what happens.

@sdetweil in my user, crontab -e. It worked just fine until I updated my mirror this morning. I don’t use pm2 on my installation for my own reasons… 😉

@KristjanESPERANTO Sorry, typo, it is lower x. It start when I manually run npm start. When I manually run node --run start:x11 it works fine. When I manually run the script ./mm.sh it works fine. When calling it from the cron nothing. In my log I see the command node --run start:x11 but MM does not launch.

Hi,

Is there anything that can be done about the add at the bottom left of the Forum? It is blocking the posts. This was gone for a while but is now back and is a nuisance.