Rebuilding the Nest plugin

For heating/cooling related questions in Domoticz
leecollings
Posts: 136
Joined: Tuesday 30 June 2015 18:09
Target OS: Raspberry Pi
Domoticz version:
Location: United Kingdom
Contact:

Re: Rebuilding the Nest plugin

Post by leecollings » Monday 26 March 2018 0:15

Ah I see. In all fairness, I don't see the difference in the 'AWAY' and 'ECO' switches in the current Nest plugin. They are the same thing aren't they?

Akerboom
Posts: 39
Joined: Thursday 15 March 2018 20:40
Target OS: -
Domoticz version:
Contact:

Re: Rebuilding the Nest plugin

Post by Akerboom » Monday 26 March 2018 21:29

This is what I was looking for, didn't know it was added to Domoticz recently. Good going!
I'm only getting 4 devices for my Thermostat, none for my Protects. Should I allow more than 5 minutes for new devices?

Also are you planning to support the Camera?
I'd love:
- Webcam support using the snapshot_url and refreshing
- Motion/Person/Sound/Zone detection

Cheers!

poudenes
Posts: 472
Joined: Wednesday 08 March 2017 10:42
Target OS: Linux
Domoticz version: 3.8993
Location: Amsterdam
Contact:

Re: Rebuilding the Nest plugin

Post by poudenes » Monday 26 March 2018 21:46

Does nobody have those errors: ?

Code: Select all

2018-03-05 10:17:34.832 Error: NestOAuthAPI: Error getting structures!
2018-03-05 10:18:06.090 Error: NestOAuthAPI: Error login!
2018-03-05 10:18:37.232 Error: NestOAuthAPI: Error login!
2018-03-05 10:19:08.390 Error: NestOAuthAPI: Error login!
2018-03-05 10:19:39.903 Error: NestOAuthAPI: Error login!
2018-03-05 10:20:11.783 Error: NestOAuthAPI: Error login!
2018-03-05 10:20:43.115 Error: NestOAuthAPI: Error login!
2018-03-05 10:21:47.672 Error: NestOAuthAPI: Error getting structures!
2018-03-05 10:22:18.915 Error: NestOAuthAPI: Error login!
2018-03-05 10:22:49.899 Error: NestOAuthAPI: Error login!
2018-03-05 10:23:24.597 Error: NestOAuthAPI: Error login!
2018-03-05 10:23:55.840 Error: NestOAuthAPI: Error login!
2018-03-05 10:24:27.029 Error: NestOAuthAPI: Error login!
2018-03-05 10:24:58.184 Error: NestOAuthAPI: Error login!
2018-03-05 10:25:29.463 Error: NestOAuthAPI: Error login!
2018-03-05 10:26:00.626 Error: NestOAuthAPI: Error login!
2018-03-05 10:26:31.214 Error: NestOAuthAPI: Error login!
2018-03-05 10:27:01.849 Error: NestOAuthAPI: Error login!
2018-03-05 10:27:33.006 Error: NestOAuthAPI: Error login!
2018-03-05 10:28:04.514 Error: NestOAuthAPI: Error login!
2018-03-05 10:28:35.651 Error: NestOAuthAPI: Error login!
2018-03-05 10:29:06.840 Error: NestOAuthAPI: Error login!
2018-03-05 10:32:23.035 Error: NestOAuthAPI: Error getting devices!
RPi3 with OSMC - RPi3 with Domoticz - Dashticz - MiLight - Nanolead Aurora - KaKu - Logitech Hamony - Nest - RFLink

Robbie
Posts: 35
Joined: Friday 04 September 2015 1:15
Target OS: NAS (Synology & others)
Domoticz version: 2.2980
Contact:

Re: Rebuilding the Nest plugin

Post by Robbie » Tuesday 27 March 2018 16:29

leecollings wrote:
Monday 26 March 2018 0:15
Ah I see. In all fairness, I don't see the difference in the 'AWAY' and 'ECO' switches in the current Nest plugin. They are the same thing aren't they?
AWAY will set the eco temp, but resumes the scheduled temps.
ECO sets the eco temperature, until ECO is deactivated (Ignoring any schedules).

