@plainbroke

Hi,

try this:

crontab -e with connected user:

05 20 * * * /usr/bin/pm2 start mm
15 07 * * * /usr/bin/pm2 start mm
30 21 * * * /usr/bin/pm2 stop mm

• sudo crontab -e is not necessary.
• I do not understand the start at 20:05 (first line)
• my pm2 is in /usr/bin
• always use full path in crontab

If you’re not sure where PM2 is you can use find / -iname pm2 in the console. Important is the full path in crontab.
/home/chris/.nvm/versions/node/v22.9.0/lib/node_modules/pm2/pm2 would be an alternative for me.

@waynerob11
Please send the error massage that you receive. I want to help you!

@sdetweil
Hi,

I’ve updated the node _helper.js.

//const fetch = require("node-fetch");

If some has trouble it can be reactivated. Maybe I hab installed node_helper in the past manually. I don’t remember. Until now I had no errors from that. But yes, it woks well without this line.

@KristjanESPERANTO yes, why not!

@chrisfr1976

I’ve found it!

.CX3 .weekGrid {
  display: grid;
  width: 100%;
  grid-template-columns: repeat(7, [cell-start] 1fr [cell-end]);
  grid-auto-columns: 0fr;
  margin-top: 5px; /* ADD THIS*/
}

@bobbylx
Hello,

for the radius update the css and add a border-radius in .CX3 .cell:

.CX3 .cell {
  border: 1px solid var(--celllinecolor);
  background-color: var(--cellbgcolor);
  height: calc(
    var(--cellheaderheight) + var(--cellfooterheight) +
      calc(var(--eventheight) * var(--maxeventlines))
  );
  position: relative;
  border-radius: 25px; /*adjust as you like it*/
}

But it might look strange if it is too big. This radius is valid for every calendar cell of course. I use it, too with 3px only.

Result with 25px:

For the other issue I’m also searching for a solution. You can see it my picture :)

I had this idea:

CX3 .week {
  width: 100%;
  padding: 0 5px;
  margin-top: 5px; /*this helps but is stupid in the next week*/
  height: calc(
    var(--cellheaderheight) + var(--cellfooterheight) +
      calc(var(--eventheight) * var(--maxeventlines))
  );
  position: relative;
}

Hello,

I had a lot of trouble with other module while the MMM-GoogleMapsTraffic was active. The last commit is more than 7 years ago and there are many open issues. So I decided to rework the module. I’ve sent a pull request of course. Let’s see if the original developer is still active.

This is my fork: MMM-GoogleMapsTraffic

Biggest change: the module has no other dependencies except the MagicMirror anymore. So you can completely remove the old module with all node modules in that folder. An installation is also not necessary. The old config is unchanged. Just restart your mirror!

There is just a warning message left. This is not so easy of fix (Google has changed the markers). So you really need to work n the API to get a new map and so on. I’ll update this, if the markers do not work anymore.

So far everything is fine in my environment. The console shows no errors anymore.

Enjoy!

@alfi153 Okay, there was a delay in your message. Glad to her that everything is okay now. If you need any assistance please let me know:)

@alfi153 Hi,
I think I’ve misunderstood this conversation a little bit.

• you’re using MMM-FroniusSolar3 from me (ChrisF1976 on GitHub).
• On your Fronius Symo GEN24 you activated the SolarApi.
• In the config.js you used the correct IP

I just started it on my mirror and it works without any problems. I also deleted it completely and reinstalled it with “git clone…”.

So the only reason I can imagine is, that there is a collision in the node_helper.js. I used only “SET_CONFIG” to data exchange. Maybe other modules use this, too. I had a lot of collisions already :-)

