Nest Thermostat/Protect OAuth - NestOAuthAPI problem while changing router to Unifi

Topics (not sure which fora)
when not sure where to post, post here and mods will move it to right forum.

Moderators: leecollings, remb0

Post Reply
User avatar
dre68
Posts: 27
Joined: Friday 30 January 2015 20:18
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Noordwijk, Netherlands
Contact:

Nest Thermostat/Protect OAuth - NestOAuthAPI problem while changing router to Unifi

Post by dre68 »

I changed my (Telfort glasvezel) Experiabox V8 router to an Unifi USG router to complete my Unifi eco system. Since that moment I am getting NestOAuthAPI errors and the thermostat is not working anymore (in Domoticz).

NestOAuthAPI: Login failed: token did not validate.
NestOAuthAPI: Error while performing login: Got empty response body while getting structures.

Is there someting specific I have to set up in the USG router to facilitate the nest api to communicate outside the LAN?

If I put back my old Experiabox as router, the Nest Thermostat/Protect OAuth hardware item starts working properly again

Any ideas what could be the culprit?
User avatar
dre68
Posts: 27
Joined: Friday 30 January 2015 20:18
Target OS: Raspberry Pi / ODroid
Domoticz version: latest
Location: Noordwijk, Netherlands
Contact:

Re: Nest Thermostat/Protect OAuth - NestOAuthAPI problem while changing router to Unifi

Post by dre68 »

For those who concern, I have found the solution to this issue myself (for Nest thermostat with Nest account).
It seems that the Ubiquity USG router has a tighter firewall than the Experiabox V8 my ISP provided.
You have to forward port 9553 to the Domoticz IP adress, this to let Domoticz transmit and receive data to and from the Nest API server.

Everything is working fine now.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest