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

eawalker1

This is my first module I am attempting to install, and keep getting a Nest API Error:null. Total noob here, but I have registered as a developer, obtained Nest token/pincode, and believe I input code correctly into config.js file per below.

module: "mmm-nest-status",
position: "top_right",
config: {
    token: "my8characterpinfromnest",
    displayType: "grid",
    displayMode: "all",
    thermostatsToShow: "all",

Any ideas how to resolve the API issue?

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.

eawalker1

@michael5r Nope, that did the trick. Thanks.

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:

costascontis

thnx for your hard work ,i really like this module,but its not updating right.When i restart MM works fine for few hours and then stops updating.My token is working fine ,i use it also to my Openhab setup .Also my other modules are all updating fine.My config is :

{
                       module: "mmm-nest-status",
                       position: "top_center", // pick whichever position you want
                       config: {
                               token: "c.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
                               displayType: "grid",
                               displayMode: "all",
                               thermostatsToShow: "all",
                               updateInterval: "60000",
                               showNames: true,
                               thermostatSize: "medium",
                               // ... and whatever else configuration options you want to use
                               }

michael5r

@costascontis You configuration looks fine - the updateInterval is set to 60000, so it’s only pulling data every 10 minutes.

What exactly do you mean that it “stops updating”?

costascontis

isnt updateinterval in ms?cause if it is then 60000 ms = 1min…

michael5r

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

isnt updateinterval in ms?cause if it is then 60000 ms = 1min…

My bad - you’re right, it’s 1 minute :)

nhl

@costascontis Make sure the away read permission is active on your nest development OAuth client
0_1550527074655_f39cdd41-e38c-4ee8-9d82-29b37f2a78bf-image.png

costascontis

@nhl in my Other Permissions Away read is greyed out.
0_1550599997962_Screenshot (10).png

michael5r

@costascontis It shouldn’t matter - I don’t use the Away read setting in this module. The settings that matter are the ones directly tied to the thermostat and smoke detectors.

costascontis

@michael5r my Thermostat read is greyed out too …is that matter?
0_1550600653289_Screenshot (12).png

michael5r

@costascontis No, that’s fine - directly below you’ve enabled read/write, so that supersedes the standalone read setting.

costascontis

found some time to debug why module stops updating.I think it has something to do with my on/off monitor function.I use Motion to turn on my mm tv when movement detected by sending a “/opt/vc/bin/tvservice -p ; sudo chvt 6 ; sudo chvt 7” command.After 5 min with no motion detected it power off my tv sending a “on_event_end /opt/vc/bin/tvservice -p”.I think that after some time of power off monitor the module’s update function breaks.All other modules i use they work and updating fine all the time.

EDIT: ignore all of the above,even when my screen is on the module stops updating after a few hours…I dont know what else to try…maybe some other module causing this?Is it possible?

EDIT 2: I opened the console at the developers tools inside mm and i notished that from the moment MMM-NEST-STATUS module starts spams with notifications clock and calendar modules like that

clock received a module notification: MMM_NEST_STATUS_UPDATE from sender: mmm-nest-status
calendar received a module notification: MMM_NEST_STATUS_UPDATE from sender: mmm-nest-status

until it stops and stop updating the nest status also.Is that normal?

costascontis

@michael5r after hours of tests i found out that if i use default clock and calendar module then after a few minutes nest module stop updating.If i dont use clock/calendar and comment them at config.js then nest module is working fine for days.I am not a developer but i suspect that has something to do with notifications between these modules…

michael5r

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

EDIT 2: I opened the console at the developers tools inside mm and i notished that from the moment MMM-NEST-STATUS module starts spams with notifications clock and calendar modules like that
clock received a module notification: MMM_NEST_STATUS_UPDATE from sender: mmm-nest-status
calendar received a module notification: MMM_NEST_STATUS_UPDATE from sender: mmm-nest-status
until it stops and stop updating the nest status also.Is that normal?

Yes, that’s totally normal. The mmm-nest-status module is broadcasting a notification to all modules saying that data is available - it’s how the socket notification system works.

michael5r

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

@michael5r after hours of tests i found out that if i use default clock and calendar module then after a few minutes nest module stop updating.If i dont use clock/calendar and comment them at config.js then nest module is working fine for days.I am not a developer but i suspect that has something to do with notifications between these modules…

I’ll see if I can recreate this with those modules - thanks for the doing the debugging!

costascontis

@michael5r just asking…why nest-status need to send notifications to other modules ?

michael5r

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

@michael5r just asking…why nest-status need to send notifications to other modules ?

mmm-nest-status isn’t sending a notification directly to other modules, it’s sending a global notification.

But seeing that all modules listen for these notifications, the notification will also reach modules that don’t need or use it (which is where the console log you showed comes from - it’s basically all modules saying “I received a socket notification”, but it doesn’t mean they actually do anything with it).

That’s just how the magic mirror socket system works - every module that broadcasts data or status does this.

numb3rs

With the sell of Nest to Google, is this module still working at all?