Looking for Beta-testers!

[dejayou]

This post is deleted!

[KirAsh4]

@pigreco, I didn’t expose the other clock hands to be easily accessible to change the colors on. I’ll have to add that in in a later update. As @MichMich said, making changes to those core files will cause git to start complaining at you.

[bscarano]

I’m now on Develop. Will this update automatically or will I need to run something periodically?

[KirAsh4]

@bscarano, regardless of which branch you are on, you are in charge of your mirror, including updating the code.

[MichMich]

@bscarano To update to the latest version, you’ll need to pull the latest changes. This can be done using: git pull (from the command line within your MagicMirror² folder).

[kckndrgn]

I am now on the development branch.
I have verified that the changes fixed my “blank screen” with the language set in the config file.

Thanks!

[MichMich]

Update: More detailed error message in case config file couldn’t be loaded.

Please let me know if this works for you.

PR: https://github.com/MichMich/MagicMirror/pull/391#issuecomment-237919625

[MichMich]

Please test the following PR:
https://github.com/MichMich/MagicMirror/pull/416

It’s merged into the current develop branch. If you are on the develop branch, please use git pull to update to the latest version.

Thanks!

[Bangee]

I’m now on the latest DEV version.

I had some problems to run it with my PIR Sensor.
this command helps to run it:

npm rebuild --runtime=electron-prebuilt --target=0.37.8 --disturl=https://atom.io/download/atom-shell --build-from-source

IpWithelist:
I’ve added my Subnet to de Withelist, but I can’t access my MagicMirror using a browser:

This device is not allowed to access your mirror.
Please check your config.js or config.js.sample to change this.

Would it be possible to add something like “Your IP-Adress: 192.168.0.99”?

ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1", ["192.168.0.99", "192.168.0.254"]],

This sould add a range from 192.168.0.99-192.168.0.254, or am I wrong?

Thanks for your help.

[MichMich]

@bangee: Check your node log. It should tell you which IP is trying to access the server. Good idea to add it to the “access denied” message. Will put it on my todo list. (PR is welcome!)