Page 1 of 2

Thermostat API has evolved and now supports Valves

Posted: 05 Mar 2018, 15:43
by Céline
Hello everybody,

We're happy to announce the evolution of the Thermostat API which now supports the Valves.
https://dev.netatmo.com/resources/techn ... nce/energy

With Smart Valves and to allow for room-by-room heating control we are introducing the notion of Home into our API.
Users with Thermostats and/or Smart Valves now have at least one Home. A Home contains Rooms, Modules and room-by-room heating Schedules.

The following endpoints are being introduced :

HomesData to retrieve user's homes and their topology
HomeStatus to get the current status and data measured
Setthermmode to set the home heating system to use schedule/away/frost guard mode
Setroomthermpoint to set a manual temperature to a room or switch back to home mode
Getroommeasure to retrieve data from a room
Switchhomeschedule to apply a specific schedule
Synchomeschedule to modify a given schedule
Createnewhomeschedule to create a new schedule
Deletehomeschedule to delete a given schedule
Renamehomeschedule to rename a given schedule

As part of this process, we will deprecate the former Thermostat API in the upcoming months. Please make sure you update your code and start using newer methods as soon as possible for a smooth transition.

Enjoy :D !

Re: Thermostat API has evolved and now supports Valves

Posted: 16 Sep 2018, 22:02
by Tiziano
Hello Céline
Is there a possibility to get with „Getroommeasure“ the status of each valve (on = heating, off = closed)?

Thank you for your answer, Tiziano

Re: Thermostat API has evolved and now supports Valves

Posted: 04 Oct 2018, 17:58
by Céline
Hi Tiziano,

You'll find this information with homestatus request. For rooms containing valves you'll have the parameter heating_power_request (0 for closed and 100 for fully opened)

Re: Thermostat API has evolved and now supports Valves

Posted: 21 Feb 2019, 14:53
by antechrestos
Hi Céline,

I implemented the homesdata endpoint call, and I have difficulties sending several values for the

Code: Select all

gateway_types
query parameter.

Calling with:

Code: Select all

gateway_types=NaCamera,NaPlug
return no module
while calling with:

Code: Select all

gateway_type=NaCamera,NaPlug
or

Code: Select all

gateway_type=NaCamera&gateway_type=NaPlug
return both camera and plug modules

Maybe the documentation should be more clear about it.

Thank you

Re: Thermostat API has evolved and now supports Valves

Posted: 27 Feb 2019, 10:17
by antechrestos
Other question, how can we put the house in 'OFF' mode? Is the 'OFF" mode deprecated as well?

Re: Thermostat API has evolved and now supports Valves

Posted: 27 Feb 2019, 11:54
by Brieuc_Netatmo
Hi,
The OFF mode does not exist for Valves.

Re: Thermostat API has evolved and now supports Valves

Posted: 22 Apr 2019, 17:07
by ospevack
Is there any way to set the 'real temperature' of the valves? i have the healthy home, and would like to make the temperatures sync.

Re: Thermostat API has evolved and now supports Valves

Posted: 02 Feb 2020, 02:57
by Shadar
ospevack wrote: 22 Apr 2019, 17:07 Is there any way to set the 'real temperature' of the valves? i have the healthy home, and would like to make the temperatures sync.
Up @Brieuc_Netatmo any chance to see API updated with fonction "SET real temperature" for each valve ? :mrgreen: :?:

Thanks

Re: Thermostat API has evolved and now supports Valves

Posted: 12 Feb 2020, 17:31
by Céline
Hi Shadar,

Thermostat and valves are working on room basis. You can only set a room to a certain temperature which makes more sense from a user's perspective. We don't plan to change this behavior.

Re: Thermostat API has evolved and now supports Valves

Posted: 28 Feb 2020, 23:21
by Shadar
OK, Then can I set a " real Temperature" (correction) to a room in order to recalibrate all valves inside this room?

:)