@sdetweil said in Running on Pi Zero 2 W?:

as addition: pi zero 2 is armv7l

nice article: https://blog.alexellis.io/raspberry-pi-zero-2/

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

@dorianhawkmoon

you can run

MM_CONFIG_FILE=config/config.js npm run server

and

MM_CONFIG_FILE=config/config2.js npm run server

Same works for npm run start.

You have to use different ports in your configs.

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.

@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

@mumblebaj

you can test the following, I couldn’t test this completely but the cors error was gone in my tests.

First yo need to create own certs, go into the config folder of mm (same folder where config.js is located) and run this command:

openssl req -newkey rsa:4096 \
            -x509 \
            -sha256 \
            -days 3650 \
            -nodes \
            -out example.crt \
            -keyout example.key \
            -subj "/C=DE/ST=Hessen/L=Frankfurt/O=MagicMirror/OU=MM/CN=www.example.com"

Then edit your config.js and add the following lines under the line with var config = {

	electronOptions: {
		webPreferences: {
			webSecurity: false
		}
	},
	useHttps: true,
	httpsPrivateKey: "config/example.key",
	httpsCertificate: "config/example.crt",

(Re)Start mm and test if MMM-Hue works now (there will still be a “mixed content” warning).

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

@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

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

@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

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

https://forum.magicmirror.builders/topic/12815/bright-ui?page=1

https://forum.magicmirror.builders/topic/13108/css-experiments-for-newbies

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

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

@oberfragger yes, in the mm folder

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

@sdetweil

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

@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

@tippon

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

.module.newsfeed {
  height: 200px;
}

you can play with the height value.

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