my pi zero 2w was delivered today and I’m really surprised about the good performance.

Tested 2 apps:

• mm as docker setup
• motioneye with google drive upload (also docker)

Both worked out of the box and felt not slower as on my old pi 3b.

@sdetweil said in MMM-Fuel black screen:

the release upgrade moved us from 17 to 19

no, we were already on v19 with release v2.20.0, now we are on v19.1.0 (not v19.0.15)

@fozi thanks but … no

would be better to have a solution without https, may someone else gets this figured out.

As an improvement for the above solution with https:

Holding the certs in the config directory makes them accessible from outside so better move them into a new directory beside config, e.g. certs which is not exposed. Don’t forget to update config.js afterwards.

@ajoreis said in Black screen on the radxa ROCK 2F, using docker:

Segmentation fault labwc

that tells you that labwc crashes, further investigation without having the used hardware is impossible.

@wishmaster270 said in electron-rebuild problems with MagicMirror 2.22.0:

Edit: Do not misunderstand me. In my opinion the best way to solve the electron-rebuild problems of a lot of modules would be to put “@electron/rebuild” as a dependency to “package.json” of MagicMirror.

I don’t have a final opinion on that yet, but if so, we should put it under optionalDependencies as electron

see https://www.bleepingcomputer.com/news/security/dev-corrupts-npm-libs-colors-and-faker-breaking-thousands-of-apps/

@retroflex thank you, your’re right.

Checked this again with this unmerged pr. With this pr, the config.js is no longer reachable per browser, so we have to wait for the next release where this is hopefully merged.

@Jessendelft other possibilities:

• you can whitelist the ip adresses which are allowed to access the mirror
• you run 2 instances of the mirror, one private restricted to localhost access and one public with content everyone is allowed to see

@sdetweil

you can use --omit=optional as param for npm install, I use this for my amd64 images because they are run to 99,9% with npm run server so electron is not needed

@sdetweil said in Alt Key Doesn't Open Menu:

I see how to do the disable in code, but we don’t do that.

we are using frame: false in electronOptions

@oberfragger yes, in the mm folder

we are at "@fortawesome/fontawesome-free": "^6.2.1"

@sdetweil

The sandbox error is mentioned in this github electron issue. It’s a chromium bug and everything should still work normally.

can reproduce it if I use a nonexisting mapUrl, so I think you have a typo in your mapUrl …

@tippon

you can add the following in css/custom.css:

.module.newsfeed {
  height: 200px;
}

you can play with the height value.

@sdetweil

the missing node-fetch in package.json of MMM-RemoteControl was fixed 19h before so I think you installed the fixed version and rhbauman not …

@spitzlbergerj

you can try the ip-address of the pi in config.js as address: instead of "0.0.0.0".

@sdetweil

well, npm install would have installed the devDependencies too…

This sentence clicked in my brain.

I have NODE_ENV=production as default in my images (expect images I use for testing) and with this

• npm install will install nothing
• npm install node-fetch@2 will install nothing

so @codac please go again in the folder of the module and run NODE_ENV=test npm install node-fetch@2

this should hopefully solve the issue

see https://github.com/MichMich/MagicMirror/issues/2831

@jca2112

this is a bug introduced with last mm version.

Let me know if you are willing to open an issue here, otherwise I will do …

@MajorC

see https://github.com/MichMich/MagicMirror-Documentation/pull/134/files

will hopefully soon merged into official documentation (there are merge conflicts …)