External integration - Netatmo

:sun_behind_rain_cloud: Netatmo (external integration) — presentation + recap up to v1.3.0

Hello everyone :waving_hand:

I realize I’ve never opened a dedicated topic for the Netatmo external integration, even though it has existed since this summer (v1.0.0 on July 21, 2026, available to everyone since the arrival of external integrations with Gladys 4.84). I’m catching up: here is a complete presentation and the recap of versions up to v1.3.0, which has just been released. This topic will then be used to announce new features and gather your feedback.

:puzzle_piece: What is it?

This is the « external integration » version of the Netatmo service for Gladys: it runs in its own container, is installed from the integrations catalog, and this is where Netatmo updates now arrive (cameras, security accessories, real-time…).

:sparkles: What is supported

  • Weather: station (NAMain) and outdoor modules, wind, rain, and indoor (temperature, min/max, humidity, CO2, noise, pressure, wind, gusts, rain…).
  • Energy: thermostat (NATherm1), relay (NAPlug), and valves (NRV), with adjustable setpoint from Gladys (in 0.5 °C increments).
  • Cameras indoor (NACamera) and outdoor Presence (NOC): image on the dashboard (retrieved locally as a priority), monitoring switch, live stream with the quality of your choice.
  • Security accessories: door/window sensor (NACamDoorTag), indoor siren (NIS), smoke detector (NSD).
  • Battery and signal of each module, and a badge « unreachable » when Netatmo reports an offline module (Gladys then stops republishing its last values).
  • Real-time with Gladys Plus (optional): with your Open API key, changes are reported in 2-3 seconds instead of 2 minutes, and you gain scene triggers: movement, person detected, animal, and vehicle (Presence), smoke.

:rocket: Installation

  1. Create your own application on Netatmo Connect to obtain a client id and a client secret (no scope or redirect URL to configure).
  2. In Gladys: Integrations → search for Netatmo → Install.
  3. Configuration tab: paste the client id/secret, Save, then Connect.
  4. Choose the device families (Energy, Weather, Security), save, and create your devices from Discovery.

The complete step-by-step guide is in the integration documentation (« Documentation » link on the configuration screen).

:scroll: Version recap

  • v1.0.0 (July 21): OAuth2 connection, Weather and Energy devices, thermostat setpoint, cameras (image, monitoring, live stream).
  • v1.0.1: reliability (recovery after Netatmo outage, delays, tokens), video quality adjustment, no more false values for offline modules.
  • v1.1.0: Gladys Plus webhooks (real-time), door/window sensor, siren, and smoke detector, FR/EN documentation.
  • v1.1.2: heavy camera images are resized instead of being ignored.
  • v1.2.0: real-time detections (movement, person, animal, vehicle, smoke) usable in scenes.
  • v1.3.0 (October 16):
    • Cloud tag and classification in the Climate, Security, and Environment categories of the catalog;
    • the entire integration in French, English, German, and Spanish (configuration, messages, documentation);
    • technical upgrade (SDK, release tooling, version notes on GitHub).

:warning: Prerequisites

  • Gladys ≥ 4.86.0 for v1.3.0.
  • A Netatmo Connect application in your name (free).
  • Gladys Plus only if you want real-time and detections.

:counterclockwise_arrows_button: Coming from the built-in Netatmo service? Keep your history!

The external integration devices have new identifiers (ext:netatmo:*) and are created as new devices, but since Gladys 4.84.1 you can migrate each old device to its replacement: the history, scenes, and dashboards follow.

Before starting: do not delete your old Netatmo devices (migration starts from them), and migrate shortly after creating the new ones (if both have recorded values for the same period, only the history before the first value of the new device is taken over, to avoid double-counting).

  1. Install the external integration, connect it, and create your devices from the Discovery tab.
  2. Open Integrations → Netatmo (the built-in integration, marked as deprecated) → Devices tab.
  3. On an old device, click Migrate.
  4. Choose the Destination Device (the new device, under the external Netatmo integration).
  5. Check the Feature Matching: it is pre-filled, adjust if needed (especially the temperature lines of thermostats and stations). « Do not migrate » removes the history of the concerned feature.
  6. Click Migrate and delete the old device.

Gladys moves the history, updates your scenes and dashboards, takes over the room, then deletes the old device. For a large history, follow the progress in Settings → Tasks (an interrupted migration can be restarted, it only resumes what remains).

