fl550 / simple_dwd_weatherforecast Goto Github PK

Unfortuneatly, I found another problem and I am not sure how to fix it (I am actually a PHP developer).

The parsing of the KML file fails with an an "list index out of range" error.

File "/usr/local/lib/python3.9/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 469, in update
    self.parse_kml(kml)
File "/usr/local/lib/python3.9/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 496, in parse_kml
    result = tree.xpath("//dwd:IssueTime", namespaces=self.namespaces)[0].text
IndexError: list index out of range

The used station was 10677. I checked the file manually and it looks exactly like the others:
MOSMIX_L_2022050815_10677.kml (renamed the file to .txt to allow upload on GitHub)

I guess the error is about this XML line:

<dwd:IssueTime>2022-05-08T15:00:00.000Z</dwd:IssueTime>

I also checked lxml and there were no recent updates that could explain this error.

These are my HA infos:

Version | core-2022.5.2
Installation Type | Home Assistant OS
Development | false
Supervisor | true
Docker | true
User | root
Virtual Environment | false
Python Version | 3.9.9
Operating System Family | Linux
Operating System Version | 5.10.103-v8
CPU Architecture | aarch64
Timezone | Europe/Berlin

Home Assistant Community Store:

GitHub API | ok
GitHub Content | ok
GitHub Web | ok
GitHub API Calls Remaining | 4855
Installed Version | 1.24.5
Stage | running
Available Repositories | 1115
Downloaded Repositories | 17

best regards,
spigandromeda

P.S. the error occurred only after I installed the HTTP patch (download results with HTTP and HTTPS are the same).

Hello, I noticed a reproducable one day shift of th e data at 0:00 o'clock. The shift exists also at 0:30 but disapears at 1:00 o'clock. I am using the dwdforecast.Weather method. Basically at 0:00 o'clock the data contains only 9 days.

Regards

Meik

The order of the map layers is currently wrong

With the url as per the line 43, above:
https://maps.dwd.de/geoserver/dwd/wms?service=WMS&version=1.1.0&request=GetMap&layers=dwd:Laender,dwd:Satellite_meteosat_1km_euat_rgb_day_hrv_and_night_ir108_3h&bbox=4.4,46.4,16.1,55.6&width=720&height=803&srs=EPSG:4326&styles=&format=image/png

we get this image

Reversing the two layers to have it this way
https://maps.dwd.de/geoserver/dwd/wms?service=WMS&version=1.1.0&request=GetMap&layers=dwd:Satellite_meteosat_1km_euat_rgb_day_hrv_and_night_ir108_3h,dwd:Laender&bbox=4.4,46.4,16.1,55.6&width=720&height=803&srs=EPSG:4326&styles=&format=image/png

we get this image

Right after installing i get the following message:

The dwd_weather integration is using deprecated forecast
This stops working in version 2024.3.0. Please address before upgrading.
The integration dwd_weather is using the deprecated forecast attribute.

Please report it to the custom integration author..

I am currently on Home Assistant version 2023.9.2

K620 ---- KANZERN

should be

K620 ---- KANZEM

https://goo.gl/maps/5zHFF9UE7wLbSxBV9

Due to an incorrect representation of the geographic coordinates in the source file for the MOSMIX stations #1 their position is incorrect.
On #1 the position is not in decimal format, but in degree and minutes separated by a dot.

Example

ID    ICAO NAME                 LAT    LON     ELEV
10763 EDDN NUERNBERG             49.30   11.03   318

whereas #2:

Stations-Kennziffer | Stations_ID | ICAO-Kennung | Stationsname | Stationshöhe in Metern | geogr. Breite | geogr. Länge
10763 | 3668 | EDDN | Nürnberg | 314 | 49° 30' | 11° 03'

And #3 states the exact decimal coordinates as 49.503, 11.0549

So for the time being, I would suggest parsing the incorrect values. Dividing the places after the decimal point by 60 to convert from arcminute to decimal. With the values from the example resulting in 49.5, 11,05. This should be sufficient to find the next station.

I only became aware of the error because the Home Assistan Integration suggested stations that are really not that close by! 😉

After the installation using hacs,

i can not find the integration in the frontend.

