Use UTC datetimes internally

What's Changed

• Python datetime object comparisons and math don't work as expected when the objects are aware and have the same tzinfo attribute. Basically, the fold attribute is ignored in this case, which can lead to wrong results. Avoid this problem by using aware times in UTC internally. Only use local time zone for user visible attributes.

Full Changelog: 5.6.0...5.6.1

Don't require attribution attribute

What's Changed

• Some weather entities don't have an attribution attribute, so don't require it. If it's not present and the entity's state is not a number (or if the entity hasn't been fully initialized by the time HA completes initialization), just default to using the standard condition-to-divisor mapping.
• When the above happens, write an appropriate message to the system log, but make it a DEBUG message to avoid annoying WARNING or ERROR messages when using a weather entity that does not have an attribution attribute.

Full Changelog: 5.5.0...5.6.0

Make weather entity optional & add irradiance mode option

What's Changed

• Make weather entity optional & add irradiance mode option by @pnbruckner in #69
  • Make weather entity optional.
  • Fallback default is 1 if no weather entity selected, or 10 when one is selected (as before.)
  • Add irradiance mode option.
  • Fix scan interval broken by HA 2024.6.
• The astral package uses pytz which does file I/O when it sees a new time zone. Force this file I/O to happen in an executor.

Full Changelog: 5.4.3...5.5.0

Clamp cloud coverage values to 0 - 100 without logging error

What's Changed

• Clamp cloud coverage values to 0 - 100 without logging error by @pnbruckner in #66

Some weather entities apparently provide cloud coverage percentages above 100%, resulting in lots of Illuminance errors. This change forces cloud coverage percentage values to be between 0 & 100, inclusive.

Full Changelog: 5.4.2...5.4.3

Avoid reloading config when not in correct state

First noticed in 2024.3.0b1, either something unexpected changed, or timing has changed, because a config entry reload that worked ok before is now running while the config entry is still being set up. This change prevents reloads from being started when the config is not in the correct state.

Fix for frozen EntityDescription, again

Custom integrations are supposed to make classes derived from EntityDescription frozen. This works in 2024.1, but not in earlier releases. This fix should work for both.

Change minimum scan_interval to 0.5 minutes

• Change minimum scan_interval to 0.5 minutes (i.e., 30 seconds.)
• Change step in corresponding config flow entry to 0.5 minutes.
• Fix for frozen EntityDescription in HA 2024.1.

Provide Italian translation

5.3.0

Bump version to 5.3.0

Provide Polish translation

5.2.0

Bump version to 5.2.0

Provide Swedish translation

5.1.0

Bump version to 5.1.0