XTX Integration for Netatmo

Description

XTX Integration for Netatmo connects your Netatmo hardware to WordPress. It reads all sensor data via the official Netatmo API, stores readings in your local database and displays them with beautiful live dashboards, animated charts and weather forecasts.

Key Features

• Full Netatmo Integration – OAuth2 authentication, automatic sync, all module types supported (Base, Outdoor, Wind, Rain, Indoor)
• Live Dashboard – Real-time sensor cards with animated counters, 24h trend charts, pressure trend indicator, wind compass, CO2 air quality levels
• Astronomy – Sunrise/sunset, moon phase with illumination, next full moon
• Derived Weather Data – Feels-like temperature, heat index, dew point, wind chill
• Historical Charts – Year-over-year comparison for temperature, pressure and rainfall with interactive legend
• Weather Forecast – 5-day forecast based on station coordinates via Open-Meteo or Yr.no
• REST API – Read-only JSON API with key authentication and rate limiting for external tools (Google Charts, Grafana, etc.)
• Encrypted Storage – All credentials (OAuth tokens, client secret, API keys) are AES-256-GCM encrypted at rest
• Configurable Units – C/F, mm/inch, mbar/inHg/mmHg, km/h/m/s/mph/kn
• Multilingual – Full German, English and Norwegian interface
• 18 Shortcodes – Dashboard, current readings, infobar, single value, computed value, sparkline, sparkline tiles, history charts, heatmap, records, this day in earlier years, sun path, wind rose, forecast, rain radar, table, widget, weather icon
• Export / Import – Full backup and restore of weather data, modules and settings
• E-Mail Notifications – battery, radio and Wi-Fi, station offline, failed syncs, frost, heat, gusts, rain, rain starting, CO₂; per-rule thresholds, one mail per state change and an all-clear when the state ends, and a master switch
• Mobile-First Responsive – All views optimized for smartphones, tablets and desktops
• 130+ Configurable Colors – Full appearance customization with live preview
• 4 Icon Sets – Emoji, Outline, Filled, Minimal with per-sensor color control

Supported Modules

• NAMain – Base Station (Temperature, Humidity, CO2, Noise, Pressure)
• NAModule1 – Outdoor (Temperature, Humidity)
• NAModule2 – Wind (Speed, Direction, Gusts)
• NAModule3 – Rain Gauge (Hourly, Daily, Rolling 24h)
• NAModule4 – Additional Indoor (Temperature, Humidity, CO2)

Shortcodes

• [naws_live] – Live sensor tiles with 24h trend charts and wind rose
• [naws_current] – Current readings of one or all modules as tiles or a list (module_id, parameters, layout, title)
• [naws_infobar] – Astronomy bar with sunrise, moon phase, felt temperature
• [naws_value] – Single inline sensor value
• [naws_calc] – Single computed value (dew point, felt temperature, sunrise, moon phase, …); full list on the Shortcodes page in the backend
• [naws_history] – Year-over-year comparison charts (supports year parameter)
• [naws_heatmap] – One year of outdoor daily average temperature as a calendar grid, one tile per day, with a year selector (year, title, legend)
• [naws_records] – Fifteen records from the daily summary with their dates, as tiles or a table (year, records, layout, title)
• [naws_on_this_day] – This calendar day in every earlier year, with the day’s records marked (date, title)
• [naws_sunpath] – The sun on its arc over the station, with sunrise, solar noon, sunset and the day length (title)
• [naws_windrose] – Where the wind comes from and how hard, as a rose of 16 or 8 directions stacked by Beaufort class, with a period switcher (period, from, to, measure, sectors, show, switcher, size, title)
• [naws_sparkline] – A curve the size of a word: the raw readings of the last hours or a column of the daily summary, rain as bars, the band between daily low and high, time and value on hover; as a card or a month block too (param, hours, days, module, width, height, show, type, band, layout, title)
• [naws_sparkline_tiles] – The sparkline cards side by side in a grid that wraps by itself: temperature, humidity, pressure, wind, rain and CO2 by default (params, hours)
• [naws_forecast] – Multi-day weather forecast
• [naws_radar] – Animated rain radar around the station: Deutscher Wetterdienst in Germany (last hour plus two-hour nowcast), RainViewer elsewhere, on a grey OpenStreetMap map. Images are fetched by your server and served from your site (width, height, km, source). Must be switched on under Settings → Rain radar.
• [naws_table] – Readings as a table over a period, grouped by hour, day, week, month or year (module_id, parameters, period, limit, group_by, title)
• [naws_weather_widget] – Compact forecast widget for a sidebar (days 3 or 5, width 250–500, scheme light, dark or transparent, sparklines 0 or 1)
• [naws_weather_icon] – Just the animated icon for the current weather state (size); renders nothing when the state is unknown

Privacy & External Services

This plugin connects to the following external services:

