I am not receiving any updates on DWD-Unwetterwarnung, but the following entry is in the log:
2020-12-27 10:12:32.787 [INFO ] [openhab.event.ChannelTriggeredEvent ] - dwdunwetter:dwdwarnings:03662255ae:updated0 triggered NEW
According to the documentation and the automatic thing definition in the MainUI, the first warning should be with warningN (N = 1) not “updated0”.
Only the channel “lastUpdated” that is not related to a specific warning ist updated: 2020-12-27 11:02:00.667 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'WarningAbgLastUpdated' changed from 2020-12-27T11:00:50.313641+0100 to 2020-12-27T11:02:00.666166+0100
Additional Information: I am using OH3 in a docker container at my Synology Diskstation 920+
Could anybody give me a hint?
Hi there,
thanks for your support. It would be nice if you could give us a short feedback as to whether it is due to the revision of the binding. Then I wait and look for the other points / problems that my double migration (OH2 -> OH3 and PI4 -> DS920 +) has brought with it.
Please rename it from “.txt” to “.zip”, extract the “.jar” file and put it into your addons/ folder. Uninstall any other DWD Unwetter binding version before.
I’ve change the Cell-Id because at the moment there is no warning at my local Cell-Id
The snapshot work with the tested Cell-Id (815085370), only the “Height (from)(1)” and “Height (to)(1)” values are “Err” and the trigger “Updated(1)” is NULL. But this might be correct?
after enabling debugging of the DWD Unwetter Binding, I found exactly the same response as Reinhard did for the warncell id from my configuration.
So I suspect it’s a general issue with the binding? I’m using the SNAPSHOT that was announced here on Dec 30th.
By the way: In the complete json from the binding documentation I found two warncell ids for my city. I tried setting up the thing with both, but the results are always the same.
I am testing the DWD Unwetter Binding just at the moment and have seen the same response.
I found warnings for several Cell-IDs in the json-file, but when I tested to request those warnings by using those Cell-IDs through the Unwetter-Binding it returned no warnings. I assume the reason for this is, that there are differences with the warnings issued through the json-file and the geoserver-request that the Unwetter-Binding uses.
I would suggest to enter the mentioned “raw request” in a web browser.
The actual issue is: The module uses the hardcoded URL https://maps.dwd.de/geoserver/dwd/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=dwd:Warnungen_Gemeinden&CQL_FILTER=WARNCELLID+LIKE+
This does not work for “Landkreise”
I’ve changed the URL to https://maps.dwd.de/geoserver/dwd/ows?service=WFS&version=2.0.0&request=GetFeature&typeName=dwd:Warnungen_Landkreise&CQL_FILTER=GC_WARNCELLID+LIKE+ which gives me the expected output for my cell ID.
I do see two solutions here:
Intruduce a parameter to use either the “Gemeine” or the “Landkreis” url
fallback to the “Landkreis” route as a fallback when there is no data returned from the “Gemeinde” route
If someone is working on the “DWD-Unwetter” binding, i suggest to solve another problem:
(I know this is slightly off-topic, but it is only a short hint in case the code is revised anyway).
Converting the values for “ALTITUDE” and “CEILING” can lead to conversion errors:
14:01:01.734 [WARN ] [se.internal.SseItemStatesEventBuilder] - Exception while formatting value '3000.00000456 m' of item WeatherWarnings_Heightto1 with format '%d m': d != java.math.BigDecimal
I assume that the conversion from “feet” to “m” is the reason for this. The correct result should be “3000 m”.
At the moment there is another issue with the “DWD-Unwetter” binding:
The DWD servers answer very slow. The timeout value of 5000 ms is not sufficient:
14:50:46.866 [WARN ] [er.internal.data.DwdWarningDataAccess] - Communication error occurred while getting data: java.util.concurrent.TimeoutException: Total timeout 5000 ms elapsed
(Please tell me if I should open a new thread instead of posting this here)
Normally, you just have to wait until there is a concrete warning for your city.
I had to wait several weeks, until today. Now there is a warning “Sturmböen” and it is available for my city.
If you change the URL from “Warnungen_Gemeinden” to “Warnungen_Landkreise” you will get more warnings, but the location is less precise.