Not any time soon. I’m coping with a family loss at the moment and haven’t touched anything in 3 weeks.

I have not.

I get that, mine does the same at night. Even turning off the output, the back light is still on. Turning off the HDMI would do the trick, except after a few seconds I get that ugly, bright blue, ‘NO SIGNAL’ box. Annoying, but at least it goes away after a while and the screen’s back light will shut off. AFAIK there is no way for the rpi to control screen brightness, at least none that I could find.

For those electrically inclined, one possible hardware solution is to tap into the brightness control within the monitor, and tie that to the rpi with a light sensor. It’s easier for those who buy their controllers off of eBay as those things are exposed and easy to get to, but on a sealed (box purchase) monitor, you’d have to tear it apart and probe for the signals that control the back light.

Perhaps an easier method might be to change the color of the elements to a lesser bright white, much like the current ‘dimmed’ style. While this does not change the light output of the screen, it will reduce the brightness of the actual text being displayed. Just a thought … I started playing with a light sensor not too long ago and it doesn’t take much to adjust the DOM based on the sensor’s output.

You’d have to talk to the moment.js folks (or figure out how to calculate the time difference yourself and pass it on to moment.js to parse for you). If you manually change the moment locales, it will get overwritten at the next update.

That’s strictly a moment.js thing … However, what we humans perceive as ‘in a day’ and ‘tomorrow’ aren’t actually the same thing.

moment.js calculates based on midnight. So, an event that happens before midnight tomorrow is considered to be tomorrow. An event that happens after midnight tomorrow, is considered ‘in a day’ because it counts starting AT midnight, and not from the current time. So current time TO midnight, plus 1 day = ‘in a day’. It’s not how we calculate time intuitively, but it’s how computers calculate time, and thus moment.js does that.

“There’s a camera behind the mirror. We will know if you don’t wash your hands.”

@alexyak … which can still be a module.

@ronny3050, please don’t cross-post your messages. Each category will reset and display at the top of the Recent page. Having the same thing posted multiple times will just become noise across all the categories.

Hopefully the community can help you out here as the Pi0 is not supported. Some people may have gotten it to work though …

@MichMich, encoding issues?

Do not install MagicMirror² as the root user. Bad idea. Root user should not be used for anything other than regular maintenance of the rpi itself, such as package and firmware updates.

Please delete that entire folder '$ rm -rf /root/MagicMirror/', log in as the regular pi user and run the MagicMirror² installation script from that account.

Running 'npm install ; npm start' also needs to happen from that pi user account, from with in the '/home/pi/MagicMirror' folder.

Not that I’m aware of. But then, @MichMich is always working on some aspect or another of the code, sometimes in complete secrecy, in a bunker deep underground and won’t tell us anything. He’ll just surprise all of us one day: “NEW RELEASE!”

As an FYI, you must have Xwindows and a window manager running for MagicMirror² to work. It uses Electron as a browser, which needs the graphical interface on the rpi to already be up and running. By itself, MagicMirror² does nothing with the OS. The end-user is responsible to make sure everything is setup properly and correctly.

The fact that you have to manually run 'startx' tells me you have the graphical environment installed, but you aren’t loading it automatically after the rpi boots up. You need to fix that. However you do it, that is outside the scope of MagicMirror.

Having played with this myself, one can run Jessie-light, however you need to then manually install all of the related packages to get the graphical environment up and running. You’re better off running the standard Jessie release and just cleaning off things that aren’t going to be used. That is extensively covered in the full tutorial I linked in my previous reply.

Have you tried following the tutorial? https://forum.magicmirror.builders/topic/236/complete-setup-tutorial

No need to use node helper for that. All modules can use 'moment.js' as it’s already in the code (for the time display, calendar, and various timers.) So write your code in the main module’s js file.

moment.now() gives you the current time.

Take a gander at my calendar_monthly module where I keep track of time for the refreshes. The calendar DOM only refreshes once a day, at midnight. However, because browsers tend to get “stuck” every so often during the day, I also keep track of the hours. What that means is, there is a “heartbeat” every hour to stay accurate to the actual time. If the browser got stuck and the clock delayed by a few seconds, the heartbeat will fix that every 60 minutes. Then, only when it reaches midnight, will it actually reload the DOM.

In the code, look at the 'start' function where I set the time till next midnight. Then I fire off a scheduleUpdate() which sets a delay to the next hour. When that timer expires, a couple of things happen:

1. it checks whether the current time is past the midnight set earlier. If so,

• it will reload the DOM (which refreshes the calendar display),
• it will calculate the next midnight
• it will reset the timer to the next hour
• it will loop back to scheduleUpdate()
  OR

2. if the current time is LESS than midnight,

• it will reset the timer to the next hour
• it will loop back to scheduleUpdate()
  … and the DOM never gets touched.

This way I don’t reload the calendar unnecessarily throughout the day. It only happens once, but the timer fires off every hour, just to keep track of time. If I didn’t do that, at least on my rpi, I noticed the browser’s time will drift by several minutes in a 24 hour period.

The calculations are correct for how a computer calculates it:

Birthday A : august 10 - shows today
Birthday B : august 11 - shows tomorrow
Birthday C : august 12 - shows in 1 day? Show display "in 2 days"
Birthday D : august 14 - shows in 3 days? Show display “in 4 days”

Calculations are done starting at the next midnight. So:

Birthday A : august 10 - shows today
    -- at the next midnight, it's day 0

Birthday B : august 11 - shows tomorrow
    -- at midnight, it will be day 0 + 1, so 'in 1 day' or 'tomorrow'

Birthday C : august 12 - shows in 1 day? Show display "in 2 days"
    -- at midnight, it will be day 0 + 2, so 'in 2 days'

Birthday D : august 14 - shows in 3 days? Show display “in 4 days”
    -- at midnight, it will be day 0 + 4, so 'in 4 days'

The way the calculations are done isn’t perfect, but it’s how Moment.js returns those values, based on midnight.

You can also set a timer in it that calls .hide() or .show() at set times during a 24 hour period. This is cleaner as you won’t know if the API will always return an empty array when there are no trains running.

There isn’t anything within MagiMirror that would do that. I don’t know that Electron does either to be honest with you, but I could be wrong. For screen captures, use 'scrot' from a command line on the rpi (don’t use VNC, use SSH to get on it and issue the command there):

$ scrot /home/pi/screenshot.png

You’ll end up with a PNG file of the whole screen.

You can search the forums for 'custom.css' and see how others are changing their styling. Each module uses a common set of styles, and by using targeted CSS rules, you can specifically set which module you want to change.