Skip to content

Use current metrics instead of hourly metrics for 0 hour #49

@Intecpsp

Description

@Intecpsp

Right now, my external temperature is 61F; my configuration is to turn on if it's above 60F. The integration states that it's still cold and is off. After looking further into this, I noticed that the projection for my current hour is that the temperature was supposed to be 56F.

2025-04-15 09:40:48.648 DEBUG (MainThread) [custom_components.check_weather.binary_sensor] Forecast: {'datetime': '2025-04-15T13:00:00+00:00', 'condition': 'partlycloudy', 'wind_bearing': 320.0, 'precipitation_probability': 0.0, 'cloud_coverage': 61.0, 'uv_index': 0.2, 'temperature': 56, 'apparent_temperature': 50, 'dew_point': 44, 'pressure': 30.01, 'wind_gust_speed': 17.0, 'wind_speed': 8.05, 'precipitation': 0.0, 'humidity': 63}
2025-04-15 09:40:48.648 DEBUG (MainThread) [custom_components.check_weather.binary_sensor] Bad conditions found at 2025-04-15T13:00:00+00:00

Looking at my weather. entity, I see a temperature attribute that is telling the current temp. Is there any way to use that for the current hour, and then project out hourly using the current logic to meet the "look ahead" criteria?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions