Skip to content

Releases: decompil3d/lovelace-hourly-weather

4.2.4

09 Aug 23:02
Compare
Choose a tag to compare

What's Changed

Fixes

  • Wait to render templates until hass object is available by @decompil3d in #95

Dependencies

Full Changelog: 4.2.3...4.2.4

4.2.3

03 Aug 17:32
Compare
Choose a tag to compare

What's Changed

Oops, 4.2.2 didn't totally fix the locale undefined issue. But this one should. Sorry about the false start.

Full Changelog: 4.2.2...4.2.3

4.2.2

03 Aug 17:23
Compare
Choose a tag to compare

What's Changed

Fixes

Dependencies

  • Bump eslint from 8.20.0 to 8.21.0 by @dependabot in #79
  • Bump @babel/plugin-proposal-decorators from 7.18.9 to 7.18.10 by @dependabot in #81
  • Bump @babel/core from 7.18.9 to 7.18.10 by @dependabot in #84
  • Bump @typescript-eslint/eslint-plugin from 5.31.0 to 5.32.0 by @dependabot in #82
  • Bump @typescript-eslint/parser from 5.31.0 to 5.32.0 by @dependabot in #83

Full Changelog: 4.2.1...4.2.2

4.2.1

02 Aug 21:12
Compare
Choose a tag to compare

What's Changed

Enhancements

  • Attempt to use HA server language if no user language set by @decompil3d in #85
  • Add machine-generated Dutch translation 🇳🇱

Code quality

Dependencies

Full Changelog: 4.2.0...4.2.1

4.2.0

19 Jul 21:45
Compare
Choose a tag to compare

What's Changed

New features

Dependencies

Full Changelog: 4.1.0...4.2.0

4.1.0

15 Jul 20:14
Compare
Choose a tag to compare

What's Changed

Full Changelog: 4.0.0...4.1.0

4.0.0

14 Jul 21:48
Compare
Choose a tag to compare

What's Changed

In version 3.1.0, I tried to address some feedback around the num_hours configuration option by attempting to make the card more aware of the number of hours per forecast segment in the entity data. This was foolish. As was brought to my attention in #60, there are forecast entities that provide weather in sub-hourly segments as well. Making the code handle this as well was going to make things overly complex and bug-prone.

As such, I've decided to essentially revert the change in 3.1.0 and, instead, rename the configuration option to num_segments. This clarifies that you are choosing how may forecast segments to show -- whether those represent 1 hour, 3 hours, 15 minutes, or whatever.

This is a breaking change of sorts, since you may have your card setup to show 12 hours of data from an "every 3 hours" entity, for example. With this change, you'll now see 12 three-hour segments instead. I'm sorry. Luckily, it's easy to address. If you update the num_segments option in the UI card editor, it will automatically remove your num_hours configuration and replace it with a num_segments one instead.

Here's hoping this makes things easier for us all. Enjoy the card, and keep the feedback coming 😄

Full Changelog: 3.3.0...4.0.0

3.3.0

14 Jul 20:05
Compare
Choose a tag to compare

What's Changed

Full Changelog: 3.2.0...3.3.0

3.2.0

13 Jul 21:53
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 3.1.0...3.2.0

3.1.0

12 Jul 23:00
Compare
Choose a tag to compare

What's Changed

  • Handle entities with coarser hours per segment better by @decompil3d in #56

Full Changelog: 3.0.0...3.1.0