Go to file
Thomas Renger 71df28f7cf
Merge pull request #1 from xperimental/master
Catch up with upstream
2021-01-13 17:22:23 +01:00
.github/workflows Add action for pull-requests 2020-11-21 20:34:57 +01:00
internal Fix lastRefreshError not being reset on success (#11) 2020-11-21 20:40:24 +01:00
.dockerignore Update build system 2020-06-21 14:57:31 +02:00
.gitignore Add readme and license. 2017-01-08 23:45:31 +01:00
CHANGELOG.md Release 1.3.0 2020-08-09 16:33:17 +02:00
Dockerfile Update Go to 1.14.7 2020-08-09 16:24:06 +02:00
LICENSE Update license. 2018-02-18 02:26:04 +01:00
Makefile Extend Makefile for selecting architecture 2020-06-21 15:09:49 +02:00
README.md Update readme for cached data 2020-06-27 18:09:04 +02:00
go.mod Fix lastRefreshError not being reset on success (#11) 2020-11-21 20:40:24 +01:00
go.sum Update Prometheus client 2020-08-09 16:26:37 +02:00
main.go Fix lastRefreshError not being reset on success (#11) 2020-11-21 20:40:24 +01:00
version.go Add handler for version information 2020-06-21 15:26:53 +02:00


netatmo-exporter Docker Build Status

Simple prometheus exporter for getting sensor values NetAtmo sensors into prometheus.


Run docker container

The exporter is available as a Docker image: xperimental/netatmo-exporter

The latest tag is built from the current master, tags tagged since the Docker support was added are also available as a tag in Docker.

Build from source

Because this program uses the "Go Module" feature introduced in Go 1.11, you'll need at least that version of Go for building it.

If you have a working Go installation, getting the binary should be as simple as

git clone https://github.com/xperimental/netatmo-exporter
cd netatmo-exporter

If you want to build the exporter for a different OS or architecture, you can specify arguments to the Makefile:

# For 32-bit ARM on Linux
make GO_ARCH=arm
# For 64-bit ARM on Linux
make GO_ARCH=arm64

NetAtmo client credentials

This application tries to get data from the NetAtmo API. For that to work you will need to create an application in the NetAtmo developer console, so that you can get a Client ID and secret.


$ netatmo-exporter --help
Usage of netatmo-exporter:
  -a, --addr string                 Address to listen on. (default ":9210")
      --age-stale duration          Data age to consider as stale. Stale data does not create metrics anymore. (default 30m0s)
  -i, --client-id string            Client ID for NetAtmo app.
  -s, --client-secret string        Client secret for NetAtmo app.
      --log-level level             Sets the minimum level output through logging. (default info)
  -p, --password string             Password of NetAtmo account.
      --refresh-interval duration   Time interval used for internal caching of NetAtmo sensor data. (default 8m0s)
  -u, --username string             Username of NetAtmo account.

After starting the server will offer the metrics on the /metrics endpoint, which can be used as a target for prometheus.

Passing secrets

You can pass credentials either via command line arguments (see next section) or by populating the following environment variables:

  • NETATMO_EXPORTER_ADDR Address to listen on
  • NETATMO_CLIENT_ID Client ID for NetAtmo app
  • NETATMO_CLIENT_SECRET Client secret for NetAtmo app
  • NETATMO_CLIENT_USERNAME Username of NetAtmo account
  • NETATMO_CLIENT_PASSWORD Password of NetAtmo account

Cached data

The exporter has an in-memory cache for the data retrieved from the Netatmo API. The purpose of this is to decouple making requests to the Netatmo API from the scraping interval as the data from Netatmo does not update nearly as fast as the default scrape interval of Prometheus. Per the Netatmo documentation the sensor data is updated every ten minutes. The default "refresh interval" of the exporter is set a bit below this (8 minutes), but still much higher than the default Prometheus scrape interval (15 seconds).

You can still set a slower scrape interval for this exporter if you like:

  - job_name: 'netatmo'
    scrape_interval: 90s
      - targets: ['localhost:9210']