So, if I leave my home for 2 days.. with AWAY activated, then in the evening my heating turns on according to the schedule.
In that case I need to override all scheduled temps with the manual ECO button.

Also, unfortunately I had to remove this plugin due the the errors mentioned by Poudenes (above).
Last edited by Robbie on Friday 30 March 2018 15:32, edited 1 time in total.

Akerboom
Posts: 39
Joined: Thursday 15 March 2018 20:40
Target OS: -
Domoticz version:
Contact:

Re: Rebuilding the Nest plugin

Post by Akerboom » Thursday 29 March 2018 22:01

Same here.
poudenes wrote:
Monday 26 March 2018 21:46
Does nobody have those errors: ?

Code: Select all

2018-03-05 10:17:34.832 Error: NestOAuthAPI: Error getting structures!
2018-03-05 10:18:06.090 Error: NestOAuthAPI: Error login!

Robbie
Posts: 35
Joined: Friday 04 September 2015 1:15
Target OS: NAS (Synology & others)
Domoticz version: 2.2980
Contact:

Re: Rebuilding the Nest plugin

Post by Robbie » Friday 30 March 2018 15:29

Akerboom wrote:
Thursday 29 March 2018 22:01
Same here.
poudenes wrote:
Monday 26 March 2018 21:46
Does nobody have those errors: ?

Code: Select all

2018-03-05 10:17:34.832 Error: NestOAuthAPI: Error getting structures!
2018-03-05 10:18:06.090 Error: NestOAuthAPI: Error login!
#MeToo

Clemen
Posts: 127
Joined: Saturday 05 December 2015 16:11
Target OS: Raspberry Pi
Domoticz version: Beta
Location: Europe
Contact:

Re: Rebuilding the Nest plugin

Post by Clemen » Sunday 01 April 2018 21:55

Robbie wrote:
Friday 30 March 2018 15:29
Akerboom wrote:
Thursday 29 March 2018 22:01
Same here.
poudenes wrote:
Monday 26 March 2018 21:46
Does nobody have those errors: ?

Code: Select all

2018-03-05 10:17:34.832 Error: NestOAuthAPI: Error getting structures!
2018-03-05 10:18:06.090 Error: NestOAuthAPI: Error login!
#MeToo

Same her

Code: Select all

2018-04-01 20:51:40.924 Error: NestOAuthAPI: Error getting devices!
2018-04-01 20:54:42.406 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:00:00.747 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:00:48.004 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:01:21.428 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:02:03.734 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:02:36.413 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:04:22.897 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:05:05.127 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:05:37.396 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:06:09.584 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:07:21.974 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:11:25.811 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:11:56.918 Error: NestOAuthAPI: Error login!
2018-04-01 21:12:29.180 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:13:12.089 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:13:43.176 Error: NestOAuthAPI: Error login!
2018-04-01 21:14:15.313 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:14:56.455 Error: NestOAuthAPI: Error login!
2018-04-01 21:16:00.913 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:16:41.972 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:18:58.855 Error: Nest: Error getting current state!
2018-04-01 21:18:59.652 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:19:01.372 Error: Netatmo: Error connecting to Server...
2018-04-01 21:20:47.596 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:22:02.614 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:24:21.997 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:25:36.510 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:26:49.722 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:27:20.840 Error: NestOAuthAPI: Error login!
2018-04-01 21:27:51.921 Error: NestOAuthAPI: Error login!
2018-04-01 21:29:05.673 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:32:38.077 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:39:13.685 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:40:27.768 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:43:18.703 Error: NestOAuthAPI: Error getting structures!
2018-04-01 21:45:45.832 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:47:06.280 Error: NestOAuthAPI: Error getting devices!
2018-04-01 21:47:37.341 Error: NestOAuthAPI: Error login!
2018-04-01 21:48:18.155 Error: NestOAuthAPI: Error login!
But it is working some time, first time ever i got a reading after a smoke alarm vent off. Never happened before the rebuilded plugin.
Screen Shot 2018-04-01 at 21.55.21.png
Screen Shot 2018-04-01 at 21.55.21.png (263.75 KiB) Viewed 823 times

