[RE-RELEASE] Netatmo (Connect) - Weather Station

[dJOS]

G'day All, seeing as cybrmage hasn't been around since 2020, I've taken the liberty to clone this app to my GitHub, make some improvements and publish it via HPM:

Note: I am still actively maintaining this Integration as of 2026.

Dashboards:

I've also written an RM 5.1 Rule (available from my GitHub below) that uses a Smart Switch to detect when your Netatmo Basestation stops communicating back to the cloud servers and will power cycle it. The Base Station Offline Threshold is configurable in the app - the default is 30 mins.

Weather Station - Netatmo - Offline Recovery.txt

You can find the original topic for this App here:

[RELEASE - UPGRADE] Netatmo (Connect) - Simple netatmo interface

This is a update to the simple Netatmo Connect App/driver package that was originally created for Smarthings by Brian Steere and ported to Hubitat by Stuart Buchanan (fuzzysb/Fuzzyligic), and long abandoned. The changes include: Add debug logging control to the application. Defaults to disabled. When disabled there is only logging for startup, auth and errors - no logging is done for normal operation of the application/drivers. Removed "Thermostat" capability from device drivers. Extend error…

UPDATE: here's brief guide on hooking Netatmo Weather Stations up to Weather Underground:

Netatmo Owners - PWS integration with Weather Underground

If you would like to get access to Weather Underground and have a Netatmo weather station, I stumbled across a really nice way to do this using Home Assistant. You can find the details here: But the general gist is to get the Netatmo integration working on HA, then setup a Weather Underground account with PWS (just select the type as Netatmo even tho it does nothing), then install the above WU data uploader into HA and make sure it's uploading to WU. Then in Hubitat you'll be able to access…

UPDATES:

26th July 2026

v1.7.3 - Fixed a crash that stopped all devices updating and fixed token refresh retry

19th June 2026

v1.7.2 - Base station presence is now staleness-based: flips to "not present" when no new data has been received for longer than the configurable "Base Station Offline Threshold" (default 30 min). Also added a numeric dataAge attribute (minutes since last Netatmo update)

v1.7.1 - Signal strength (WiFi/RF) shown as Good/Average/Poor bands instead of raw values, and moved onto the last (Battery) row in the Summary tiles

• Overview tile no longer prints "null" for Outdoor/Wind/Rain when the base station has no such module feeding it (lines are now omitted when data is absent)
• Additional device attributes now available: presence (online/offline), firmware and last_seen (all devices); wifi_status (base); rf_status and battery_vp (modules); AbsolutePressure (base); max_wind_angle (wind)

18th June 2026 - v1.7.0 - Major overhaul of OAuth token handling and security improvements, added user-selectable polling interval, a default 50 dB sound threshold, opened the Connect button in a new tab.

28th March 2026 - v1.6 - Bug fixes: OAuth token parsing, stray syntax error, capability names, namespace/author update

1st October 2024 - v1.5 - Added a manual reauthorize option

7th November 2022 - v1.4 - Updated URL to https://dev.netatmo.com/

30th September 2022 - v1.3 - fixed “An error occurred while installing the package: Failed to upgrade app” error.

29th September 2022 - v1.2 - Fixed all debug logging code, so it is conditional to you actually turning it on.

[Inge_Jones]

Do you have a link to the raw code we could use, as I don't use HPM?

[dJOS]

Sure, it’s on my GitHub:

GitHub - dJOS1475/Hubitat_Netatmo: Netatmo Application for Hubitat

[monsterdykaren]

Getting this message as I’m trying to connect to my weather station. Any Idea what might cause this?

[dJOS]

Have you generated an API key via the Netatmo dev portal?

Here's the URL:

https://dev.netatmo.com/apps/

[monsterdykaren]

Yep, I did that to the other version of the app and reused the client ID and client secret for this version.

[dJOS]

I’d suggest there’s been a copy paste error then, I haven’t changed any code around the authentication process.

I’d recommend going into the Netatmo dev portal and copying the keys into a text only document (eg notepad on windows or textedit on Mac), then copying them into the app.

If falls, you might need to go into the “apps code” section on Hubitat, open the app and hit the oauth button. Then save and exit the apps code.

[monsterdykaren]

Ok, I’ll give reentering my credentials a try. Pressing the ouath-button in app code and then save did’nt help.

Otherwise I’ll try create a new client id and a new client secret in Netatmo dev.

[dJOS]

Cheers. Sometimes copying directly from HTML pages causes issues - I always paste into a plain text file first to remove any rubbish.

[monsterdykaren]

Thanks for the help! I’ll post the result here when I’ve tried..

[brad]

I’m assuming others are receiving this email as well, but looks like we’ll need to update the way the app authenticates:

Netatmo API Security Update
Dear Netatmo developer,
To improve the security of our products, we inform you that the Client Credentials grant type method will be completely removed. It will no longer be possible to authenticate with the username and password of the user.

The effective date of this update is October 2022.

How can you authenticate with Netatmo API ?
From this date, the OAuth2 authorization code flow must be followed for authentication.

You can find details on this method on our website:
Netatmo Connect Authentication

For tests, you can also get an Access Token from our developper portal.
Netatmo Developer Portal

• Log in
• Go on your account
• Select the application for your test
• Click on "Generate a Token"

You can now use this Access Token for 3 hours.
Sincerely,
Legrand - Netatmo - Bticino

[dJOS]

@brad

looks like we’ll need to update the way the app authenticates

I don’t believe so, I think it’s saying that user ID and password option will no longer be valid ways to access the API.

It will no longer be possible to authenticate with the username and password of the user.

This app already uses Oauth via an API key etc.

[brad]

Ok. I just noticed some language about refresh tokens, which I don’t think the app uses. The Tesla Connect app that I use needed to be updated to periodically generate refresh tokens, so I was thinking that was the case here as well. If not, then great!

[dJOS]

@brad

If not, then great!

I hope that the case, I guess we’ll see.

[monsterdykaren]

@Inge_Jones Did you solve it? I haven’t have the time to look at it yet.

[dJOS]

I’m not seeing a problem, only deleted posts.

[monsterdykaren]

Sorry! It was supposed to be an answer to one of the deleted posts. I got an email with the content of the deleted posts so thats why I answered.

[Inge_Jones]

Sorry for any confusion. I realised I had just made a silly mistake myself and it was quickly corrected. In my case it was just I forgot to enable OAuth in the App editing screen itself, and thought I was gonna do it in the App at runtime

[dJOS]

@Inge_Jones

I forgot to enable OAuth in the App editing screen itself, and thought I was gonna do it in the App at runtime

Hehe, been there, done that!

[dJOS]

G'day all, I added a link to the first post to a brief guide to hooking up your Netatmo to Weather Underground.

Netatmo Owners - PWS integration with Weather Underground

If you would like to get access to Weather Underground and have a Netatmo weather station, I stumbled across a really nice way to do this using Home Assistant. You can find the details here: https://community.home-assistant.io/t/wunderground-data-uploader/330332 But the general gist is to get the Netatmo integration working on HA, then setup a Weather Underground account with PWS (just select the type as Netatmo even tho it does nothing), then install the above WU data uploader into HA and ma…