[680] Nest Fieldtest support

Use this forum to discuss possible implementation of a new feature before opening a ticket.
A developer shall edit the topic title with "[xxx]" where xxx is the id of the accompanying tracker id.
Duplicate posts about the same id. +1 posts are not allowed.

Moderators: leecollings, remb0

Post Reply
puttemanp
Posts: 5
Joined: Thursday 15 October 2015 13:24
Target OS: NAS (Synology & others)
Domoticz version:
Location: Tremelo, Belgium
Contact:

[680] Nest Fieldtest support

Post by puttemanp »

Good morning,

I know I'm not the only Nest field tester on this board and using Domoticz.
Currently, Nest support is using the 'official' Nest web interface http://home.nest.com
Nest Field testers use another website http://home.ft.nest.com

While I'm not allowed to discuss functionality, I can tell that the basics of the Nest official interface and the field test interface are identical.
I recompiled Domoticz on a Raspberry, changing the pointer in Nest.cpp to http://home.ft.nest.com and Nest support for us fieldtesters works perfectly (Thermostat and smoke detectors).

Would it be possible to add a second Nest hardware in Domoticz, called Nest Beta or Nest Fieldtest with only the above mentioned modification?
Recompiling at every update risks breaking the entire setup, and web update would break Nest Fieldtest compatibility at every update.

P.
joostvanderlinde
Posts: 44
Joined: Tuesday 23 June 2015 23:06
Target OS: Linux
Domoticz version: 2023.2
Location: NL + SE
Contact:

Re: [680] Nest Fieldtest support

Post by joostvanderlinde »

Any chance of getting the Nest base-url parametrized in Domoticz?
Domoticz on BPI-M2-Pro (compiled on Ubuntu 22.04) and RPI (binary on Raspian 10)
RFXCom, Sonoff Zigbee stick, eBusd Adapter 5, P1, S0, Husdata H60 integration
Zigbee2MQTT AD, MQTT local, AirconWithMe, Ebusd, VolvoRecharge, PSA Car Controller
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests