Read the statement by Michael Teeuw here.
Unable to determine reason for MM/electron decaying/dying/hanging
-
@max64 said in Unable to determine reason for MM/electron decaying/dying/hanging:
Also, interesting enough, I do use \n in my remote file, and under Stretch and the previous version of MM it did not format the line return on the screen, and I noticed that right off after this most recent load on the RP3.
ok, you do not appear to be having the problem with compliments that the other user was having…
u have troubles with crash/hang…
I don’t use that module for background images.
I have loaded it for testing… don’t see any problem ‘yet’!
-
@sdetweil
Well, woke today to another frozen screen.The only modules running were: clock, calendar, currentweather, weatherforecast, and mmm-nest-status. It was running most of the day yesterday with just the first 4 modules, so I added in mmm-nest-status.
I’ll roll it back to just the 1st 4 default modules again, and see if that will run 24 hours.
As mmm-nest-status appears pretty light weight and has no “npm install” requirements, this still may be an incompatibility between Buster and Electron…
-
@max64 said in Unable to determine reason for MM/electron decaying/dying/hanging:
As mmm-nest-status appears pretty light weight and has no “npm install” requirements, this still may be an incompatibility between Buster and Electron
or a bug in the module…
will look later
-
Getting ridiculous.
Remove mmm-nest-status. Was only running: clock, calendar, currentweather, and weatherforecast. And THAT locked up.
Now removed weatherforecast also.
-
In the end I was never able to get Electron to run properly under MM2 on my Pi3B+ under Buster. My only “solution” has been to run MM in serveronly mode, and then load Chromium separately from a script. This seems to be pretty stable.
-
@max64 with release 2.10, all you have to do is set serverOnly: local in config.js
And it will do that split mode for you.We are running such an old electron version.
