search

r-renato / ha-climacell-weather

Climacell weather provider integration is a custom component for Home Assistant. The climacell platform uses the Climacell API as a source for meteorological data for your location.
MIT License
46 stars 10 forks source link

[Feature Request] Combine various timestep sensors into a single sensor with a list of attributes #15

Open ajayjohn opened 4 years ago

ajayjohn commented 4 years ago

If possible, could you please create a single entity for hourly or daily forecast and providing all the values related to it as an array of attributes available on it? I am not sure if this something the custom component takes care of or if it is handled by HA itself. But, this is how all the weather type entities seem to work.

Attached here is an example of how the NOAA component work. If you notice here, there is only one entity for the daily forecast. However, the entity holds the attributes needed for each and every forecast timestep. I feel like the Climacell component, as it adds more and more attributes, can make use of such a structure to avoid too many new entities from being created.

image image

r-renato commented 3 years ago

What is the name of the integration?

ddellspe commented 3 years ago

I believe that's leveraging the weather entity from homeassistant core. I've been looking into it myself and was considering taking some of the climacell work that you've done to provide some consistent weather entities and potentially writing a frontend that can provide more than just temperature forecast, etc.

ajayjohn commented 3 years ago

@r-renato As @ddellspe mentioned, any weather type entity (https://www.home-assistant.io/integrations/#weather) would typically behave this way. The ones I have in the screenshots are https://www.home-assistant.io/integrations/weather.darksky/ and https://www.home-assistant.io/integrations/nws/.

@ddellspe It would be awesome something like that would be available in HA!

K-Money commented 3 years ago

I was just about to request the same thing myself. Glad there's already one on here.

The weather platform would also allow the usage of other lovelace cards since they all require a weather entity to function rather than individual sensors. e.g. https://www.home-assistant.io/lovelace/weather-forecast/ .

The existing Weather Conditions Card is great for pairing with this repo but may not aesthetically work in all cases for the end user. Adding the weather entity would allow the user more options.

cerebrate commented 3 years ago

Yes, indeed. (Although I would prefer that this was in addition to, rather than instead of, the current individual sensors, because it's handy to be able to use them in various places without needing a template to break out the specific attributes.)

As a side note, up until today I've been using the Weather Template integration on HACS (https://github.com/xannor/hass_weather_template) to compose a weather.climacell from the individual sensors, but it looks like 0.115.1's changes to the template platform have broken this option.

Chaotic commented 3 years ago

Yes, indeed. (Although I would prefer that this was in addition to, rather than instead of, the current individual sensors, because it's handy to be able to use them in various places without needing a template to break out the specific attributes.)

As a side note, up until today I've been using the Weather Template integration on HACS (https://github.com/xannor/hass_weather_template) to compose a weather.climacell from the individual sensors, but it looks like 0.115.1's changes to the template platform have broken this option.

Any chance you could share your template config till this gets updated?

cerebrate commented 3 years ago

Sorry, I'm afraid I deleted it shortly after 0.115 came out because of that issue I was having with the template platform. I'm now just using https://github.com/r-renato/ha-card-weather-conditions instead.