For Agents
Read Netatmo weather station, thermostat, and camera data, manage heating schedules, and subscribe to webhooks for home and security events.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Netatmo, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Netatmo API.
Discover the Netatmo devices and modules attached to a user account through /devicelist
Read indoor and outdoor weather measurements from a Netatmo Weather Station
Read air quality data from a Netatmo Healthy Home Coach via /gethomecoachsdata
GET STARTED
Use for: Read the current outdoor temperature from a Netatmo Weather Station, List all Netatmo devices linked to my account, Get the air quality reading from a Netatmo Healthy Home Coach, Create a new heating schedule for a Netatmo thermostat
Not supported: Does not handle device firmware updates, billing, or third-party smart-home device control — use for Netatmo weather, thermostat, and camera data only.
The Netatmo API is the cloud interface for Netatmo's connected weather stations, smart thermostats, indoor and outdoor cameras, and home coach devices. The 22 endpoints cover device discovery, sensor reads, schedule management, webhook subscription, and snapshot capture from cameras, so a developer or smart-home integrator can read environmental data, control heating schedules, and react to camera events programmatically.
Manage thermostat heating schedules using /createnewschedule and related endpoints
Capture a still picture from a Netatmo camera via /getcamerapicture
Subscribe and unsubscribe webhooks to receive home and camera events
Patterns agents use Netatmo API for, with concrete tasks.
★ Personal Weather Dashboard
Smart-home enthusiasts pull /devicelist and the weather station reads to render a personal dashboard with indoor temperature, humidity, CO2, and outdoor conditions. The endpoints expose the same numbers shown in the Netatmo app, so a Home Assistant or Grafana board can sit alongside the manufacturer app rather than replace it.
List the Netatmo devices on my account, then return the latest indoor temperature and CO2 reading from the main weather station.
Heating Schedule Automation
Owners of a Netatmo Smart Thermostat use /createnewschedule and the related schedule endpoints to switch heating profiles based on calendar events or occupancy. An agent can flip to an away schedule when nobody is home and back to the comfort schedule before they return, replacing the static weekday/weekend pattern most thermostats default to.
Create a new heating schedule named Away that holds 16 degrees Celsius from 8am to 6pm on weekdays.
Camera Event Webhooks
Security-aware integrators register a webhook through /addwebhook so Netatmo Welcome and Presence cameras push motion, person, and animal events to an external service. The /getcamerapicture endpoint then fetches a still for incident review, which avoids polling the camera and gives near-real-time event capture.
Register a webhook at https://example.com/netatmo-events, then capture a snapshot from the front-door camera when a motion event arrives.
AI Agent Integration via Jentic
An AI agent uses Jentic to read Netatmo sensors and act on them inside a wider home automation flow. Jentic exposes /devicelist, /gethomecoachsdata, and /getcamerapicture by intent, the agent supplies the device id, and the OAuth token stays in the Jentic vault rather than the agent context.
Use Jentic to search for read netatmo sensor data, load the schema, and return the current outdoor temperature for my home.
22 endpoints — the netatmo api is the cloud interface for netatmo's connected weather stations, smart thermostats, indoor and outdoor cameras, and home coach devices.
METHOD
PATH
DESCRIPTION
/devicelist
List devices and modules on the account
/gethomedata
Get home configuration and rooms
/gethomecoachsdata
Read Healthy Home Coach measurements
/getcamerapicture
Capture a still picture from a camera
/geteventsuntil
List home events up to a given timestamp
/createnewschedule
Create a new thermostat heating schedule
/addwebhook
Subscribe a webhook for home events
/dropwebhook
Unsubscribe a webhook
/devicelist
List devices and modules on the account
/gethomedata
Get home configuration and rooms
/gethomecoachsdata
Read Healthy Home Coach measurements
/getcamerapicture
Capture a still picture from a camera
/geteventsuntil
List home events up to a given timestamp
Three things that make agents converge on Jentic-routed access.
Credential isolation
Netatmo OAuth tokens are stored encrypted in the Jentic MAXsystem vault, refreshed automatically, and injected at execution time so the raw token never enters the agent context.
Intent-based discovery
Agents search Jentic by intent (for example, read netatmo weather data) and Jentic returns the matching operation with its input schema, so the agent calls the right endpoint without reading the spec.
Time to first call
Direct Netatmo integration: 1-2 days for OAuth flow, token refresh, and webhook handling. Through Jentic: under 1 hour to search, load, and execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Netatmo API through Jentic.
What authentication does the Netatmo API use?
Netatmo uses OAuth 2.0 — the spec exposes both code_oauth (authorisation code) and password_oauth flows. Jentic stores the access and refresh tokens encrypted in the MAXsystem vault and refreshes them automatically, so the raw token never enters the agent context.
Can I read sensor data from a Netatmo Weather Station through the API?
Yes. Call /devicelist to discover the station and module identifiers, then read measurements via the data endpoints. /gethomecoachsdata covers Healthy Home Coach air quality, /gethomedata covers home configuration, and the device list response includes recent dashboard values for the weather station modules.
How do I create a thermostat heating schedule with the Netatmo API through Jentic?
Search Jentic for create netatmo heating schedule, load the schema for POST /createnewschedule, then execute with the schedule name and time blocks. The full flow is pip install jentic, search, load, execute.
What are the rate limits for the Netatmo API?
Netatmo enforces per-application and per-user rate limits documented on dev.netatmo.com — typically a few requests per second per user and a few hundred per hour per application. Use webhooks via /addwebhook for event-driven flows rather than polling the device endpoints.
Can I subscribe to Netatmo home events through a webhook?
Yes. POST /addwebhook with the callback URL and Netatmo will push home and camera events to that URL. Use /dropwebhook to unsubscribe when the integration is decommissioned.
Can I capture a still picture from a Netatmo camera?
Yes. /getcamerapicture returns a JPEG given the camera id. Combine it with the events from /geteventsuntil to fetch a snapshot tied to a specific motion or person event.
/createnewschedule
Create a new thermostat heating schedule
/addwebhook
Subscribe a webhook for home events
/dropwebhook
Unsubscribe a webhook