MMM-Nest-Status - New module for your Nest thermostats and protect smoke detectors!

[dazza120]

@michael5r cheers but its not that everything else is solid you know where you have the smoke co2 and temp for the themostat on the right i just need that whole thing pulling a little to the left towards the names of the devices, im failing at explaining myself lol

[michael5r]

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

@michael5r cheers but its not that everything else is solid you know where you have the smoke co2 and temp for the themostat on the right i just need that whole thing pulling a little to the left towards the names of the devices, im failing at explaining myself lol

I think you’re talking about about the width of the battery, co2 and smoke cells, right?

Try setting them to this:

.mmm-nest-status .nest-list th,
.mmm-nest-status .nest-list td {
    width: auto;
}

[dazza120]

@michael5r Hi yeah thats what i mean but that has shifted it further to the right and only the Nest protect battery stuff i need to move it in the opposite direction finally figure how to take a screen capture lol here is what i mean hue status lower right, the more bulbs you have the worse it will get as it moves up when bulbs are turned on! PS speeds aren’t this slow changed the config file for the speed test and it knocked of a zero so it was a 4 second test lol 0_1544518147439_2018-12-11-084242_1824x984_scrot.png

[michael5r]

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

@michael5r Hi yeah thats what i mean but that has shifted it further to the right and only the Nest protect battery stuff i need to move it in the opposite direction finally figure how to take a screen capture lol here is what i mean hue status lower right, the more bulbs you have the worse it will get as it moves up when bulbs are turned on! PS speeds aren’t this slow changed the config file for the speed test and it knocked of a zero so it was a 4 second test lol 0_1544518147439_2018-12-11-084242_1824x984_scrot.png

It looks like the module is in the middle_center or bottom_bar position, though - which is why it it takes up the entire width of the page. Shouldn’t it be using bottom_left?

[dazza120]

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

bottom_left

Yes you the man, i swear i did that and the MM just showed me a black screen changed it back to default and it worked. But that was it it looks good i might have to bring some modules back well at least compliments lol

[max64]

Love the module. (and I tried them all)

2 humble requests:

1. Any way to add a transparency setting to the entire graphic so that an underlying background pic can partially show through? (Can that be done via custom.css?)

2. Can you add a “initial polling delay” config option? (similar to what is in the weather forecast module). My use case is a vertical monitor where I have two instances of the module loaded. One in top-right (Upstairs) and one in bottom right (Downstairs). Nest recommends polling of not more than once per minute with separate device per hour and token limits. I set up each instance of the module to use a different token, but as you can only set the ‘updateInterval’ it’s a challenge to get the two modules to stagger the calls. (And I think this is why i was getting “null” response displayed after a while… )

1 observation: when using the “alignment” option, both text and graphics are justified according to the setting. This is OK for “center” and even looks OK for “left”, but it does look odd for “right” where the thermostat graphic itself is flush right of the allocated space (e.g., top-right), but the title text is also right justified (.e.g., Upstairs) and not aligned with the graphic itself. IMHO the text above and below the graphic would look best centered with the graphic, and then the whole block is “aligned” according to the setting chosen.

Again…great work.

[michael5r]

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

Love the module. (and I tried them all)

2 humble requests:

1. Any way to add a transparency setting to the entire graphic so that an underlying background pic can partially show through? (Can that be done via custom.css?)

2. Can you add a “initial polling delay” config option? (similar to what is in the weather forecast module). My use case is a vertical monitor where I have two instances of the module loaded. One in top-right (Upstairs) and one in bottom right (Downstairs). Nest recommends polling of not more than once per minute with separate device per hour and token limits. I set up each instance of the module to use a different token, but as you can only set the ‘updateInterval’ it’s a challenge to get the two modules to stagger the calls. (And I think this is why i was getting “null” response displayed after a while… )

1 observation: when using the “alignment” option, both text and graphics are justified according to the setting. This is OK for “center” and even looks OK for “left”, but it does look odd for “right” where the thermostat graphic itself is flush right of the allocated space (e.g., top-right), but the title text is also right justified (.e.g., Upstairs) and not aligned with the graphic itself. IMHO the text above and below the graphic would look best centered with the graphic, and then the whole block is “aligned” according to the setting chosen.

Again…great work.

1. Certainly - add this to your custom.css file and the dial becomes transparent:

.mmm-nest-status .thermostat .circle {
    background: transparent !important;
}

.mmm-nest-status .thermostat .dial-classic .dial-circle {
    fill: transparent !important;
}

The !important means that this will also apply when the thermostat is heating or cooling (eg. it will no longer have the blue or orange background). If you only wish for the grey version of the dial to be transparent, remove the !important.

If you’re using the classic mode of the thermostat, setting the styles above means you get a nice colored glow when the thermostat is heating or cooling:

2. It’s already there - for some reason I just forgot to add it to the documentation. Just add initialLoadDelay with whatever value you want to your configuration. The value is in ms, so if you want a 1 minute delay, set the value to be 60000.

3. In regards to your observation - that’s a legit bug, thanks for spotting it! The alignment setting should only apply to the graphic itself, not the text inside it. I have pushed an update that fixes it, so if you pull the latest version of the module from github, it should be fixed.

It’s an interesting usecase you have - I hadn’t even thought about using 2 instances of the module to have separate thermostats displayed on the screen in separate locations.

The reason you’re getting the null response is because of this:
https://developers.nest.com/guides/api/data-rate-limits

(I’ve updated the module to display a more helpful error message when that happens.)

Anyway … it’s not a good idea to make 2 separate calls to the Nest API to get the data (that gives you even more of a chance to get that null error), so check out the latest version (1.3.0) I just pushed - if you use the same token in both module instances, they’ll only do 1 call to the Nest API and use the sockets to update both thermostats at the same time :thumbs_up:

Thanks for the comments!

[michael5r]

Btw, for those of you with Nest cameras as well, I’ve just published a new module called mmm-nest-cameras which shows your camera streams on the mirror as well.

When both of my Nest modules are installed on the same mirror and you use the same Nest token for both, they’ll share data streams to avoid unnecessarily pinging the Nest API.

Check it out here:
[card:michael5r/mmm-nest-cameras]

[max64]

@michael5r

The right alignment text is perfectly centered over the dial. And the transparent background looks very very good.

Switched the token to the same for both modules and set the updateInterval to 1.5 minutes on both also. No null yet… Using your socket method there’s really no reason to use initialLoadDelay to stagger the API calls.

Many thanks.

[max64]

@michael5r

Is Nest Lock status next on your agenda?