One weather entity to rule them all

TheFes · August 1, 2025, 4:35pm

I’m currently on holiday, I will have a closer look at the twice daily forecasts when I’m back

TheFes · August 4, 2025, 10:11am

Can you show me the result of this in devtools > actions

action: weather.get_forecasts
data:
  type: twice_daily
target:
  entity_id: weather.kteb

dovy6 · August 4, 2025, 4:13pm

I’m seeing some errors in vscode “Property weather is not allowed” “Property actions is not allowed” "Property triggers is not allowed.

It seems to be working fine, and under Developer Tools no errors are showing. Anything to be worried about?

TheFes · August 7, 2025, 4:49am

No, nothing to worry about. This is just the HA config checker extension in VSCode not being up to date with all recent changes in the template integration.

TheFes · August 8, 2025, 10:51am

@mynolix1986
I fixed the issue in the new version I’ve put online now.
Note that I also changed how the weight is provided, it is now a list instead of a dictionary. I did this in preparation to create a template blueprint for this template weather.

Update

BREAKING

weight is now provided as a list with dictionaries, instead of a named dictionary. This is in preparation of creating a template blueprint for the combined weather. It makes it easier to provide GUI support when this is released for template blueprints.

IMPROVEMENTS

A twice_daily forecast will now be created based on the hourly forecast in case there are no weather integrations which provide it

BUG FIXES

twice_daily forecasts were not created correctly (the required is_daytime forecast attribute was not provided). This has now been fixed, so if you have a weather integration providing a twice_daily forecast, it will now also be visible (and combined with others).

TheFes · August 15, 2025, 8:11am

Update

IMPROVEMENTS

Changed the trigger to trigger every 5 minutes instead of every hour. When the trigger is on every hour, the current values (like current temperature and humidity) are also only updated hourly, which means they are lagging behind.
Moved the calculation of the current attributes (like current temperature and humidity) to the action section to reduce duplicate code

BUG FIXES

fixed several cases where I didn’t properly use the new format to provide weights.

Zenia · August 15, 2025, 12:38pm

Thank you for great , reliable add on to our HA. I have 2 questions
1- How to update existing YAML file ? Just copy and paste entire file from your github page or some portions need to be updated?
2- When you will post template blueprint for combined forecast, what we have o do?
Download blueprint and it will update existing one, or we have to remove old files and start using blueprint?
Thank you in advanced . I think blueprint is a brilliant idea , specially for people who is not comfortable to modify YAML code.

TheFes · August 15, 2025, 1:03pm

Updating the current version would indeed mean replacing the current file with the new one.
But if you’ve set weight you need to make sure it’s adjusted to the new format, and added in the right spot in the code.

Regarding the blueprint there is currently no support for the GUI yet, so also there changes in the settings (like weight or the unit of measurements) need to be done in YAML. However, the underlying code for the calculations can be updated independently of the settings.

I have the bleuprint ready, but I’m not mentioning it yet because:

changes to template blueprints are expected regarding how unique id’s are set, which might make it that the current version needs adjustments which break it for already installed setups
currently only one template entity can be created using a blueprint, which will make the current setup with the additional sensors impossible. Also this is something that might change in the future
there is no GUI support yet, which gives it not much additional benefit over the current setup

However, if you really want you can import the blueprint here

A full example how to then use it can be found here

Important:

this will only create the template weather, not the additional sensors
this might break in the future

dovy6 · August 17, 2025, 6:28pm

It appears to have reached 187 degrees here!

I’ve added 4 weather entities to the template, each of which are reporting temperatures between 85 and 90 degrees. Not sure why, but my combined sensor is reporting 187. Anyone else having a similar issue?

TheFes · August 17, 2025, 6:59pm

@dovy6 Are you using the latest version?

Wait, did you change the unit of measurement for temperature to °F? If it’s still on °C it’s using you Fahrenheit input as Celcius, and then HA converts that to Fahrenheit again, resulting in a value which will be too high.

You need to change all units of measurement to the ones your integrations are providing

dovy6 · August 17, 2025, 11:24pm

That was exactly it. I had initially changed it to F, but when I just updated to the latest version, you moved the unit section, and I had accidently changed everything back to metric. Changing it back to °F has fixed the issue, and temps are back down to the slightly more sane 80 degrees.

Thanks!

erik7 · January 9, 2026, 12:19pm

After updating HA to 2026.1 the following error after each restart:

Logger: homeassistant.components.weather
Source: helpers/entity_platform.py:684
integration: Weather (documentation, issues)
First occurred: 12:43:46 (1 occurrence)
Last logged: 12:43:46

Error adding entity weather.combined for domain weather with platform template
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 684, in _async_add_entities
    await self._async_add_entity(
        entity, False, entity_registry, config_subentry_id
    )
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 1010, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1380, in add_to_platform_finish
    self.async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1024, in async_write_ha_state
    self._async_write_ha_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1149, in _async_write_ha_state
    self.__async_calculate_state()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1088, in __async_calculate_state
    if state_attributes := self.state_attributes:
                           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/weather/__init__.py", line 614, in state_attributes
    data[ATTR_WEATHER_HUMIDITY] = round(humidity)
                                  ~~~~~^^^^^^^^^^
TypeError: type str doesn't define __round__ method

Using this one and not the blueprint.

TheFes · January 12, 2026, 4:01pm

I see it myself for both the blueprint and the other setup.
I’ll have a look at it. Right now the weather entity does seem to work.

erik7 · January 12, 2026, 6:23pm

Thanks!
The entity is indeed working, the error shows up during restart.