For anyone that wonders across this, this ended up happening because I was using one of the family acconts for my nest developer account. Nest doesn’t consider this as having a device associated to it. Problem was solved by creating a developer account with the ‘main’ account.
Read the statement by Michael Teeuw here.
Posts
-
RE: MMM-NEST
-
RE: MMM-NEST
No luck I’m afraid.
And to not really help matters, the console continues to state the same things, and the mm-error-0.log file is empty.
I opened this a few times just to make sure I wasn’t typing something wrong.
Then I redid the git pull, just because I figured maybe that was the problem. But shows up to date now.
-
RE: MMM-NEST
Awesome, that I can do.
Here’s what I see in Console that stands out.
MMM-Nest.js:120 Uncaught TypeError: Cannot convert undefined or null to object
processTemp @ MMM-Nest.js:120
nestRequest.onreadystatechange @ MMM-Nest.js:108Digging a little further, console sems to think there’s an issue with MMM-Nest.js on line 120:
var keyVar = Object.keys(data.thermostats);and line 108
self.processTemp(JSON.parse(this.response)); -
RE: MMM-NEST
I’m trying to figure out how to look at the console logs. (Googling console logs and linux)
Just 1 nest, controlling ac and heat, pretty simple setup.
-
MMM-NEST
Anyone have luck getting this module going? It’s pretty straight forward, nice script that walks you through all steps (reminds me of VMWare tools). The module looks to be installed, but my mirror only ever shows “Loading” and no nest data.