:motorway: In progress, Gladys core side

Two requests from @smuteau require an evolution of the core, the PRs are proposed:

  • the battery level displayed on the card of each device (Devices tab) — the integration already publishes the battery;
  • the photo of each device, like with the built-in service (the images will remain in the integration container).

:test_tube: Feedback welcome

Thanks in advance for your feedback :folded_hands:

Hi @Terdious, I’d propose a PR for the thermostat because I forked it on my side to add some missing information. Or I could give you an update on what I need.

With pleasure @Will_71 :smiling_face_with_three_hearts: :folded_hands:

:rocket: Netatmo 2.0.0 is available!

Major update of the Netatmo external integration, and at the same time the minimum version is now Gladys 5.2.0.

New devices

  • :window: Bubendorff / iDiamant roller shutters (NBR, NBO, NBS): open / close / stop and position, via the new « Roller shutters » switch.
  • :bell: Video doorbell: image on the dashboard and « If the doorbell rings » scene trigger.
  • :cloud: Carbon monoxide detector: CO alert usable in scenes, with pre-alarm.
  • :herb: Home Coach (air quality): temperature, humidity, CO2, noise, pressure and air quality index (with color on the dashboard and HomeKit, plus the level in full text), via the « Air quality » switch.

Gladys 5.x new features

  • :fire: Heating mode of the house (Planning / Away / Frost protection) on thermostats and valves. @Will_71, feel free to tell me if this matches what you wanted to do and otherwise make a PR on top of it.
  • :clapper_board: Scenes: triggers « a known person arrives / leaves », « the siren rings »; actions « change heating mode », « mark absent / present ».
  • :bar_chart: Dashboard widgets: Netatmo Weather, Netatmo Heating, Netatmo Cameras.

Reliability

  • The weather continues to be reported even if the Netatmo weather service fails, and a prolonged failure is displayed ( Degraded badge + message in the configuration).
  • The end of a smoke alert (« smoke dissipated ») no longer retriggers the smoke scenes.

:warning: What to do after the update

  • Gladys 5.2.0 minimum to receive this version.
  • For the doorbell and the shutters: re-click on « Connect » in the configuration (new Netatmo permissions; the screen indicates if needed).
  • For already created devices: Discovery → Update on thermostats / valves (heating mode).

:folded_hands: Call for testers

Everything was developed based on the Netatmo API (and verified with what Home Assistant / pyatmo and openHAB do), but without all the hardware at hand. If you have a CO detector, a doorbell, Bubendorff shutters or a Home Coach, your feedback (and a snippet from the Logs tab) is welcome here!

:memo: Full release notes: Release v2.0.0 · Terdious/gladys-netatmo · GitHub
:open_book: Documentation: gladys-netatmo/docs/fr.md at master · Terdious/gladys-netatmo · GitHub

Netatmo Integration v2.1.0 Available :tada:

New minor version. It still requires Gladys 5.2.0 minimum (5.2.1 recommended).

:fire: Heating

  • Modulating Thermostat / OpenTherm (OTM + OTH relay): It works like the classic thermostat (temperature, setpoint, heating mode, boiler state, battery). The relay reports the outdoor temperature and a binary Boiler Fault.

  • BTicino Smarther with Netatmo Thermostat (BNS): temperature, setpoint, heating mode, boiler and air conditioning state. :warning: New Netatmo permissions are required: click on « Connect » again in the integration configuration (the screen reminds you).

  • Advanced heating, 4 new scene actions:

    • setpoint for a room, with an optional duration;
    • boost for a room;
    • return to schedule;
    • choose the heating schedule.

    The heating widget also displays the active schedule, signals rooms in manual or boost mode, and offers a « Change Schedule » button.

:camera: Cameras and Security

  • Indoor Advance Camera (NPC): image on the dashboard, on/off surveillance, motion and person detection. It appears in the cameras widget. :warning: It also requires clicking on « Connect » again.
    Limitation: Like the doorbell, it only streams live in WebRTC, which Gladys cannot yet read. For now, we only have the image. Two options are being studied.
  • Outdoor Camera Spotlight (NOC): the on/off/auto mode becomes two features, Spotlight (a light: on = forced) and Spotlight Auto Mode (a switch). A « turn everything off » scene never turns off the auto mode. On already created cameras, do Update in the Discovery screen.
    Only one « mode » feature is offered on the Gladys side. We will migrate as soon as it is available.
  • Presence of known people in cameras: a device « - Known People », with a presence per person named in the Netatmo application, updated in real time by webhooks.

