Reference · built on requestConnectorSensors, meters & gateways

Netatmo Connect

Weather Station, Aircare, and Energy device data and webhook events from the Netatmo Connect API.

Request accessPricing ↗

About

Netatmo Connect is the cloud API for Netatmo and Legrand home devices. The Weather Station reports temperature, humidity, CO2, pressure, noise, rain, and wind through /getstationsdata. The Smart Indoor Air Quality Monitor reports the same indoor measures plus a Health index through /gethomecoachsdata. Energy devices expose room temperatures, setpoints, schedules, and boiler activity through /homestatus. Cloud weather data updates every 10 minutes; /homestatus reads the devices in near real time. There is no local path: data and devices are reachable only through the Netatmo cloud.

An operator on Fibric reads these measures, listens for device_event webhooks, and proposes the room setpoint, the schedule switch, or the ticket for your approval.

This is a reference listing. It documents what Fibric would read from Netatmo Connect and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Weather Station measures through GET /getstationsdata: temperature, humidity, CO2, pressure, noise, rain, and wind, each with current, min, max, and their dates
  • Module diagnostics in the same response: radio status, wifi status, battery level, setup date, and reachability for NAMain and NAModule1 to NAModule4
  • Smart Indoor Air Quality Monitor (NHC) readings and its 0 to 4 Health index through GET /gethomecoachsdata
  • Measure history for a device or module through GET /getmeasure, and room temperature history through GET /getroommeasure
  • Homes, topology, and station type (owned, friend, favorite) through GET /homesdata; current home and device status through GET /homestatus
  • Webhook pushes by HTTP POST: device_event, home_event_changed, topology_changed, webhook_activation, and webhook_deletion, signed in the X-Netatmo-secret header
  • Public outdoor measurements from stations in a defined area through GET /getpublicdata

Proposed actions

  • Target capability: propose a room setpoint or a manual, max, or home mode through POST /setroomthermpoint
  • Target capability: propose a home heating mode of schedule, away, or frostguard through POST /setthermmode
  • Target capability: propose switching a home to an existing heating schedule through POST /switchhomeschedule
  • Target capability: propose a per-user webhook subscription through POST /api/addwebhook or POST /webhooks/v1

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Ventilate on CO2, not on a timer

    Read CO2 and the Health index from every station and Air Quality Monitor. When a room stays above your threshold, propose the ventilation change and notify the person responsible for that space.

    With CO2 Ventilation, Indoor Air

  • Replace the module before the data gap

    Battery level, radio status, and reachability come back with every /getstationsdata call. When an outdoor or rain module reads very low or goes unreachable, propose the replacement task.

    With Sensor Health

  • Put a drifted room back on schedule

    Compare each room's setpoint and mode from /homestatus with its schedule. When a manual override outlasts its duration or a home is off frostguard in winter, propose the correction.

    With Setpoint Drift, Freeze Protection

Requirements

  • A registered Netatmo Connect application with a client_id, a client_secret kept server-side, and a redirect URI
  • Each user authorizes the scopes the app requests; when none is requested the default is read_station
  • A webhook endpoint that answers HTTP 200 within 5 seconds; the URL is set per application and users must reauthorize after it changes
  • A note to Netatmo before commercial use of the Weather API, as the developer guidelines ask
Authentication
OAuth 2.0 Authorization Code Grant against api.netatmo.com/oauth2: the app exchanges a code for a Bearer access token and a refresh token, scoped to families such as read_station, read_homecoach, read_thermostat, and write_thermostat.

Limits

  • Per user: 50 requests every 10 seconds and 500 every hour. Per application: 2 requests per user, capped at 200, every 10 seconds
  • An application with fewer than 500 users has 2000 requests every hour; the hourly quota rises in steps with the user count
  • Cloud weather values refresh every 10 minutes; only /homestatus reads the devices themselves in near real time
  • Webhooks retry up to 3 times, can repeat or arrive out of order, and a failing endpoint is suspended for up to 10 minutes with its events dropped

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Netatmo Connect ↗

Questions and answers

How often does Netatmo weather data update?
The cloud value read through /getstationsdata refreshes every 10 minutes. /homestatus reads the devices and returns near real time data, under 10 seconds. Webhook device_event pushes arrive within a few seconds of a change; webhooks are in beta for Legrand product types.
Which scopes does Fibric need?
read_station for the Weather Station, read_homecoach for the Air Quality Monitor, read_thermostat and write_thermostat for Energy devices. Webhook delivery is documented for read_station, read_thermostat, read_smarther, read_magellan, and read_mhs1 only, so Aircare data is polled. The access_ scopes need Netatmo approval and are not used.
Can Fibric read a device on the local network?
No. Netatmo states that the only way to reach data and devices is through the Netatmo cloud. Every read goes to api.netatmo.com with the user's access token, and every write is proposed to you before it is sent.
Ask about Netatmo Connect

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Netatmo Connect through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy