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?

@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.

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.

@Niggich Glad it is working for you now.

@Niggich Have you also check for any errors in the Dev console (shift + ctrl + i)

@Niggich said in MMM-WOTD:

not working with more pages and server mode

Not sure I understand the above.

The module works fine, works with MMM-pages and in Container (server only mode) I have tested this.

Can you check in the logs if you see any errors in the logs and advise?

@plainbroke You can target the selectors specifically in your custom.css like this:

#wotd-we {
  color: orange;
  font-size: 50px;
}

@sdetweil Agreed, all work is the same.

@sdetweil You provide your own list of modules and config alongside your compose and it all gets imported into the container. No need to go fiddle in the container itself.

@plainbroke There are instructions on the Docker website. Follow the link in my post above.