:wrench: Fixed

  • A refresh triggered by a webhook always starts with fresh Netatmo data.

To Test on Real Hardware

If you have an OpenTherm thermostat, a Smarther, an Advance camera, or an outdoor camera, your feedback is precious: values reported, projector commands, boiler fault.

Full notes: Release v2.1.0 · Terdious/gladys-netatmo · GitHub

A quick update on the limits of these two versions: they are already handled by core and SDK PRs waiting to be merged. @pierre-gilles, when you have a moment to review them :smiley:

The Home Coach provides a level on a scale of 5 (good → very bad), not an index. For now, the integration converts this level into an approximate index, with the label in French only. Once these PRs are merged, we will switch to a standard « air quality level » type, translated and with history:

The chosen option: WebRTC live stream negotiated by the browser. Gladys simply relays the offer and response to the integration, as Home Assistant does for these cameras. The stream goes directly from the Netatmo cloud to the browser: no conversion, sound is preserved, very low latency, and it also works via Gladys Plus.

On the integration side, I am preparing the connection for the doorbell (NDB) and the Advance camera (NPC) (#70). It will remain inactive until Gladys supports it. I will be able to test it on my own doorbell.

The new standard lighting « operating mode » type (off/on/auto/schedule) will be used for all lights that have an auto mode: camera projectors, motion detector lights, Zigbee, Matter… Once merged, the two projector features will become one (#69).

Thanks in advance! As soon as these PRs are published, I will update the integration side.

Netatmo Integration v2.2.0 Available :tada:

A small version that prepares the next steps. Gladys 5.2.0 minimum is still required.

:bell: BTicino Classe 300X / Classe 300 EOS Intercom (Preview)

  • New switch « BTicino Intercom (Classe 300) — Preview », disabled by default.
  • Once enabled, the intercom modules are discovered: indoor station, street panel, strike, staircase lighting, outlet, and X module. For now, we have their signal and the « unreachable » indicator.
  • Activating the switch requires 4 additional Netatmo permissions: click on « Connect » again (the configuration screen reminds you). If you don’t have a BTicino intercom, nothing changes for you; no reconnection is necessary.
  • This is a data collection step. A log [bticino-diagnostic] records the raw data of these modules, masking tokens, keys, and emails. If you have a Classe 300, your logs will help me add the doorbell as a scene trigger, the door opener, and the staircase lighting. Make sure to review them before posting.

:movie_camera: Direct WebRTC for the Doorbell and Advance Camera (Prepared)

The integration already knows how to relay the direct WebRTC stream from the doorbell (NDB) and the Advance indoor camera (NPC). It only activates it once Gladys supports it (core PR #3215 and SDK #43). Until then, nothing changes: you keep the static image.

Full notes: Release v2.2.0 · Terdious/gladys-netatmo · GitHub

Hello,

I’m going to test this integration.

Is the Gladys Plus OPEN API key the RSA key?

Edit:

Ok, you need to be logged in with plus.gladysassistant to see the Open API tab.

Settings (rather than « Settings » in the doc)

I consistently get an error when I try to save my cameras


In the logs, there is no device name, but its address:
[2026-10-19T07:20:37.448Z] [INFO] [netatmo-camera] Netatmo camera 70:xx:xx:xx:xx:xx: snapshots will use the VPN URL

Thanks @gaetanb76 for the feedback and screenshot!

This is a now-known bug on Gladys’ side, not the integration. I encountered the same issue yesterday. When you click Save in the Devices tab, Gladys sends the entire device, including the last camera image. However, this route is limited to 100 KB: a camera with a recent image exceeds this limit, and the save is rejected (error 413 in the browser console). That’s also why an unreachable camera, i.e., without an image, saves without any issues.

The camera works normally in the meantime: only the saving of the name or room fails.

For the log snapshots will use the VPN URL, this is normal: the integration identifies cameras by their Netatmo ID, which is their MAC address. This line simply means that the image is retrieved via the Netatmo cloud rather than locally.

@pierre-gilles, @cicoub13, @bertrandda: when you have a moment, PR #3228 fixes this bug for all integrations that publish a camera image. It’s small and blocking for users. Thanks in advance :pray:

Hi,

Thanks for this ultra-fast response :smiley:

So, we save and tough luck for the error, is that right?

Let’s say that for now, the camera is supposed to work normally, yes, while waiting: only the recording of the name or the room fails.

To confirm that this is the case: open the browser console (F12 → Network tab), then click on Save. You should see POST /api/v1/device in 413 with Payload too large. If it’s something else, send me the displayed response.

Yes, Payload Too Large

Have the cameras from my previous Netatmo integration disappeared on their own? Is this normal?

However, they are still present on my Dashboard and available to be added to the Dashboard.
I have two sets of cameras.

Additionally, it is impossible to rename a camera in the devices section. The new name is not saved.

Already reviewed, waiting for your feedback :wink:

Thanks @pierre-gilles,

Corrections made by Claude according to your review.

I reposted a review (well, Claude), for info I use Anthropic’s code-review skill, don’t hesitate to use it in a fresh conversation before asking for my review, because on my side, it will be Claude who runs it anyway :joy:

Thanks to you,

Sorry, indeed I was doing a review, but in the same session as the working one… I don’t know if that affects the fact that he doesn’t see what yours is returning ^^ but apparently yes!!

So I restarted in a fresh new session, and I asked him to post his own review, so now we can see it!! From his point of view everything is well corrected, and he doesn’t see anything more than what yours had seen.

He also created the follow-up issue for the mentioned point: Device list endpoints should not return the camera image in `camera/image` `last_value_string` · Issue #3237 · GladysAssistant/Gladys · GitHub

Hello @Terdious,

Thank you for the integration! After adding support for Bubendorff roller shutters, I decided to take the plunge and buy the iDiamant plug :slight_smile:

From my phone, the shutter control works, but not from Gladys.

I followed the procedure to add a shutter:

  • Enabling the « Roller Shutters » function
  • then I reconnected the integration to grant permissions for the shutters
  • it worked very well, the shutter is well added to Gladys

After that, what works: reading the shutter position

What doesn’t work:

  • Shutter control
  • Signal strength (no signal on Gladys while the app displays 3 out of 4 bars for WiFi / I haven’t found the signal strength between the iDiamant plug and the shutter but the plug is located just below the shutter so 0 seems very unlikely)

Here are the integration logs:

[2026-10-19T16:03:24.395Z] [INFO] Starting the Netatmo integration..```

Hello @PhilippeMA, and thank you for this very detailed feedback, the logs are very helpful :smiley:

The shutter command

The logs show that your commands are indeed reaching the integration (onSetValue … position = 38, then state = -1 to close and state = 0 to stop). The integration then sends them to Netatmo, in the same format as Home Assistant: the shutter, the iDiamant gateway, and the house.

The issue: Netatmo can respond « OK » while refusing the command, with an error code slipped into its response. The integration was not reading this code for the shutters, hence a command that has no effect and logs that say nothing. This is fixed in v2.6.2, available now (Release v2.6.2 · Terdious/gladys-netatmo · GitHub). When Netatmo refuses, Gladys now displays an error, and the logs have a line with the Netatmo code:

Command …:state = -1 failed: Netatmo did not apply target_position 0 to shutter 0000991652 (bridge …, home …): error X on …

After the update, could you try Open, then Close, and paste the following lines? With the error code, we will know what to fix.

Very useful additional information: in Integrations → Netatmo → Configuration, run the action Device Diagnostic on the shutter, then paste the result here. It shows what Netatmo returns for the shutter: reachable or not, position, target_position:step, etc. The tokens and addresses are removed, but please read it again before publishing it. If target_position:step is 100, it means that this model can only open, close, and stop, and cannot go to an intermediate position (38 %).

Signal strength

The 3 out of 4 bars in the Netatmo app is the WiFi of the iDiamant plug. In Gladys, the « Signal Strength » feature of the shutter displays something else: the radio link between the plug and the shutter, as Netatmo provides it (rf_strength). However, Netatmo often returns 0 for Bubendorff shutters, including in the reference data of Home Assistant. The diagnostic will tell us what Netatmo returns for you.

Question: would seeing the WiFi of the iDiamant plug in Gladys be useful to you, for example to monitor a plug that is dropping? If so, I can add it to the shutter.

The 503 errors in the logs

These are temporary outages of the Netatmo cloud (« service unavailable »), not a problem with your installation. The integration keeps the last values and retries in the next cycle, 2 minutes later: that’s why your weather stations continue to work.