I hope this message finds you well. I am reaching out to seek further clarification regarding the sun irradiance values I have received from your API. I have been analyzing the data for different German cities, and the irradiance values I retrieved are considerably higher than I initially anticipated.

While I am not an expert in meteorology, I had understood that the maximum possible amount of solar irradiance reaching the Earth's atmosphere is approximately 1365 W/m². Particularly in Germany, I assumed this value to be somewhat lower. However, upon examining the hourly dataframes for cities like Germany and Potsdam, I noticed that the values exceed 2000 W/m².

I must admit that I am a bit perplexed by these readings and would greatly appreciate your guidance in understanding this matter better. I would like to comprehend the specifics of the "sun_irradiance" parameter better, as it appears that my current understanding might be incomplete or incorrect. Your insights into the nature of these irradiance values and the factors that could contribute to such measurements would be invaluable.

I want to express my gratitude for the functionality of your API, which has been performing remarkably well for my purposes. I eagerly await your response and am thankful for any assistance you can provide in shedding light on this situation.

Thank you for your time and support.

Best regards
Max

https://opendata.dwd.de/weather/weather_reports/poi/

I was wondering if it would be possible to add support for ICON-D2.

It seems to provide significantly more accurate data (thanks to higher resolutions it seems) than the "normal" ICON model.

Since it's in grib2 format, it would probably require a different method of parsing.

DWD Documentation of ICON-D2 (Section 6.3. Near surface products)
DWD OpenData Folder for ICON-D2 (the subfolders are different generation times if I understand correctly)

Also this data would need to be merged with the normal ICON (or ICON-EU, see below) model for >45h forecast.

I would be happy to help, but I thought getting an overview first (and your opinion on this) would probably help.

If you want to see it in action, windy has this model included.

EDIT: After some further reading, the normal station data seems to depend on the ICON 13km resolution. Seeing this, it would probably also help to switch to ICON-EU for the 45h+ forecast.

Resolutions
ICON: 13km
ICON-EU: 6.5km
ICON-D2: 2.2km

Motivation: ICON data differs significantly where I live (in the 5° range temperature wise, precipitation is even worse), so getting more accurate forecast (into hass) is always helpful.

If I call this
temperature = dwd_weather.get_forecast_data(dwdforecast.WeatherDataType.TEMPERATURE, time)
multiple times for the same dwd_weather (the same station) it crashes (want to use different times):
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 239, in get_forecast_data
if self.is_in_timerange(timestamp):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/simple_dwd_weatherforecast/dwdforecast.py", line 219, in is_in_timerange
list(self.forecast_data.keys())[0]
^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'keys'

I get the Impression, that the kml file ist fatched on every get query (I am fetching one hour after another in a outer loop and it takes about 2s per hour). From reading the code (I am Python beginner) I understood, that new data shall be fatched only if the kml issued time is older than 6 hours. Sometimes running the same code goes very fast. So I assume that there ist an issue with the issue time supplied by the dwd. Is there any solution to it?

I was wondering why the home assistant integration was returning a station which is far away from the lat/long from my home.
I have then checked the values that DWD provides in their station list.
If they write 50.25 they don’t mean the decimal value 50.25, but 50 degrees, 25 minutes.
I‘m on my phone right now and can’t type the degree symbol, but you can check this in google maps when you type 50*25'N 7*13'E in the search bar (replace * with the degree symbol).

Hi,
I just came around to an issue with the station.json file when updating the HCAS dwd weather add-on to v2.0.

First, I just noticed that the somehow migrated station was displaying "wrong" data. I re-added, in my case the station of Nürnberg Airport, and noticed that the station IDs differ.

Second, in home assistant when you configure the add-on you will get a list of weather stations close by. There I noticed a vast of stations that are historic: The stations were once operated by the DWD, but have since been decommissioned (e.g. Station Tennenlohe ID 11659 out of service since 24.04.1978 1).

Now comes the fun part: DWD somehow re-uses those IDs 🤦‍♂️. So the ID from my example (11659) now maps to Přibyslav in Czech Republic 2. Hence, you select a station nearby and get data from else where 😄

So I guess the station file needs a little rework.