XTX Integration for Netatmo

Registro de alterações

1.9.12

• Added: [naws_windrose] — where the wind comes from, how often, and how hard: one ray per compass direction (16 or 8), its length the share of readings from there, stacked by Beaufort class from the centre outwards, calm in the hub. Below it the main directions, mean, peak and calm share, a legend, and a table for screen readers. Built from the raw ten-minute readings with one grouped query per period, cached as a transient. period (7d, 30d, 90d, year, all), from/to for a fixed range, measure (wind, gust, both), sectors, show, switcher, size, title. Every period of the switcher is rendered on the server; the script only swaps panels and dresses the tooltips. Seven colours on a new Appearance tab.
• Added: the “Wind & Gusts” card of [naws_live] shows the day’s strongest gust as a third value, in the configured wind unit, and the gauge gets a third, red needle for it.
• Fix: the compass directions are translated. The forecast in [naws_live] and [naws_forecast] showed a German visitor “ESE” where “OSO” belongs; the sixteen codes go through gettext now, in German and Norwegian.
• Fix: the frontend stylesheet and scripts carry the file’s modification time in their version, so a changed file is fetched even when the plugin version stays the same — the admin assets have done this since 1.9.7.
• Changed: this readme carries only the five most recent versions of the changelog; the full history since 1.0.0 lives in CHANGELOG.md on GitHub.

1.9.11

• Added: [naws_records] — fifteen records from the daily summary, each with its date: hottest day, coldest night, warmest night, coldest day, largest daily range, warmest and coldest month, wettest day and month, longest dry and wet spell, strongest gust, longest frost period, longest heat wave and longest run of summer days. As tiles or a table, since the first day with readings or for one year (year="2025"), a subset with records="…". A tie goes to the earlier date, a month needs twenty days to compete, and a gap in the data breaks a run rather than bridging it.
• Added: [naws_on_this_day] — this calendar day in every earlier year: low, high, mean and rain, newest year first, with the day’s record marked in each column. The running year is left out.
• Added: [naws_sunpath] — the sun on its arc over the station as an inline SVG: sunrise, solar noon and sunset, the part of the day already travelled, and the sun where it stands; at night below the horizon. Under it the day length, the change since yesterday and the year’s longest and shortest day at the station’s latitude. No script — a page cache shows the sun where it stood when the cache was filled.
• Added: a colour scheme for the sidebar widget. [naws_weather_widget] was a white card whatever the sidebar looked like. It now has light, dark and transparent — the last draws no card at all and takes the sidebar’s own colours. Chosen under Appearance → Sidebar widget, where the preview shows it on a dark ground, or per placement with scheme="dark".
• Fix: the purge button under Settings → Manual Data Purge did nothing, and every admin page of the plugin threw “$ is not a function”. Since 1.6.4 two handlers in admin.js stood behind the line that closes the jQuery block. The purge button works again, and its messages are translated instead of German literals in the script.
• Fix: the bundled catalogue builder now writes plural forms, so “1 day / 2 days” reads right in German and Norwegian. Both bundled catalogues are complete at 735 strings.

1.9.10

• Added: [naws_heatmap] — a year of outdoor daily mean temperatures as a calendar grid: twelve rows of months, thirty-one columns of days, one coloured tile per day, and a row of buttons to page through the years. What a curve makes you read, a grid lets you see: the cold fortnight in February and the hot week in July are shapes on the page rather than wiggles on a line. It reads the daily averages the annual chart already uses, so there is nothing to import. The ten colour stops are settings under Appearance → Heatmap Scale, values between two stops are interpolated, and they are anchored in Celsius even when the display is set to Fahrenheit, because the colour comes from the stored value and the tooltip from the unit you chose. Where a day has no stored average but does have a minimum and a maximum, the tile shows the mean of the two and its tooltip says so. The grid is a table rather than a drawing: the month column stays put while the days scroll sideways on a phone, colours are rendered on the server so the map is complete without JavaScript, and a screen reader reads “March, 14th, 8.2 °C” instead of “image”. Attributes: year, title, legend.
• Changed: the MAC addresses of your modules are no longer written into public pages. A module id in this plugin is the hardware address of a Netatmo module, and until now it travelled into every page carrying [naws_live] or [naws_history] — in the data block, on every chart configuration, in the data-module4, data-indoor and data-outdoor attributes — and it came back out with every request the dashboard made, whose reply carried the base station’s address on every one of its thirty-odd readings as well. What travels now is a public reference: outdoor, indoor, wind, rain and in-<name>, resolved back on the server. Pages cached from before the update and the documented NAWS_Chart JavaScript interface both keep working.
• Fix: the two language files 1.9.9 shipped were never read. German and Norwegian travelled along as .mo files so that an installation with a German interface would not find an English one the day the update arrived — but WordPress refused both, because the address of the hash table in the file header was wrong. A refused catalogue produces no warning, no log line and no visible difference except that everything stays English. Norwegian, which has no language pack yet, therefore read English throughout 1.9.9.
• Fix: fourteen German and thirteen Norwegian strings had lost their translation in 1.9.9. The table columns from 1.9.8 — time, module, parameter, average — and the card-order screen came through the migration empty, so a German reader without a language pack saw English column headings in a German interface. The texts were taken from the 1.9.8 language files rather than written afresh, so nothing changed wording that a reader had already got used to.
• Fix: three sentences in the chart script were German whatever language WordPress was set to — the chart that failed to render, the period with no readings, the request that came back with an error code. They sat in the JavaScript as literals, which the move to gettext in 1.9.9 never reached.
• Fix: [naws_table] printed a MAC address in its module column when the reading’s module was no longer in the modules table. Readings outlive the module they came from, so this was reachable rather than theoretical. The cell stays empty now, the way the chart legend does.
• Fix: a chart request that left out group_by wrote a PHP notice into the log. The plugin’s own scripts always send it; anything else calling the endpoint did not have to.

