Deutscher Wetterdienst (DWD)

[chbram (Chris)]

Excellent !! I missed the “action” part of it. Working like a charm now. THANKS

[arittner (Aljoscha Rittner)]

Hi!

Thank you for the great integration into Home Assistant.

I integrated two entities via the region code, and my entities were named by these codes:

The sensor names were like this one:

sensor.dwd_weather_warnings_114713000_aktuelle_warnstufe

Today I updated to Home Assistant 2024.07 and after the update my DWD maps no longer work. I have checked the errors and the names of the entities:

What has happened here? Is it something that came from older changes (and was eventually changed with the restart of HA Update) or something that was triggered by the update itself?

I can change my Markdown cards to update to the new entity names, but I’m wondering why this happened and how to avoid these entity name changes in the future?

[FL550]

Hi,

it seems like you have mistaken the integration. My integration does not provide a “Warnstufe” so I guess this comes from another integration. Can you please confirm this?

Best regards

[arittner (Aljoscha Rittner)]

Hm, yeah. I use this integration: Deutscher Wetterdienst (DWD) Weather Warnings - Home Assistant - so, it’s another one - sorry.

[lutz85 (Lutz)]

Hello, I tried to install the HACS integration dwd_weather ( GitHub - FL550/dwd_weather: Deutscher Wetterdienst integration for Home-Assistant ). I can see it on the file system after installing it:
\homeassistant\config\custom_components\dwd_weather with all the files.

And also I see the integration in HACS view.

But I have no entities, nothing on the dashboard (only AccuWeather and Openweathermap) -( ok dashboard doesn’t matter,)
it seems to me like something failed to install.
I have already restarted and updated several times.

i run core-2024.7.2 but also did not work on 2024.6.x for me
What am I doing wrong? Thanks for the support!

