-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Weerlive API v2 #120
Conversation
Release Notes (Draft)Before proceeding with the update, please review the comprehensive release notes, as there are breaking changes. Version 2.0.0Exciting news! Version 2.0.0 is here, featuring a collaboration with Weerlive, unleashing a new API with enhanced capabilities for all users. Thank you, Martijn! New features:
Breaking changes:To align with the latest developments:
New entities:In response to user feedback and the deprecation of the forecast attributes in HA, several new entities have been introduced. Most of these sensors are not enabled by default, allowing you to choose the ones you find valuable. The amount of sensors enabled doesn't impact the API limits. Binary sensors
SensorsNormal sensors:
Diagnostic sensors:
WeatherThe weather entity contains all the weather information, ideal for displaying a comprehensive overview in the Home Assistant frontend. It includes both a daily forecast spanning up to 5 days and an hourly forecast covering up to 24 hours. Daily forecast attributes:
Hourly forecast attributes:
Thank you for your continued support and feedback! |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #120 +/- ##
==========================================
+ Coverage 95.58% 96.32% +0.74%
==========================================
Files 9 9
Lines 362 354 -8
==========================================
- Hits 346 341 -5
+ Misses 16 13 -3 ☔ View full report in Codecov by Sentry. |
This is really interesting thanks for taking the effort to migrate the APIs. Would it be possible to make a pre-release out of this? That makes it easier to test the changes using HACS. |
Thanks, yes will make a pre-release later today |
Works fine so far, and thanks for the seperate sensors - it simplifies my code big time. Q: did |
Working as expected here for the past few days. I like the additional sensors and forecasts. q: Is there a way to get wind direction forecast? I was able to extract a separate sensor for the current wind direction, but would be great to get more wind direction details if possible. |
This value is now in the sensor with the name Weather forecast/Weersverwachting |
I think this is too specific, for this, I would suggest to use the |
Quality Gate passedIssues Measures |
If you are willing to test out this update, I would really appreciate your feedback!
See the draft release notes in my comment below, and the updated README.md as there are some breaking changes.
Please answer the following questions:
see en.json and nl.json, please comment in the pull request files section to keep it organized
Tasks list:
value_fn
andattr_fn
instead of subclassing = less codeasync_migrate_entry
Known bugs:
wrsch_g
) and timestamp (wrsch_gts
) format from the API are inconsistent, ifwrsch_gts
becomes anint
, no action is requited.