dotms
Posts: 24
Joined: Monday 01 May 2017 22:52
Target OS: Linux
Domoticz version: git
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by dotms » Tuesday 03 April 2018 13:42

I'm currently testing it against Nests official simulator. This is a fake home with a thermostat, a camera and a protect. Maybe I'm testing the wrong way, but it all works fine here:

Code: Select all

2018-04-03 13:32:42.383  EventSystem: Queue thread started...
2018-04-03 13:32:48.492  NestOAuthAPI: Access token appears to be valid.
2018-04-03 13:32:50.445  (nestoauth) Thermostat (Demo House Living Room Setpoint)
2018-04-03 13:32:50.460  (nestoauth) Temp + Humidity (Demo House Living Room TempHum)
2018-04-03 13:33:22.444  (nestoauth) Thermostat (Demo House Living Room Setpoint)
2018-04-03 13:33:22.444  (nestoauth) Temp + Humidity (Demo House Living Room TempHum)
2018-04-03 13:33:31.061  Incoming connection from: ::1
2018-04-03 13:33:54.453  (nestoauth) Thermostat (Demo House Living Room Setpoint)
2018-04-03 13:33:54.469  (nestoauth) Temp + Humidity (Demo House Living Room TempHum)
2018-04-03 13:34:26.454  (nestoauth) Thermostat (Demo House Living Room Setpoint)
[...]
2018-04-03 13:37:38.421  (nestoauth) Temp + Humidity (Demo House Living Room TempHum)
2018-04-03 13:38:10.364  (nestoauth) Thermostat (Demo House Living Room Setpoint)
2018-04-03 13:38:10.376  (nestoauth) Temp + Humidity (Demo House Living Room TempHum)
Please note that I do not own a Nest Thermostat any more, so I'm dependent on these tools to develop this domoticz plugin. Camera support is not planned.

To those who have errors, can you please describe what your Nest environment looks like (how many homes, thermostats, protects and such). Please be as elaborate as possible since I can't reproduce these errors myself right now. That makes it kinda difficult to figure out what's wrong. If I can get the plugin to break it will most likely be an easy fix but until then it's just guessing.

For what it's worth: when I had it running on a recent Debian install (9 I guess) I wasn't able to make connections to the outside world, causing all kinds of weird errors. Back then I did a reinstall of an older Debian and everything worked just fine. Most of the errors that I see consist of a lot of errors not getting data at all. I'm not a Linux/Debian wizard so I don't know what was going on (apart from it breaking like mad).

This can be seen in the log of @Clemen for example:

Code: Select all

2018-04-01 21:11:56.918 Error: NestOAuthAPI: Error login!
[...]
2018-04-01 21:18:58.855 Error: Nest: Error getting current state!
[...]
2018-04-01 21:19:01.372 Error: Netatmo: Error connecting to Server...
It may just be that the NestOAuthAPI plugin is a little more verbose about what it's trying to do.

dotms
Posts: 24
Joined: Monday 01 May 2017 22:52
Target OS: Linux
Domoticz version: git
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by dotms » Tuesday 03 April 2018 18:42

I did some additional work, restructuring and troubleshooting. I'll be uploading the changed code to my github shortly, and will be doing a test compile on a Linux machine tonight. Please help me in testing this and pointing out if things break!

Things fixed
  • Away mode in case of multiple homes/structures. Probably worked fine with a single home, but it could have caused the wrong home to be set to away.
  • Manual eco mode implemented.
  • Improved logging of API interaction.
  • Quite a bit of small fixes.
In my case some of the things that did not work (like setting away) were caused by incorrect permission settings. As far as I can see the following permissions in the Nest developer portal are needed for current or future full access. Some are currently required, some may or may not be used in the future. I think it's best to enable them anyway, so you don't have to change them at a later point after you find out things don't work and you don't know why.