Go to the node_helper.js and replace:

    socketNotificationReceived: function (notification, payload) {
        if (notification === "Solar3_SET_CONFIG") { //Solar3_ added to avoid collision with other modules

Then go to the MMM-FroniusSolar3.js and replace:

    start: function () {
        this.solarData = null;
        this.solarSOC = null;
        console.log("[MMM-FroniusSolar] Sending configuration to node_helper...");
        this.sendSocketNotification("Solar3_SET_CONFIG", this.config); // Send configuration to node_helper with more specific name
        this.scheduleUpdate();
    },

I this helps, please tell me. Then I’ll update it in general also for the other modules.

If it doesn’t help, please look into the logs (for example with pm2 log mm) and also in logs of electron (I think ctrl+I was the command). I’m running a separate instance on server mode with the port 8081 and a separate config2 to find those errors. I hope you can find the error!

@sdetweil Aha! I need to wear my glasses :)

@rchacon, you can try this:

go to the CSS and do some modifications (better use custom.css):

.CX3 .eventContainer {
  z-index: 20;
  position: absolute;
  top: var(--cellheaderheight); /* try, if too litte space, remove that*/
  left: 0;
  width: 100%;
  height: auto;
  display: grid;
}

then

.CX3 .event {
  margin: 2px 5px;
  padding: 2px 2px;
   grid-row: span 1;
  text-align: left;
  color: var(--calendarcolor);
  display: flex;
   justify-content: flex-start;
  gap: 2px;
  text-overflow: clip; /* Prevent truncation */
  overflow: visible; /* Allow content to overflow the container */
  white-space: normal; /* Allow text wrapping */
  min-width: 0;
  position: relative;
  border-radius: 8px;
}

and

.CX3 .event .headline {
  display: flex;
  flex-direction: row;
  justify-content: flex-start;
  align-items: flex-start; /* Align items at the top to allow height adjustment */
  gap: 2px;
  min-width: 0;
  flex: 1;
  flex-wrap: wrap; /* Allows children to wrap to the next row if needed */
}

If the event title is very long this can be annoying. But is you can control this to keep it a little shorter than “Behandlung von Hemiplegiepatienten in der Spätphase” it can be helpful.

@rchacon Hi, you can add useMarquee:true, in your config. Maybe that’s better. If you have 3 events on one day then you’re already at the limit with the row height if you wrap the text.

@alfi153 Hi, my module is working complete different. I don‘t know the other node_helper. The MMM-FroniusSolar 1-3 use the same node_helper. Version 4 is again different. For inverter settings nothing special is necessary. Is the ip configured corretly?

Which version do you try to use?

Chris.

@alfi153
Hello,
the node_helper.js is the same for module 1,2 and 3. If one of them is not running there must be a config error. Maybe my mistake in the readme. Check what the console messages and/or pm2 logs tell and send me the result. I‘ll check parallel the documentation.

@mariecbilodeau
Hi,
Maybe a new module is needed. I found an approach to get data from your car. Maybe not that easy.

Polestar GitHub

I don’t have a Polestar so it is difficult to support.

@sdetweil
Hi,
yesterday I was off. Now I tried to install it but I got this error:

chris@MagicPi:~ $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/installer/refs/heads/main/installit)"
Klone nach 'installer' ...
remote: Enumerating objects: 257, done.
remote: Counting objects: 100% (24/24), done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 257 (delta 10), reused 17 (delta 6), pack-reused 233 (from 1)
Empfange Objekte: 100% (257/257), 1005.39 KiB | 4.31 MiB/s, fertig.
L?se Unterschiede auf: 100% (151/151), fertig.
Hinweis: Es wird davon abgeraten zu Pullen, ohne anzugeben, wie mit abweichenden
Hinweis: Branches umgegangen werden soll. Sie k?nnen diese Nachricht unterdr?cken,
Hinweis: indem Sie einen der folgenden Befehle ausf?hren, bevor der n?chste Pull
Hinweis: ausgef?hrt wird:
Hinweis: 
Hinweis:   git config pull.rebase false  # Merge (Standard-Strategie)
Hinweis:   git config pull.rebase true   # Rebase
Hinweis:   git config pull.ff only       # ausschlie?lich Vorspulen
Hinweis: 
Hinweis: Sie k?nnen statt "git config" auch "git config --global" nutzen, um
Hinweis: einen Standard f?r alle Repositories festzulegen. Sie k?nnen auch die
Hinweis: Option --rebase, --no-rebase oder --ff-only auf der Kommandozeile nutzen,
Hinweis: um das konfigurierte Standardverhalten pro Aufruf zu ?berschreiben.
Do you want execute the module installer now? (y/N)?y
./installer.sh: Zeile 32: cd: ../../modules/MMM-Config: Datei oder Verzeichnis nicht gefunden
cp: der Aufruf von stat f?r 'module_schema_template.json' ist nicht m?glich: Datei oder Verzeichnis nicht gefunden
node:internal/modules/cjs/loader:1251
  throw err;
  ^

Error: Cannot find module '/home/chris/MagicMirror/installers/formatModuleInfo.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
    at Module._load (node:internal/modules/cjs/loader:1074:27)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:166:5)
    at node:internal/main/run_main_module:30:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.9.0
./installer.sh: Zeile 68: ./install_module.sh: Datei oder Verzeichnis nicht gefunden
node:internal/modules/cjs/loader:1251
  throw err;
  ^

Error: Cannot find module '/home/chris/MagicMirror/installers/runserver.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
    at Module._load (node:internal/modules/cjs/loader:1074:27)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:166:5)
    at node:internal/main/run_main_module:30:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.9.0

@sdetweil i hope that your installer can also uninstall a module … g

@sdetweil it is running on my pi but until now i didn‘t need it. I have no space for a new module left ;)
But i‘ll try tomorrow and give you a feedback.

Hello,

I’ve added a quite special module to the “family” which is exact what I need. Maybe someone else hat also a PV on the roof controlled by the Fronius inverter and in addition a mini-PV system measuring with a Shelly-device. I have exactly that case in my house :-)

So, that’s it: MMM-FroniusSolar4

Added Shelly device in the monitoring:

There is a small flickering effect with the text labels. SVG doesn’t like text with icons inside that much. I have no more ideas how to fix this (I tried a lot). But it is not really annoying me.

One hint: the label text must be modified in the js-file in this part of the code:

        svg.appendChild(createGauge( "Grid", this.config.icons.P_Grid, "top", .............));
        svg.appendChild(createGauge( "Akku", this.config.icons.P_Akku, "bottom", ................));
        svg.appendChild(createGauge( "", this.config.icons.P_Load, "middle",..................));
	svg.appendChild(createGauge( "PV Mini", this.config.icons.P_Shelly, "bottom", ...............));

The "" is the house in the middle :)

@plainbroke
Hi,
my mm.sh also restarts the mirror. But my intention with was doing only a refresh to save a lot of time. My restarts script sleeps 15s before it is executed. So i created a seperate refresh script.

Fixed. IP can now be defined in the config.js:

InverterIP: "<yourInverterIP>",