Posts made by michael5r

michael5r

@michael5r - Actually, I don’t get scrollbars at all. If I don’t subtract back from the 100vh/100vw or 100% - It’ll just run off the edge of the screen as if the system is seeing the screen (In this case, the RasPi’s 7" touchscreen) bigger than it is. With it set the way I have it, everything is dead on edge, giving the maximum use of the screen.

I’m glad it works for you, but it still doesn’t make any sense :)

michael5r

@spitzlbergerj Super nice build!

If you don’t mind, a couple of questions:

Seeing that you screwed the Dibond panel into the wood frame, did you cover up the screw holes afterwards or are they just not visible through the glass?
I didn’t see any brackets or bracing in the photos, so how are you actually holding the monitor in place?

Thanks!

michael5r

@bkeyport said in Is there a way . . .:

@sdetweil so, then because I have to use the following:
body {
margin: 0px;
height: calc(100vh - 10px);
width: calc(100vw - 5px);
}
am I correct in assuming that magicmirror sees the screen a few pixels bigger than it really is - and that’s being expressed by running off the right and bottom of the screen when I don’t have the 10px subtract from height, and the 5px subtract from width?

No - the screen is the size it is.

Your CSS above doesn’t make sense (you’re setting a body height that’s 10px smaller than the window height). If you set the body height to be 100vh and you get a vertical scrollbar, it’s because of another margin that’s pushing the body element.

In general, it’s good practice to also do:

html {
    margin: 0;
    padding: 0;
}

to avoid situations like this.

michael5r

@dazza120 That seems odd - let me check it out & see if I can replicate.

michael5r

Hi,

Just released a new, small module called mmm-energy-saver.

This module works in conjunction with MMM-Pir-Sensor to automatically suspend & resume all your modules based on movement detection. Furthermore, this module allows you to specify times when all the modules are suspended and your HDMI-connected screen is turned off as well.

Please note that the movement detection will not work unless you have the MMM-Pir-Sensor module installed (and working).

By design, this module has fairly limited functionality - which is nice because it makes it very easy to set up & use. If you, however, want a lot more control over the individual modules including setting specific timers based on days or showing alerts, I’d recommend checking out the MMM-ModuleScheduler module instead.

Anyway, check out the new module here:
[card:michael5r/mmm-energy-saver]

michael5r

@eawalker1 said in MMM-Nest-Status - New module for your Nest thermostats and protect smoke detectors!:

@michael5r Nope, that did the trick. Thanks.

Great :thumbs_up:

michael5r

@eawalker1 If your token is 8 characters long, it’s not the correct Nest token. It should be a long-ass string that usually begins with c. I think you’re confusing the token with the PIN you get from Nest.

Did you run the getToken.sh bash script in the module? It has multiple steps - you start by entering the client id and client secret which then generates a URL you need to open in a browser to get a PIN.

You then enter the PIN in the bash script and on the next screen, it should display your actual token.

michael5r

Just wanted to announce that there’s a new version out of both my Nest modules!

I added functionality to support Paviro’s MMM-PIR-Sensor module meaning that the modules can now be suspended & resumed based on movement detected through a PIR sensor (or whatever else you’re using for motion detection).

Check out the release notes here:
https://github.com/michael5r/mmm-nest-status/releases/tag/1.4.0

And for mmm-nest-cameras:
https://github.com/michael5r/mmm-nest-cameras/releases/tag/1.1.0

michael5r

Just wanted to announce that there’s a new version of this module out!

I added functionality to support Paviro’s MMM-PIR-Sensor module meaning that this module can now be suspended & resumed based on movement detected through a PIR sensor (or whatever else you’re using for motion detection).

Check out the release notes here:
https://github.com/michael5r/mmm-hue-lights/releases/tag/1.3.0

michael5r

@sebi76 Your syntax is wrong - you have this:

const DISABLED = {};
   
    DISABLED.clock = false;

},

It should just be this:

const DISABLED = {};
DISABLED.clock = false;

It’s that last }, that’s breaking your code.