Netatmo API (api.netatmo.com)

• Purpose: Authenticate via OAuth2, fetch sensor readings and station data
• Data sent: The Client ID and Client Secret of the Netatmo application you created, in exchange for an access token; afterwards the access or refresh token with every request, plus the station and module IDs whose measurements are being requested
• When: During initial authentication, on every automatic sync cycle, on every token refresh, and while a historical import is running
• Terms of service: https://dev.netatmo.com/legal
• Privacy policy: https://legals.netatmo.com/?goto=privacy

Open-Meteo API (api.open-meteo.com)

• Purpose: Fetch weather forecast data based on station coordinates (default provider)
• Data sent: Latitude and longitude of your weather station
• When: When the forecast shortcode is displayed (cached for 3 hours)
• Terms and privacy: https://open-meteo.com/en/terms
• Note: Open-Meteo is a free, open-source weather API. No API key or registration required.

Open-Meteo Geocoding API (geocoding-api.open-meteo.com)

• Purpose: Turn a place into coordinates, and coordinates into a place name for the forecast heading
• Data sent: In «manual» location mode, the city name or postal code entered in the plugin settings. In «automatic» mode, the latitude and longitude of your weather station, rounded to two decimal places, in order to look up the name of the nearest place.
• When: In manual mode whenever no cached result exists (cached for 7 days). In automatic mode exactly once — the resolved name is stored in the plugin settings and never looked up again.
• Terms and privacy: https://open-meteo.com/en/terms
• Documentation: https://open-meteo.com/en/docs/geocoding-api

Yr.no / MET Norway API (api.met.no)

• Purpose: Fetch weather forecast data (optional provider, selectable in settings)
• Data sent: Latitude and longitude of your weather station
• When: When the forecast shortcode is displayed and Yr.no is selected as provider (cached for 3 hours)
• Privacy policy: https://www.met.no/en/About-us/privacy
• Terms: https://developer.yr.no/doc/TermsOfService/
• Note: Free API, no API key needed. MET Norway’s terms require every client to identify itself, so requests to this service carry a User-Agent naming the plugin, its version and your site address — that address is how MET Norway would reach you before restricting a misbehaving client. This is sent to api.met.no only, and only while Yr.no is the selected provider.

Deutscher Wetterdienst (maps.dwd.de)

• Purpose: Radar images (measured and two-hour nowcast) for the rain radar [naws_radar] when the station is in Germany
• Data sent: The map section around your station (as a bounding box) and the time of each image. No visitor data: your server fetches the images and your site serves them.
• When: Only if «Allow rain radar» is on, after a page showed the radar, at most every 15 minutes
• Terms and privacy: https://www.dwd.de/EN/service/copyright/copyright_node.html, https://www.dwd.de/EN/service/dataprotection/dataprotection_node.html

RainViewer (api.rainviewer.com, tilecache.rainviewer.com)

• Purpose: Radar images for the rain radar [naws_radar] outside Germany
• Data sent: The tile numbers of the map section around your station and the time of each image. No visitor data: your server fetches the images and your site serves them.
• When: Only if «Allow rain radar» is on, after a page showed the radar, at most every 15 minutes
• Terms and privacy: https://www.rainviewer.com/terms.html, https://www.rainviewer.com/privacy.html

OpenStreetMap tiles (tile.openstreetmap.org)

• Purpose: The background map of the rain radar [naws_radar]
• Data sent: The tile numbers of the map section around your station. Fetched once per map section and kept on your server.
• When: Only if «Allow rain radar» is on, the first time a page shows a radar with that map section
• Terms and privacy: https://operations.osmfoundation.org/policies/tiles/, https://osmfoundation.org/wiki/Privacy_Policy

No personal user data (names, emails, IP addresses) is collected or transmitted by this plugin. All sensor data is stored exclusively in your local WordPress database.

Third-Party Libraries

Two JavaScript libraries are bundled with this plugin, both under the MIT license, which is GPL-compatible. They ship in their minified distribution builds; the unminified source and the build tooling for each are available at the links below.

Chart.js 4.5.1

• File: assets/vendor/chart.umd.min.js
• License: MIT
• Homepage: https://www.chartjs.org
• Source and build tools: https://github.com/chartjs/Chart.js — the exact release bundled here is v4.5.1
• Used for: All charts — 24h trend lines on the live dashboard and the year-over-year history charts

chartjs-adapter-date-fns 3.0.0

• File: assets/vendor/chartjs-adapter-date-fns.bundle.min.js
• License: MIT
• Source and build tools: https://github.com/chartjs/chartjs-adapter-date-fns — the exact release bundled here is v3.0.0
• Used for: Time axis formatting in the charts. This is the bundled build, which includes date-fns (also MIT).

No other third-party code is included. No library is loaded from a CDN; everything is served from your own installation. Libraries that ship with WordPress itself are used from WordPress and are not bundled.