Mariusthvdb commented 3 years ago

The problem

and because of that, the forecast card in Lovelace has an empty placeholder behind the windspeed position. Post it here in core, because the integration doesnt collect the data, either from a dedicated template, nor from the other data in the config.

What is version of Home Assistant Core has the issue?

2021.3.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Weather template

Link to integration documentation on our website

https://www.home-assistant.io/integrations/weather.template/

Example YAML snippet

# Put your YAML below this line
  - type: weather-forecast
    entity: weather.composite

and:

  - platform: template
    name: Composite
    condition_template: >
      {{states('sensor.br_condition')}}
    temperature_template: >
      {{states('sensor.weatherbit_apparent_temperature')|float}}
    humidity_template: >
      {{states('sensor.weatherbit_humidity')|float}}
    forecast_template: >
      {{state_attr('weather.dark_sky','forecast')}}
    pressure_template: >
      {{states('sensor.luftdaten_37248_pressure')|float}}
    wind_speed_template: >
      {{states('sensor.openweathermap_wind_speed')|float}}

Anything in the logs that might be useful for us?

# Put your logs below this line

please dont refer this as a feature request, the template integration should contain all entities to respectfully fill/feed the default core Lovelace representation.

probot-home-assistant[bot] commented 3 years ago

Hey there @phracturedblue, @tetienne, mind taking a look at this issue as its been labeled with an integration (template) you are listed as a codeowner for? Thanks! _{^{(message by CodeOwnersMention)}}

avee87 commented 3 years ago

47736 should take care of this

github-actions[bot] commented 3 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.