Coreflux Templates

Netatmo Energy over REST, OAuth 2 on the broker

Poll Netatmo valves into a UNS and write setpoints back; OAuth 2 token rotation runs in the broker.

Dataflow

How it flows

Actions, models, routes and the topics that link them. Click a node to trace its flow.

Summary

Netatmo smart radiator valves (NRV), thermostats (NATherm1) and their relay report to the Netatmo cloud only: there is no local API. This template polls the Netatmo Energy API from the broker, publishes every room into a Unified Namespace, and lets an operator change a room's setpoint from the UNS.

The whole OAuth 2 refresh-token rotation runs inside the Coreflux broker: no container, no cron script, no token in a file. A REST Route posts the refresh, an action keeps the rotated pair in the broker's encrypted secret store, and the Route reads the tokens again per request. They never travel from a client and never sit in your git repository.

It is the pattern we run against a live Netatmo account, generalised and hardened by what operating it taught us. Two of its rules came from failures: the refresh must never land in the same second as a poll, and the token store must only ever write a real token pair.

 

Key features

The notebook

What’s inside

Browse the markdown and code cells before you download.

LoT Notebooks:
Related use cases

Similar templates

Templates chosen for overlap in routes, tags, and category.

View all in IoT & Connected Devices

Get this template

2 files