You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Thomas Renger 71df28f7cf
Merge pull request #1 from xperimental/master
7 months ago
.github/workflows Add action for pull-requests 8 months ago
internal Fix lastRefreshError not being reset on success (#11) 8 months ago
.dockerignore Update build system 1 year ago
.gitignore Add readme and license. 5 years ago
CHANGELOG.md Release 1.3.0 12 months ago
Dockerfile Update Go to 1.14.7 12 months ago
LICENSE Update license. 4 years ago
Makefile Extend Makefile for selecting architecture 1 year ago
README.md Update readme for cached data 1 year ago
go.mod Fix lastRefreshError not being reset on success (#11) 8 months ago
go.sum Update Prometheus client 12 months ago
main.go Fix lastRefreshError not being reset on success (#11) 8 months ago
version.go Add handler for version information 1 year ago

README.md

netatmo-exporter Docker Build Status

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

Installation

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
make

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.

Usage

$ 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:

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