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

[nhl]

@costascontis Make sure the away read permission is active on your nest development OAuth client

[costascontis]

@nhl in my Other Permissions Away read is greyed out.

[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?

[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 ?