(I am looking for a better sun_duration_hours prediction for the current day. AccuWeather does not work well for Germany. I quickly checked using
simple_dwd_weatherforecast with SUN_DURATION = “SunD1” # Unit: s property and it seems really good to me!)

[paddy0174 (Patrick)]

With HACS you install the integration. Next step is to enable and configure it.

Go to Einstellungen > Geräte & Dienste (Settings > Devices & Services), click on the blue button in the right down corner, and enter “DWD” into the search field.

Noted here in the documentation:

GitHub - FL550/dwd_weather: Deutscher Wetterdienst integration for...

[lutz85 (Lutz)]

ah, damn. I missed the point that said I should install it like a normal integration after adding it in HACS
Thanks!

[paddy0174 (Patrick)]

You’re welcome!

Btw. I forgot before, if you’re after other things sun related, take a look at this great integration:

GitHub - pnbruckner/ha-sun2: Home Assistant Sun2 Sensor

Enhanced Sun component

[Sun2 Sensor] Have you ever wanted to: use sunrise or sunset in a template, only to discover that next_rising and next_setting change to tomorrow’s times as soon as sunrise and sunset happen? display today’s sunrise/sunset time(s) for the entire day? display or use today’s (or yesterday’s or tomorrow’s) amount of daylight? reduce the frequency at which sun.sun’s azimuth & elevation attributes are updated, e.g. to reduce the number of events in the database and log? completely eliminate azimuth…

[lutz85 (Lutz)]

Thanks! Looks cool as well - I might need it in the future!

For now I only needed the Sunhours for current day (sum over the whole day). I didn’t find an easy way to extract it from dwd_weather. so I created this python script as a service (setting a helper numerical value) to sum up the “hourly sunhours” to a day total.

EDIT: Actually I noticed that the prediction will decrease during the course of the day because the past forecast hours will drop from the “data” object
To fix this I use another helper variable (type input_text) that stores the sunhours per hour so that the python script can take it from there (last known value) if it has dropped from the forecast data object in the meantime. It’s definitely not so nice to do this without being able to define functions, use json library and other standard python features, but it works (and for me was much easier to do than in jinja)

New Python Script

# From Automation maybe not possible to pass in data?! hardcode IDs here
aggregate_sensor_id = 'sensor.dresden_flughafen_sun_duration'
ha_storevar_string_hourly_id = 'input_text.dwd_current_day_data_storevar'
output_entity_id = 'input_number.sunhours_today_dwd_python_aggregate'

# Read Forecast data
mystate = hass.states.get(aggregate_sensor_id)
mydata = mystate.attributes['data']
# Get Handle to input_text Variable that saves the sunhours per hour in format:
# 00:0.0,01:0.0,02:0.0,03:0.0,04:0.23333333333333334,05:0.48333333333333334,06:0.6666666666666666,07:0.7666666666666667,08:0.8833333333333333,09:0.9,10:0.85,11:0.85,12:0.8,13:0.7666666666666667,14:0.7333333333333333,15:0.6833333333333333,16:0.6833333333333333,17:0.65,18:0.5666666666666667,19:0.36666666666666664,20:0.0,21:0.0,22:0.0,23:0.0
# to save this string, an attribute "data" is used because the state seems to be limited to 255 characters
ha_storevar_string_hourly_obj = hass.states.get(ha_storevar_string_hourly_id)
ha_storevar_string_hourly = ha_storevar_string_hourly_obj.attributes['data']

# Get Data for Today from DWD
matchstr = str(datetime.datetime.now())[:10] + "T" # Today
predictions_today_list = [hourdict for hourdict in mydata if hourdict["datetime"].startswith(matchstr)]
# Create Dict to read values easier: key:hour_str_2digit, value = sunhours_h (for respective hour)
predictions_today_dict = {hourdict["datetime"][11:13]:hourdict["value"]/3600.0 for hourdict in predictions_today_list}

# Iterate over each hour of today
sunhours = {}
for hour in range(24):
    hour_2digit = str(hour).zfill(2)

    # check if this hour in dwd data
    if hour_2digit in predictions_today_dict:
        # then use it from there
        sunhours[hour_2digit] = predictions_today_dict[hour_2digit]
        
    else:
        # take from variable
        # sunhours[hour_2digit] = read_from_varstring(ha_storevar_string_hourly, hour_2digit)
        
        # doing this without defining a function (function not possible?)
        startpos = ha_storevar_string_hourly.index(hour_2digit + ":")
    
        remaining_string = ha_storevar_string_hourly[startpos:]
        
        if "," in remaining_string:
            # case: not last item of string
            stoppos = remaining_string.index(",")
            hour_sunvalue = float(remaining_string[3:stoppos])
        else:
            # case: last item of string
            hour_sunvalue = float(remaining_string[3:])
            # print(hour_sunvalue)
            
        sunhours[hour_2digit] = hour_sunvalue

# update the HA variable -  Finally output sunhours result to numerical variable
duration_today_h = sum(sunhours.values())
duration_today_h_rounded = round(duration_today_h, 1)
hass.states.set(output_entity_id, duration_today_h_rounded)

# save today sunhours data string in hass variable (update)
inputState = ha_storevar_string_hourly_obj.state
savestring = ",".join([f"{hourstr}:{value}" for hourstr,value  in sunhours.items()])
new_attributes = {"data" : savestring}
hass.states.set(ha_storevar_string_hourly_id, inputState, new_attributes)

Old Script (decreasing-sunhours-issue)

# From Automation maybe not possible to pass in data?! hardcode it therefore
aggregate_sensor_id = 'sensor.dresden_flughafen_sun_duration'
output_entity_id = 'input_number.sunhours_today_dwd_python_aggregate'

mystate = hass.states.get(aggregate_sensor_id)
mydata = mystate.attributes['data']

matchstr = str(datetime.datetime.now())[:10] + "T" # Today, # building without forbidden strftime

sun_durations_today = [hourdict["value"]/3600.0 for hourdict in mydata if hourdict["datetime"].startswith(matchstr)]
duration_today_h = sum(sun_durations_today)
duration_today_h_rounded = round(duration_today_h, 1)

# set state
hass.states.set(output_entity_id, duration_today_h_rounded)

[paddy0174 (Patrick)]

Hi!

I’m getting a log entry for a few days now (can’t say since when, sorry!), that tells me I should open an issue.

It’s not really dramatic, so I thought I’ll just post it here:

Logger: homeassistant.helpers.entity
Quelle: helpers/entity.py:1183
Erstmals aufgetreten: 18:43:12 (1 Vorkommnisse)
Zuletzt protokolliert: 18:43:12

Updating state for sensor.xxx_stundlich_sonnenscheindauer (<class ‘custom_components.dwd_weather.sensor.DWDWeatherForecastSensor’>) took 0.421 seconds. Please create a bug report at Issues · FL550/dwd_weather · GitHub

As I said, I don’t see this as dramatic, as the time is not really that much, but if you want me to investigate this further, please let me know!

[FL550]

@paddy0174

Updating state for sensor.xxx_stundlich_sonnenscheindauer (<class ‘custom_components.dwd_weather.sensor.DWDWeatherForecastSensor’>)

Thanks, I’ll will look into this.

[stephanschleichstr13]

How i can use the new Charts Feature?

[write-only]

2024-09-12 11:05:27.049 ERROR (MainThread) [custom_components.dwd_weather] Unexpected error fetching DWD Weather Coordinator for 10739 data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 354, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 271, in _async_update_data
    return await self.update_method()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/dwd_weather/connector.py", line 97, in async_update
    if await self._hass.async_add_executor_job(self._update):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/dwd_weather/connector.py", line 106, in _update
    self.dwd_weather.update(
  File "/usr/local/lib/python3.12/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 673, in update
    self.download_latest_kml(self.station_id, force_hourly)
  File "/usr/local/lib/python3.12/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 1013, in download_latest_kml
    self.parse_kml(kml)
  File "/usr/local/lib/python3.12/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 706, in parse_kml
    self.loaded_station_name = self.parse_station_name(tree)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 758, in parse_station_name
    return tree.xpath(
           ^^^^^^^^^^^
IndexError: list index out of range

Getting this error after changing the wind direction to degrees, deleting and re-adding the integration gives the same error (regardless of the settings I choose). Any Ideas what could be the problem here? Worked fine until now.

[FL550]

I guess you have the hourly data update enabled?

[write-only]

Yea I do, also if I disable hourly data it works again. Still strange that it worked before trying to reconfigure the extension.

[FL550]

Yes it is. And unfortunately I am unable to reproduce this with my stations. Can you please give me your station id, so I can have a closer look?

[write-only]

Sure, the Station is 10739 (Stuttgart Schnarrenberg). Thanks for your work

[DevelOpsMan (John Doe)]

That’s a cool addon from an unspying source and with nearly every data we need for weather.

In the addon I have a question, because it is somehow strange.

In the weatherforecast card one can choose the UV index as second info, but it is not listed in the sensor data of the DWD device. I also found the UV card and wanted to use the UV index directly in this card. Or is it possible to calculate it from the UV index camera data?

[FL550]

You can either use the weather.get_forecasts service to retrieve the uv data in a template sensor or you wait a few days until I have time to add a new sensor which you can then use

[DevelOpsMan (John Doe)]

In this case I prefer your update as you are far deeper in this project.

But do you know why the value is currently accessable in the card and not as sensor? It seems to be the right value. I just ask for my understanding.
Thought the values are collected as sensors and the sensors are referenced in the card.