v0.4.1

What's Changed

• New 1D Simstrat model support. Fallback for unsupported lakes
• Additional lakes supported.:
  ammersee, amsoldingersee, arendsee, attersee, baldegg, bannwaldsee, barchetsee, barone, bichelsee, bled, brenet, bret, bretaye, brienz, burgaschisee, burgseeli, cadagno, champfer, chavonnes, chiemsee, chlimoossee, como, dittligsee, egelsee, eibsee, faaker, fuschlsee, geistsee, gerzensee, grabensee, grosseralpsee, gruntensee, gruyere, hasenseeost, hasenseewest, hauptwilerweiher, hopfensee, hugiweiher, husemersee, huttnersee, huttwilersee, inkwilersee, irrsee, iseo, klontalersee, kochelsee, konigsee, lauerz, lenkerseeli, lioson, lobsigensee, lowerconstance, lowerlugano, lowerzurich, lucernealpnachersee, lucernegersauerandtreibbecken, lucernekreuztrichterandvitznauerbecken, lucerneurnersee, lungern, lutzelsee, maggiore, marwilermoos, mattsee, mauensee, mettmenhaslisee, millstaetter, mondsee, moossee, niedersonthofener, nussbommersee, obererbommerweiher, oberesbanzlauiseeli, obertrumer, oeschinensee, ossiacher, pfaffikon, poschiavo, riegsee, rotsee, sarnen, sassolo, schliersee, seehamer, seeweidsee, sempach, sihlsee, sils, silvaplana, simssee, soppensee, staffelsee, starnberger, steinsee, stockseewli, superiore, tachinger, tegernsee, thun, tome, traunsee, turlersee, uebeschisee, untererchatzensee, upperconstance, upperlugano, upperzurich, vagoweiher, walchensee, walensee, wallersee, weissensee, wilemersee, wistererweiher, wolfgangsee, worthsee, worthersee, zeller
• Alplakes brand logos and icons

Full Changelog: v0.3.0...v0.4.1

v0.4.1-alpha

v0.4.1-alpha.1.1

prepare v0.4.1-alpha

v0.3.0

What's Changed

• Added Home Assistant 2026 compatibility fixes for options flow setup and coordinator refresh timing.
• Added per-lake model selection, including Lucerne/Brunnen, Neuchatel, and Thun mappings.
• Improved config entry and entity IDs to distinguish measurement points by lake, location, coordinates, and depth.
• Added validation for latitude, longitude, depth, and scan interval.
• Added offline unit coverage for config flow, coordinator parsing, lake/model mapping, and test discovery.

Special thanks to @linuxlurak

Full Changelog: v0.2.2-alpha.1...v0.3.0

v0.2.0

Release Notes

Alpine Lake Temperature Integration

Highlights & Key Features

1. Configurable Lake Temperature Sensors

   • Add sensors for any supported Swiss lake and location.

2. Custom Location Name

   • Users can specify a custom, one-word location name for each sensor.

3. Unique ID Generation

   • Unique IDs for sensors now include both the lake and sanitized location name, plus depth.

4. Depth Handling

   • Accepts both integer and float values for depth, always stored as float.

5. Default Values

   • All configuration defaults to Lake Zurich, Männedorf, 47.255, 8.688, 0.1m.

6. Google Maps/LatLong.net Link

   • The config flow dialog includes a Markdown link to help users find coordinates.

7. German Translation

   • Full German translation available for the config flow UI.

8. Configurable Scan Interval

   • Users can set the update interval (in minutes) for each sensor.

9. Device Info

   • Each sensor exposes device info, including manufacturer and model.

10. Attribution

    • Attribution string included in all sensors: "Data provided by Alplakes / Eawag".

11. Robust Error Handling

    • Handles API errors, missing data, and connection issues gracefully.

12. Async Data Fetching

    • Uses Home Assistant's DataUpdateCoordinator for efficient async updates.

13. Test Coverage

    • Unit, integration, and e2e tests for config flow, coordinator, and sensor logic.

14. Type Checking

    • Enforced with mypy in CI; build fails on type errors.

15. Linting

    • Linting with flake8 in CI; build does not fail on lint errors.

16. Home Assistant 2025.4+ Compatibility

    • Integration requires and is tested against the latest Home Assistant versions.

17. HACS Support

    • Fully compatible with Home Assistant Community Store (HACS).

18. Easy Setup & Removal

    • Supports Home Assistant's config entry setup and removal flows.

19. Modern Python Practices

    • Uses type hints, async/await, and modern Home Assistant integration patterns.

20. Clear Documentation

    • README and in-app descriptions guide users through setup and usage.

---

Upgrade Notes:

• If upgrading from a previous version, review your sensor unique IDs and location names for compatibility.
• Ensure your Home Assistant version meets the minimum requirement.

Full Changelog: v0.1.0...v0.2.0