Neues Widget - Gezeiten

Damien · 23. August 2026 um 22:17

Bravo! Exzellente Idee!

Zum Abschluss des Themas Wetter, wie wäre es mit einem nächsten über die Gezeiten?

Will_71 · 23. August 2026 um 22:28

Warum nicht, ich notiere es. Zögere nicht, einen spezifischen Antrag zu erstellen.

Will_71 · 27. August 2026 um 11:31

@Damien, Hier ist mein Vorschlag

Will_71 · 27. August 2026 um 21:59

Hier ist der PR

github.com/GladysAssistant/Gladys

Dashboard: add a tide widget for harbours worldwide (#3028)

master ← William-De71:feat/tide-widget

ouvert 09:59PM - 27 Aug 26 UTC

William-De71

+2718 -0

What this does Adds a tide dashboard widget showing the tides of a house by t…he sea: a harbour tide clock, the next high and low water, the water level right now, and the curve of the day annotated with each tide. A row of tabs steps through the week ahead, one day at a time. On the French coast it also shows the tide coefficient. How tides are computed Tides are predicted locally. The harmonic constituents of the tide station closest to the house are downloaded once from the Open Waters tide database (MIT code, CC-BY-4.0 data, built from the NOAA and TICON-4 datasets) and stored in a per-house variable. Every prediction afterwards is computed offline: the widget keeps working with no network access, and a station that can no longer be downloaded is kept rather than dropped. Predictions were checked against the tide tables published by the SHOM for Concarneau: times land within 1 to 4 minutes, heights within about 20 cm. Places with no tide to show A house inland matches a harbour hundreds of kilometres away, and the Mediterranean or the Baltic move by a few centimetres. Rather than drawing a flat curve, the widget says which of the two it is — the cases are told apart by the distance to the station and by the spring range, and worded differently. A third case says the tide could not be retrieved at all: failing to reach the station database says nothing about where the house is, so a seaside house is never told it is inland because the network was down. The tide coefficient On the French coast the widget shows the tide coefficient, computed on the semi-diurnal constituents alone, the way the SHOM publishes it. Keeping the diurnal ones makes the morning and the evening tide of a same day differ by ten points, which published coefficients never do. Brest harmonics are embedded, so the coefficient needs no second download. New dependency @neaps/tide-predictor (MIT, ~217 KB unpacked, no transitive dependencies). It is an ES module while the server is CommonJS, so it is loaded through a memoized dynamic import() in server/lib/house/house.getTideState.js — the only dynamic import() in the server, which is why docs/specs/tide-widget.md explains it. Reimplementing it would be wrong rather than merely tedious: harmonic prediction needs the astronomical equilibrium arguments and the nodal corrections following the 18.6-year lunar cycle. A naive sum of cosines written with the real Saint-Malo constituents lands 2.4 to 6.2 m off across four dates spread over a year (table in the spec). There is no CommonJS equivalent on npm. The dynamic import() is safe here: production installs run npm ci --production with no bundler, Node 24 supports it natively, and tests cover it including the offline path. API One new route: GET /api/v1/house/:house_selector/tide Returns the tide state of the house: the tides framing the current moment, the water level, the curve of the day, and the coefficient where it applies. ?day_offset= selects a day within the week ahead. Returns 400 when the house has no coordinates. ## Forum Forum: https://community.gladysassistant.com/t/nouveau-widget-marees/10714 ### Checklist - [x] Tests pass: `cd server && npm run coverage` (Codecov requires 100% coverage on changed lines) and Cypress (`npm run cypress:run`) if the UI changed - [x] Linter and prettier pass on both front and server (`npm run eslint`, `npm run prettier`) - [x] No undocumented breaking change <img width="1355" height="489" alt="image" src="https://github.com/user-attachments/assets/f79d1b53-d954-4f88-af45-22203c1993c1" /> ## Summary by CodeRabbit * **New Features** * Added a Tides dashboard widget with weekly forecasts, tide curves, current levels, high/low tides, and coefficients. * Added house selection and an option to show or hide the tide curve. * Added automatic station caching and refresh for tide forecasts. * Added clear messages for unavailable, unsupported, or negligible tides. * Added English, French, and German translations, plus demo data support. * **Documentation** * Added documentation covering tide predictions, attribution, validation, and supported scenarios.

cursor-bot · 29. Oktober 2026 um 10:49

Hallo @Damien!

Die Gezeiten haben eine externe Integration: Marées France (William-De71, v0.2.0).

Hochwasser, Niedrigwasser, Koeffizienten, ein Dashboard-Widget und Werte, die in einer Szene verwendet werden können.

Integrationen → « Gezeiten ». Du wählst den Hafen in der Konfiguration aus.

Ich verschiebe dieses Thema in « Erledigte Anfragen ». Falls noch ein Fall nicht passt, erstelle ein neues Thema: Das wird einfacher zu verfolgen sein.

Thema		Antworten	Aufrufe
Nouveau widget phase de la lune Développement dashboard	1	92	11. Oktober 2026
Intégrations externes : Pouvoir créer des intégrations de type "météo" Demandes livrées in-progress , feature-core	3	109	7. August 2026
Intégration externe - Vigicrues (vigilance crues et hauteur des rivières) Développement integration-externe	6	108	15. Oktober 2026
Permettre aux intégrations de déclarer leurs propres widgets de dashboard (schéma JSON) Demandes livrées in-progress	12	263	20. September 2026
[Intégration externe] Phase de la lune 🌙 Développement integration-externe	1	52	13. Oktober 2026

Neues Widget - Gezeiten

Verwandte Themen