How your sensors and devices connect
Every device gets its readings to SensorConsole by one of two routes: it sends them to us directly, or we collect them from the manufacturer's cloud. Here is the path for everything we support.
Fastest route for most people:
if your device's app has a custom server or other weather service setting, or you run a DIY sensor
on an ESP32, Raspberry Pi or Home Assistant, use a generic push device on the
connect a sensor page. Readings arrive in real time
and no API key from anyone is needed.
| Device | How it connects | Status | Notes |
|---|---|---|---|
| Wi-Fi stations with a custom server option | sensor → radio or Wi-Fi → the device's own app → straight to SensorConsole | live | Covers Ecowitt, Bresser and other stations that can send data to a server of your choice. Works over HTTP or HTTPS. |
| DIY boards and platforms | your code → straight to SensorConsole | live | ESP32, ESPHome, Tasmota, Arduino, Raspberry Pi, Node-RED and Home Assistant. Plain HTTP works for boards that cannot do HTTPS. |
| Cameras and NVRs with a motion webhook | camera detects motion → its own webhook feature → straight to SensorConsole | live | Motion events and an optional snapshot link only, never video. Camera devices are always private and can never be shared publicly. |
| Ecowitt | sensor → 433MHz radio → Wi-Fi gateway → pushed directly to SensorConsole (or polled from Ecowitt's cloud) | live | One gateway can feed many sensors; each is added by channel number. |
| Ambient Weather | sensor → radio → Wi-Fi console → Ambient Weather cloud → SensorConsole | live | Uses your Ambient Weather account's API and application keys. |
| Bresser | sensors → radio → Wi-Fi base station (WSLink app) → pushed directly to SensorConsole | beta | Uses the custom server option in Bresser's WSLink app. |
| PurpleAir | sensor with built-in Wi-Fi → PurpleAir cloud → SensorConsole | live | Uses a PurpleAir read API key and your sensor index. |
| AirGradient | monitor with built-in Wi-Fi → AirGradient cloud → SensorConsole | beta | Uses an API token enabled in your AirGradient dashboard. |
| Netatmo | indoor module → Wi-Fi → Netatmo cloud → SensorConsole | live | Uses a Netatmo developer app and refresh token. |
| Airthings | monitor with Wi-Fi (or Bluetooth via hub) → Airthings cloud → SensorConsole | live | Uses an Airthings API client from your Airthings dashboard. |
| Aranet | sensor → Bluetooth → Aranet base station → Aranet Cloud → SensorConsole | beta | Uses an API key from your Aranet Cloud account. |
| Govee | sensor → Wi-Fi (or Bluetooth gateway) → Govee cloud → SensorConsole | live | Uses a free Govee API key (for personal, non-commercial use). |
| SensorPush | sensor → Bluetooth → SensorPush G1 gateway → SensorPush cloud → SensorConsole | live | Needs a SensorPush Wi-Fi gateway so readings reach the cloud. |
| Crodeon | sensor → Reporter unit → cellular or Wi-Fi → Crodeon cloud → SensorConsole | beta | Uses your Crodeon API key plus reporter, sensor and channel IDs. |
| Monnit | sensor → wireless gateway → iMonnit cloud (paid plan) → SensorConsole | beta | Needs an iMonnit Premiere or Enterprise plan for API access. |
| Minut | sensor → Wi-Fi → Minut cloud → SensorConsole | beta | Uses developer credentials from your Minut account. |
| Flume | sensor on your water meter → Wi-Fi bridge → Flume cloud → SensorConsole | beta | Uses API credentials from your Flume account settings. |
| SolarEdge | inverter → SolarEdge monitoring cloud → SensorConsole | live | Uses an API key and site ID from the SolarEdge monitoring portal. |
| Shelly | device → Wi-Fi → Shelly Cloud → SensorConsole (or pushed directly) | beta | Uses your Shelly Cloud server address and authorization key. |
| Rachio | controller → Wi-Fi → Rachio cloud → SensorConsole | beta | Uses the API token from your Rachio web app account. |
Beta means the connection works but is newer than the rest. If a reading does not come through, email sensorconsole@protonmail.com.
Coming soon:
Metos — join the waitlist on the page to hear when it is ready.