Looking for Beta-testers!

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

Bangee

@MichMich Thank you. I’ve had to update my config:
the Log told me:
Access denied to IP address: ::ffff:192.168.0.99

It works with this:

ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.0.1/24", "192.168.0.1/24"],

Jopyth

My mirror is now also running the development version, and I am experiencing restarts more often than before. I guess it is related to # 150 since there is no error in the log. Anyway I saw this twice yesterday, but this might just be something with a newer electron version, so maybe nothing we can fix. It is still a little bit annoying.

@MichMich By the way, do you have any particular date in mind for the release?

MichMich

No, can’t give you an ETA.

Keep me posted on the restart issue.

Jopyth

I am a little bit in the dark on the restart issue. It happens every time I change any file in my source code directory, i.e. config/config.js or even package.json.

All I have so far, is this appeared after I updated to development branch (hence updated all npm dependencies), plus I had to update my PIR-Sensor module (got a version XX expected, got XX error), and rebuild dependencies there also.

Does anyone have any idea on this? And is anyone else even seeing this behavior also? If I have time, I will try a complete reinstall and see if that fixes it.

MichMich

Arent you running any tool that watches your directory and restarts? Like nodemon or pm2?

Jopyth

I am using pm2 but watch & reload was disabled.

I did a complete update, which apparently helped people before with #150, that seems to have fixed it:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt-get clean
sudo rpi-update

gismo2006

@Jopyth some time ago my mirror suddenly didn’t work whit pm2. From one day to the other. I changed nothing and it works fine before. I didn’t know what happens. But then I found a little order in the display when I prompt pm2 start mm… I didn’ t rember the order but I know pm2 worked some second displayed something and then everything works fine again. …

Maybe you found something , too

Greets gismo

MichMich

Guys, I’ve just made a modification that hides a region if all modules in a region are hidden. This should prevent unwanted margins when a region (like the top_bar) only contains hidden modules. This allows my to move the updatenotification module to the topbar.

Due to the nature of the change, this could cause some serious issues if it contains any missed bugs. It would be great if you guys gan pull the latest version and let me know if everything keeps working. If you’re having issues with some modules not showing up, please let me know.

More info about this change can be found here: https://github.com/MichMich/MagicMirror/commit/e4197012f65778f815cd73a6c7fab1a30ef3b92f

Thanks!