1.9.9

• Changed: breaking — the plugin no longer has its own language setting; the WordPress locale decides. The old setting was a single site-wide value for the front end and the back end at once, and it read the site language rather than your own, so it could never give you a back end in one language and your visitors another. Site Language plus the per-user Language in your profile do exactly that, and for your theme and every other plugin at the same time. If you had the plugin set to a language other than your site’s, set the site language instead — or your own user language, if you meant only your own screen.
• Changed: the interface translates through WordPress now instead of through the plugin’s own language files. Until now translate.wordpress.org saw six strings of this plugin; it sees all 649. That means anyone can contribute a language without touching the code, and every language gets a proper WordPress language pack.
• Changed: weekday, month and weather-condition names are translatable. They used to be two hardcoded lists, German and English, so a Norwegian reader got English with no way to change it.
• New: German and Norwegian ship with this release as a bridge. Language packs do not exist the moment an update goes out, and an installation that had a German interface yesterday should not find an English one today. A pack always takes precedence once it is built.

1.9.8

• Fix: [naws_table] produced nothing at all. The shortcode was registered, documented in the reference and listed in this readme, and its stylesheet was written — but the template it includes, templates/table.php, had never been committed. Every use of the shortcode output an empty string and left two PHP warnings in the log. The template is there now, and a test fails if it goes missing again.
• Fix: [naws_table] listed the bookkeeping values Netatmo stores alongside the readings. max_wind_angle and max_wind_str have neither a name nor a unit in the plugin, so they appeared as a raw key next to a bare number. The table now asks only for parameters it can present; naming one explicitly in parameters still returns it. The daily minimum and maximum temperature and the hourly rain total were in the same position for the opposite reason — they are meaningful and were simply unnamed, so they have their labels now instead of being hidden.
• Fix: [naws_table] found nothing for the periods its own reference recommends. period="24h" asked for a range that starts tomorrow — PHP does not read 24h as a duration, and strtotime('-24h') returns a point in the future rather than yesterday. 365d failed to parse altogether. The start of the range therefore sat behind its end and the query returned nothing, which looked exactly like a station with no readings. The shorthand is spelled out before it reaches the parser now, and a period that cannot be read falls back to the documented 24 hours instead of to 1970.
• Fix: the reference gave the grouping of [naws_table] as hour, day, week or month. year works as well, and any other value lists single readings instead of averages. The readme named four of the shortcode’s six attributes.
• Fix: a database change would never have reached anyone who updates through WordPress. The routine that creates and migrates the tables hung on the activation hook alone, and WordPress does not fire that when it updates a plugin — it reactivates it silently. Nobody was hurt by it yet, because until 1.9.7 the plugin was installed by hand and activated in the process; since the directory listing, the update button is the normal way, and that is exactly the path that skipped it. The plugin now compares the stored schema version on every load and migrates when they differ.
• Changed: Plugin URI in the plugin header points at the plugin’s own page, netatmo.frank-neumann.de, instead of at a weather page that carries a section about it. That is what the “Visit plugin site” link in your plugins list opens.

Older versions: the complete changelog since 1.0.0 is kept in CHANGELOG.md on GitHub.