You might want to read the README on the module:
https://github.com/MichMich/MagicMirror/tree/master/modules/default/currentweather

Basically, you need to go get your own API key for that to work.

The only reason I ask is because you can do one of three things here:

• pick the best reflective mirror and just deal with the lesser light shining through, or
• use the lighter one and when you want to use it as a mirror, you can either:
  a) turn off all the modules, but the TV remains on, or
  b) turn off the TV all together

Using the lighter one is contingent on how well it reflects when there’s nothing being displayed or the TV is completely turned off. But if it reflects better, then that may be the way to go.

I realize the last option may be somewhat annoying but it would work. And turning off the modules is a piece of cake. Or you could even turn off the HDMI output on the rpi, but the TV remains on … although some (most?) TV will then also turn off the screen’s backlight if they don’t detect an HDMI signal. Mine does. It stays on for a few seconds then the backlight turns off. The TV is still on, but the screen is off completely.

There shouldn’t be any reason to edit 'defaultmodules.js', that’s only specific to the default modules that MM comes with. Any modules that you install does not go in the default folder, but simply in MagicMirror/modules/<module_name> …

@MichMich, unfortunately I can’t reproduce that. I’m using my own private Google calendar and it loads just fine.

The config.js file lives inside of the MagicMirror folder. Look in ~MagicMirror/config/ for a file named 'config.js.sample' and rename that to 'config.js'. Load up your mirror. Once that’s working, you can start customizing it.

Yeah, I definitely like the lighter one better (specially with the TV completely off!), but you need to decide on the reflective property. If it doesn’t suit you (you can’t quite see the mustache hair), then you’ll have to figure something else out.

For debugging purposes, I sprinkle 'Log.log("...")' statements in my code which I can then see in the console log. For example, in my calendar_monthly module, I have a 'debugging'flag that I can set which then outputs this bit in the console log:

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
CALENDAR_MONTHLY IS IN DEBUG MODE!
Remove 'debugging' option from config/config.js to disable.
             Current moment(): 1466399977889 (11:19:37 pm)
scheduleUpdate() delay set at: 1466402400000
  nextReload should happen at: 1466402400000 (12:00:00 am)
                  which is in: 40 minutes and 22 seconds.
              midnight set at: 1466402400000 (12:00:00 am)
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

That output helped a great deal when I needed to accurately calculate those values (and I couldn’t figure out why the delay I was setting wasn’t right.)

Having log notifications like that helps. I tend to put them in places where I need to check for a value, or verify that a condition is being met, before the rest of the code continues on. It’s worth nothing that I load the running mirror remotely on my development desktop machine (through Chrome or Firefox) by going to my rpi’s IP and MM’s port. I don’t touch the actual running task on the rpi itself, once loaded, I leave it alone. When I make a change in the code, I can refresh my browser and see the results immediately without affecting the mirror itself. It’s not till I’m certain the code works that I will restart the npm process on the mirror. This has the added advantage that I can see the current running code on the mirror and compare it with what the new/changed code shows on my remote browser.

As for the height/width part, those are being set in the main CSS file. Because it’s a fluid layout, there is no exact numbers, it’s all calculated at run-time based on the monitor’s resolution. So you’ll have to use the main layout “box” for the position that your module will be in, and then work within that. Setting fixed sizes will cause problems later down the road with folks who don’t have the same resolution as you.

Yeah, I saw that too when using Edge. I need to spent some time looking into that, but I’m also working on other code … one thing at a time. :)

That’s been in the 'develop' branch. Not pushed to 'master' yet. With this being a “biggie” for everyone who’s running the master branch, perhaps @MichMich might consider pushing it to the master branch sooner rather than later.

And my apologies earlier for not having spotted it. I always run the develop branch. #livingontheedge :)

What you see there are laser cut wood pieces. The connectors and light cups are done on an Ultimaker 2.

For me the whole thing is integration. How to get devices integrated into the current ecology without needing additional ‘anything’ to be added. So I didn’t have to install npm nor electron on my work station, I already had all the necessary tools. And why work on separate copies of the software in different locations, that causes confusion later. I keep it all in one location, and use it from there.

And with the addition of Git, even if I horribly break something, I can always revert the code to an earlier state simply by going to Git and checking out an earlier commit state. Instant backup and revision control.

My setup at the office is similar, except instead of the rpi, I have it running as a serveronly on one of my large servers (replace the Raspberry Pi for a server in the layout above). But that’s really the only difference. Everything else is the same.

Got a reply on there at least. I don’t want the user to think we’re ignoring it.

Sometimes it’s the simple things that are the most frustrating. I get calls, almost daily, from coworkers who can’t log in … I ask, ‘is your CAPS key on’ … you can guess the response.

My only guess here is that there wasn’t enough ventilation along the back side. Those backlit LEDs do get hot, and having it flush up against something, specially something that doesn’t conduct heat well, will cause them to overheat. Always leave some breathing space behind the panel, and as others suggested, a quiet fan to help move air doesn’t hurt.

macOS is the edge case. :)

Hey @acdacd2, please use proper Markdown when posting code. It really isn’t that hard to do and it makes it so much easier and pleasant for others to read, and possibly find errors quicker. Specifically you need to use back ticks before and after your code:

     ```
     like so. Note that a back tick is not the same as the normal apostrophe, ` versus ' .
     ```

As he said, there is no mechanism to do that. However, using the carousel module, you can trigger all of the current modules to turn off and a different set to be displayed, effectively giving you a ‘2nd page’.

If you are talking about having something totally different, non-MagicMirror, on a ‘2nd page’, there is no way to do that.

@cowboysdude, evil, just pure evil.

Unsuspecting friend visits, friend goes to bathroom, you whip out phone and “text” the mirror … friend comes running out screaming.

@Phate said in Its may a problem with node_helper:

Are you a miner also?

I used to be … but there’s no competing with China (yes, the country), the biggest miner in the world.

@shavesophere said in npm start dev:

@KirAsh4 sorry - i stand corrected! but that being said when i first started getting npm ERRS i tried this and it still did not work… anyway, moving forward now!

Well yeah, that’s different. If npm is giving you errors, no matter how you attempt to start it, the errors won’t magically go away. That’s like saying, the car won’t start if I’m sitting on the left side, maybe if I sit on the right side it might, but in reality there’s no gas in it. Switching seats isn’t going to fill the gas tank. :)