- Thermostat: Thermostat read/write (currently required), Energy read (possible future use)
- Camera: Camera + Images read/write (possible future use)
- Smoke+CO Alarm: Smoke+CO Alarm read (currently required)
- Security: Security State read (possible future use)
- Other permissions: Away read/write (currently required), ETA read (possible future use), ETA write (possible future use), Structure read/write (currently required), Postal code read (possible future use)

Akerboom
Posts: 39
Joined: Thursday 15 March 2018 20:40
Target OS: -
Domoticz version:
Contact:

Re: Rebuilding the Nest plugin

Post by Akerboom » Tuesday 03 April 2018 20:16

Do we need to compile Domoticz from your brache for testing?

dotms
Posts: 24
Joined: Monday 01 May 2017 22:52
Target OS: Linux
Domoticz version: git
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by dotms » Tuesday 03 April 2018 20:20

Yes. I don’t want to go through the trouble of putting in pull requests (and bothering gizmocuz) to the development domoticz repository while it’s still in feature testing (consider it alpha). It is synced up to the development branch though.

Akerboom
Posts: 39
Joined: Thursday 15 March 2018 20:40
Target OS: -
Domoticz version:
Contact:

Re: Rebuilding the Nest plugin

Post by Akerboom » Tuesday 03 April 2018 21:52

Not building for Arm 32bit (RaspberryPI) I suppose? :roll:

dotms
Posts: 24
Joined: Monday 01 May 2017 22:52
Target OS: Linux
Domoticz version: git
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by dotms » Tuesday 03 April 2018 21:58

That's what I'm currently doing. On my Windows desktop build is done in like 1-2 minutes, on my Raspberry it's more like half a day.

Akerboom
Posts: 39
Joined: Thursday 15 March 2018 20:40
Target OS: -
Domoticz version:
Contact:

Re: Rebuilding the Nest plugin

Post by Akerboom » Tuesday 03 April 2018 22:04

happy to test if you can share the binary :)

dotms
Posts: 24
Joined: Monday 01 May 2017 22:52
Target OS: Linux
Domoticz version: git
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by dotms » Wednesday 04 April 2018 2:16

Been doing some cross-compilation because compiling on a rpi is unbearably slow. Running into some compilation errors on Linux that I don't get when building on Windows, probably some non-portable code. Will look into it later. For now, compiling it via MS Visual Studio should work. Other platforms probably not.

edit: Can't get cross compilation to work for now. Ironed out some issues though. Should build on non-Windows now. Leaving the rpi to compile overnight.

edit 2: built successfully on a fresh Debian 9 amd64 install. I don't expect any problems Pi, but will not be putting time in testing on it since the thing is too painfully slow.

User avatar
tcviper
Posts: 169
Joined: Monday 30 June 2014 13:34
Target OS: Raspberry Pi
Domoticz version:
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by tcviper » Tuesday 10 April 2018 14:36

Is working very well so far with Thermostats and Smoke/CO Protect. However, will Camera/Hello support come also anytime soon? :)

dotms
Posts: 24
Joined: Monday 01 May 2017 22:52
Target OS: Linux
Domoticz version: git
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by dotms » Tuesday 10 April 2018 21:18

As mentioned earlier, camera support is not a priority for me right now for a number of reasons:

- I don't have a camera, never had one either
- I have no idea what its uses are and what useful information for these things would be
- My time is limited and I want the current plugin to be confirmed stable and integrated first before expanding it to new areas.

Never say never though :lol:

Akerboom
Posts: 39
Joined: Thursday 15 March 2018 20:40
Target OS: -
Domoticz version:
Contact:

Re: Rebuilding the Nest plugin

Post by Akerboom » Tuesday 10 April 2018 21:37

I'd like a switch in domoticz to activate when a 'person' is spotted in a specific 'zone' on my camera.
Then I can activate the light or broadcast the presence on my google home. In the nighttime I might want to sound the alarm.

