@karsten13 Understood. Will do the add blocker thingy…
Read the statement by Michael Teeuw here.

Posts
-
RE: Starting MM Crontab
@sdetweil Yep, only MM update. Let me try
start: node --run start:x11
and see what happens. -
RE: Starting MM Crontab
@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… 😉 -
RE: Starting MM Crontab
@KristjanESPERANTO Sorry, typo, it is lower
x
. It start when I manually runnpm start
. When I manually runnode --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 commandnode --run start:x11
but MM does not launch. -
Adds Blocking Posts
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.
-
Starting MM Crontab
Hi.
I have been using crontab to start my MM for ages and it has always worked well. After updating it no longer seems to work. cron calls a script that has the following.
cd ~/MagicMirror DISPLAY=0 npm start
Now, I have seen that it is suggest to use
node --run start:X11
going forward and I have updated my start script with same but that does not seem to work either.So my
mm.sh
now looks like,cd ~/MagicMirror DISPLAY=0 node --run start:X11
But as mentioned, this does not work.
Any ideas?
-
RE: MMM-Growatt
@nowayto Hi. That sounds more like something else. Have you checked the logs to see if you see any errors during the time when there is no update? Let me know if you see anything.
The retry will try 3 times, first after 1000 milliseconds and and then at 2000 milliseconds and the last time at 3000 milliseconds and will return a warning. The next time it will try is at the refresh interval which is whatever value you have set.
You can update if you want to check this out. You can let me know if you experience any issues.
I am thinking about making the retry interval configurable but not sure if it is warranted at the moment.
-
RE: MMM-Growatt
v2.2.0 Upgrade
I have decided to refactor the code to make it a little easier to manage
- Update growatt library to latest
- Added helper functions
- Add a connection retry in cases where connection to the Growatt server is down or interrupted
- Add better error handling
Current users do NOT have to update to the latest version unless you want to be on the latest version.
If you do decide to upgrade and experience any issues, please open an issue on the MMM-Growatt Github page.
The same updates were applied to the MMM-Growatt-Stats module. If you update and experience any issues please open a ticket at the MMM-Growatt-Stats Github page.
-
RE: MMM-WOTD
@Niggich Have you also check for any errors in the Dev console (shift + ctrl + i)