@hermpi Curious. I dropped those changes into my mirror and it didn’t resolve the problem at all. Hrm.

@erik72 said in Problems with weather modules on new install:

EADDRINUSE

This usually means that you already have the mirror process running and attempted to start it again.

@dhirajv12 Let’s double-check some things. Please enter the following.

cd ~/MagicMirror
rm -rf modules/aiclient
git pull
npm install
cp config/config.js.sample config/config.js
npm start

With luck, that should at the very least get you a basic interface with the calendar, clock, compliments and newsfeed.

@dhirajv12 said in Black Screen after Launching application.:

In the terminal it says
No helper found for module: clock
no helper found for module: complements

This is normal. The system is checking for a node_helper.js file for every module. Those modules do not have one, so it is reported as such during the startup process.

@tidus5 The OpenGL drivers are experimental. I think we’re pushing the Pi - even the RPi3 - to its absolute limit with this type of rendering. A stable power supply isn’t the issue. It’s an issue of raw computing power.

@pieterbeulens I’m kind of swamped at the moment, so I can’t look at it for a couple weeks. My suggestion for right now is to create a test calendar and populate it with discreet events. Nothing that overlaps days, nothing that is an all-day event. See if you can’t connect and display it normally.

Once you’ve confirmed that it works, add a multi-day event and see if it breaks. Let’s isolate the exact problem and then we have a test case we can use for fixes.

Well, this sucks. I tried to enable the GL drivers on my Raspberry Pi 3 and it crashed the Pi. It installed the drivers, asked me to reboot and then the Pi won’t come back up. I’m going to have to reflash the card and start over.

It’s going to be a long night. If you’re going to try the GL drivers, back up your config.js at the very least. Better yet, image your SD card just in case.

I saw the updates this morning at the office and updated. Looks great! Thanks for the work.

@vindoan Quick basic questions: Do you have a working internet connection to your Raspberry? Can you start the desktop and use the embedded browser to surf to any particular website?

Is the weather coming up for your mirror correctly?

@pepemujica I believe the MMM-MotionDetection module works with the Pi camera. Facial recognition and gesture control should also work with the Pi camera. You may need to flip a few switches.

@d3r Well, there goes that theory.
At this point, all I can think of is a permissions problem. What does ls -lh ~/MagicMirror/config get you?

@d3r That’s really curious. Because I do not have that problem with node serveronly.

node serveronly
Starting MagicMirror: v2.1.1
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: updatenotification
No helper found for module: clock.
No helper found for module: MMM-Globe.
All module helpers loaded.
Starting server on port 8080 ... 
Starting server op port 8080 ... 
Server started ...
Connecting socket for: updatenotification
Sockets connected & modules started ...

Ready to go! Please point your browser to: http://localhost:8080

It looks like you are running two different mirrors on that box. The list of modules loaded in each case is different. I think you’re logged in as different users, so the ~ folder is going to point to different spots.

What do you get in return when you run ls -lh /home/?

@RE_Magic_Mirror I don’t think there is a problem, no. I haven’t done any research on the topic, but I believe the lightdm.conf file was deprecated around the time the Wheezy version of the Raspian operating system was released. At least… changes to that file on Wheezy didn’t seem to have the desired effect. That continued on Jessie.

@d3r This whitelist configuration is a bit dependent upon your network. If you have a router that assigns a different IP address, then this won’t work. For example, my Netgear Nighthawk router assigns IP addresses in the 10.0.0.X range, which are not covered by this whitelist. You’ll need to add values that represent your specific network. Otherwise, you can use [ ] to allow everyone to see your mirror interface.

In windows, open up a command prompt by clicking on the Start Button and then typing cmd in the search bar. Click on the first result and you’ll get a command prompt. Enter ipconfig and it will respond with your IP address. Take that IP address and add it to your whitelist value in your config.js. If you want to authorize every machine on your network, replace the final value in that ip address with 0 and add “/24”. In my case, it’s 10.0.0.0/24. In most other networks, it will be 192.168.0.0/24. That should allow any device on your local network the ability to view the Mirror by browsing to its IP address.

If you’re using Ubuntu or some other flavor of UNIX, ctrl+alt+t will get you a command prompt. The command in UNIX is ifconfig, not ipconfig. Don’t ask, because I don’t know why.

@RE_Magic_Mirror The best way to keep your mirror running is to install a screensaver and then configure the screensaver to never run. Yeah, it’s a bit weird.

Install the screensaver program: sudo apt-get install xscreensaver

Once you do, start your Pi and get to the desktop. If you have already configured your Pi to start the Magic Mirror interface, click ctrl+q to exit. Open the menu by clicking on the Raspberry start button with your mouse, or clicking the special/window key on your keyboard. Go to Preferences and there should be a new entry called “Screen Saver”. Click/Press enter to activate the screen saver configuration.

On the configuration screen, there is a drop-down box with options as to which screen saver you wish to run. I believe the default is “random screensaver”. Navigate to this drop down box and select “disable screensaver”. Close the screen saver configurations window.

That’s it. That should keep your Pi from going black.

@pieterbeulens Can you check each calendar to see if they have different types of events in them? There may be an issue between all day events and normal start/end events. Or possibly events that span multiple days.

My initial guess is that an event that spans multiple days does not have time associated with it. That may be throwing the module off.

@RE_Magic_Mirror That’s a bit more specific than we usually consider around here.

That 2nd variable, the transmittance visible, is usually about all we consider. I just bought a mirror that was also 11% transparent and it works great. It is maybe a little dim in a brightly lit reception area, but I’m certainly not going to send it back.

At most, you might want to go up to 20% transmittance, but I would use that only in areas that are in bright sunlight. For your typical household / interior mirror, I think you’re good to go with that mirror.

@BlackTalon Interesting. Thanks for figuring out the issue.

Question: I could load this on the Raspberry Pi 3 at the office and then take a video of the end result. Would that be interesting to the community? Or should we just call this a greater-than-raspberry module?

@BlackTalon I don’t think so, no. I’m running this on either my development PC, my work desktop or a microPC. Win10 or Ubuntu 16, respectively.

It looks like the electron browser thingy doesn’t support some of the commands used by the module. Possibly. We may need a workaround. Still investigating.

@cowboysdude I looked into it briefly. I had a prototype going using plantary.js, but it was a complete processor hog. I was afraid to even try it on a Pi.

IIRC, there were three of us looking into it, two of us had prototypes. And then @Eunanibus comes along and solves it for us all. Well done.

You know what? Even better:
https://youtu.be/6KSCDIaIgdA