When your code is in place, I'll be happy to have a look if I can create a PR to add camera support.

poudenes
Posts: 472
Joined: Wednesday 08 March 2017 10:42
Target OS: Linux
Domoticz version: 3.8993
Location: Amsterdam
Contact:

Re: Rebuilding the Nest plugin

Post by poudenes » Wednesday 13 June 2018 14:44

Hi All,

Tried in Beta version v3.9631 to use Nest OAuth method but after less then 12 hours i got still get the errors in log.
Is there someone rebuild this plugin or must we forget this method to link nest thermostat en smoke detectors in Domoticz?

Code: Select all

2018-06-13 13:41:38.059 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 13:41:38.060 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 13:42:12.145 Error: NestOAuthAPI: Error getting devices!
2018-06-13 13:50:35.000 Error: NestOAuthAPI: Error getting devices!
2018-06-13 14:30:37.548 Error: NestOAuthAPI: Error getting devices!
2018-06-13 14:31:08.907 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:31:08.908 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:31:30.680 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:31:31.684 Error: Restarting: Nest OAuth
2018-06-13 14:31:38.335 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:31:38.336 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:32:09.700 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:32:09.700 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:32:41.127 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:32:41.128 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:33:00.928 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:33:01.930 Error: Restarting: Nest OAuth
2018-06-13 14:33:08.485 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:33:08.485 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:33:39.914 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:33:39.914 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:34:11.279 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:34:11.280 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:34:30.150 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:34:31.154 Error: Restarting: Nest OAuth
2018-06-13 14:34:37.599 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:34:37.600 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:35:08.980 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:35:08.981 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:35:40.359 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:35:40.359 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:36:00.541 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:36:01.541 Error: Restarting: Nest OAuth
2018-06-13 14:36:08.783 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:36:08.783 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:36:40.100 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:36:40.101 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:37:11.583 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:37:11.583 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:37:30.384 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:37:31.386 Error: Restarting: Nest OAuth
2018-06-13 14:37:37.888 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:37:37.888 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:38:09.328 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:38:09.328 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:38:40.715 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:38:40.715 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:39:00.607 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:39:01.608 Error: Restarting: Nest OAuth
2018-06-13 14:39:08.080 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:39:08.080 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:39:39.511 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:39:39.511 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:40:10.952 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:40:10.952 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:40:30.853 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:40:31.853 Error: Restarting: Nest OAuth
2018-06-13 14:40:38.390 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:40:38.390 Error: NestOAuthAPI: Login failed: token did not validate.
2018-06-13 14:41:11.238 Error: NestOAuthAPI: Error getting structures!
2018-06-13 14:41:44.113 Error: NestOAuthAPI: Error getting structures!
2018-06-13 14:42:00.971 Error: Nest OAuth hardware (2) nothing received for more than 1 Minute!....
2018-06-13 14:42:01.972 Error: Restarting: Nest OAuth
2018-06-13 14:42:08.489 Error: NestOAuthAPI: Error while performing login: Got empty response body while getting structures. Response code: HTTP/1.1 307 Temporary Redirect
2018-06-13 14:42:08.490 Error: NestOAuthAPI: Login failed: token did not validate.
RPi3 with OSMC - RPi3 with Domoticz - Dashticz - MiLight - Nanolead Aurora - KaKu - Logitech Hamony - Nest - RFLink

dotms
Posts: 24
Joined: Monday 01 May 2017 22:52
Target OS: Linux
Domoticz version: git
Location: Netherlands
Contact:

Re: Rebuilding the Nest plugin

Post by dotms » Wednesday 13 June 2018 18:40

Nest throwing a 307 redirect either means:
  • There is some maintenance happening at their side. That should be transient and resolve itself.
  • You hit some rate limit. This can be fixed by polling less frequently.
The latter case which is something that needs to be changed in the plugin. Unfortunately for us Nest does not tell us the actual limits (except that you have crossed the limit) so it remains a guess what a good interval is.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest