Skip to content
This repository has been archived by the owner on Dec 29, 2024. It is now read-only.

Releases: briis/weatherbit

Version 0.12

03 Jun 06:06
Compare
Choose a tag to compare

Release 0.12

  • Weather Entity now reports datetime as UTC Date time in RFC 3339 format, which is what the Lovelace Weathercard expects.
  • Sensor Entity now reports datetime as Location aware Date time in RFC 3339 format.
  • Bumped weatherpypi to 0.13

Version 0.11

01 Jun 05:51
Compare
Choose a tag to compare

Release 0.11

  • Changed Imperial Wind Unit from mi/h to mph
  • Fixed Rain value not displaying correctly when Imperial units
  • Changed Forecast for Weather and Sensor to start with Current Day.

Version 0.10

29 May 14:37
Compare
Choose a tag to compare

Update Intervals can now be specified

With this release you can now specify update intervals for both Current Data and for Forecast data. For Current Data there is range between 4 and 60 minutes for updates and for forecast Data it is between 30 and 120 min.

The reason for the 4 minutes on the Current Data, is that if you go below that, there is a very high probability that you will exceed your daily limit of 500 requests.

You can update from V0.9 without problems, but you will have to remove and re-add the Integration to specify the update intervals. That should not break your current setup.

Remember to restart Home Assistant after the upgrade.

Version 0.9

29 May 04:05
866e874
Compare
Choose a tag to compare

Introducing Sensors

BREAKING If you upgrade a current installation, you must remove the current Integration first (Go to the Integration Page, click the 3 dots in bottom right, and select delete), restart Home Assistant, and then add the Integration again. Failure to do so, will result in an error during setup of the Integration.

This release adds current weather data and forecast for 7 days, as sensors. This is very similar to the way DarkSky is able to show both a Weather Card and individual sensors. This is the first release of the sensors so let me know if it is working and they give valuable information.

For individuals who do NOT want the sensors added to Home Assistant, you are given the option during setup, to not install sensors. If you later decide you want the sensors, you will need to remove the Integration, and set it up again.

Beside the sensors, there are no visible changes, but I had to rewrite the whole data handling engine to make it possible to get the sensor data, without adding extra calls to Weatherbit. My own tests reveal no issues, and I assume this will apply to everyone.

Version 0.8

29 May 03:18
Compare
Choose a tag to compare

Introducing Sensors

This release adds current weather data and forecast for 7 days, as sensors. This is very similar to the way DarkSky is able to show both a Weather Card and individual sensors. This is the first release of the sensors so let me know if it is working and they give valuable information.

Beside the sensors, there are no visible changes, but I had to rewrite the whole data handling engine to make it possible to get the sensor data, without adding extra calls to Weatherbit. My own tests reveal no issues, and I assume this will apply to everyone.

Version 0.7

28 May 18:12
Compare
Choose a tag to compare
Version 0.7 Pre-release
Pre-release

Introducing Sensors

This release adds current weather data and forecast for 7 days, as sensors. This is very similar to the way DarkSky is able to show both a Weather Card and individual sensors. This is the first release so let me know if it is working and they give valuable information.

Beside the sensors, there are no visible changes, but I had to rewrite the whole data handling engine to make it possible to get the sensor data, without adding extra calls to Weatherbit.

BREAKING Due to the rewrite of the data engine the weather Component will change name and remove the weather_ from the entity_id. Sorry for any inconvenience.

Version 0.6

25 May 09:28
Compare
Choose a tag to compare
  • BREAKING You might see that the entity has changed name, and is no longer shown correctly. If that is the case, just remove the Integration and add it back again.
  • Night and Day symbols did not change correctly in all cases. Implemented a new function to check for timezone for the Latitude and Longitude. Please note that there is 30 min between each update, so the change of the symbol might have a delay in relation to local sunset and sunrise.

Version 0.5

18 May 07:36
Compare
Choose a tag to compare

This release contains the following changes:

  • The weather symbol for a clear night should now display correctly, instead of displaying a sun
  • Added a few extra attributes to both the current status and to each forecast day
  • Fixed conversion of values for both Metric and Imperial
  • Bumped weatherbitpypi to V0.7

Version 0.4

15 May 08:44
Compare
Choose a tag to compare
  • Rewritten Config Flow, so that naming of the Entity is pulled from the Latitude and Longitude coordinates
  • Bumped weatherbitpypi to 0.5

Version 0.3

13 May 09:35
Compare
Choose a tag to compare

Fixed API check in Config Flow