MrBartusek / MeteoalarmCard

Meteoalarm, Météo-France and DWD severe weather warnings card for Home Assistant Lovelace UI ⛈️
MIT License
134 stars 49 forks source link

DWD selected integration doesn't match selected entity #214

Closed kineci closed 11 months ago

kineci commented 1 year ago

Describe the bug

Can some one take a look at what's wrong?

Integration state attributes

region_name: Stadt Nordenham region_id: 803461007 last_update: '2023-09-16T23:32:08.690000+00:00' warning_count: 0 attribution: Data provided by DWD icon: mdi:close-octagon-outline friendly_name: DWD Weather Warnings 803461007 Aktuelle Warnstufe

region_name: Stadt Nordenham region_id: 803461007 last_update: '2023-09-16T23:47:08.675000+00:00' warning_count: 0 attribution: Data provided by DWD icon: mdi:close-octagon-outline friendly_name: DWD Weather Warnings 803461007 Vorwarnstufe

Screenshots

Screenshot (62) Screenshot (60)

Card version

2.5.4

Installation type

Home Assistant Community Store (HACS)

Card Configuration

type: custom:meteoalarm-card entities:

Integration type

Deutscher Wetterdienst (DWD)

Integration configuration

GUI

Integration Configuration

No response

csoltenborn commented 1 year ago

Same problem here. Same configuration as above, but with 105315000 (Stadt Köln) and 705315105 (Köln Nippes).

arboeh commented 1 year ago

Same here...

kineci commented 1 year ago

I eventually fixed it myself. It's a language issue. Because the entities are created in German by the integration they cannot be recognised. You have to rename both sensors accordingly. Changing "vorwahnstufe" to "advance_warning_level" and "aktuelle_warnstufe" to "current_warning_level"

So the entity-id's are renamed like they are mentioned in the documentation:

Before:

After:

Don't forget to enter your city code after "...warnings_" tho.

Same problem here. Same configuration as above, but with 105315000 (Stadt Köln) and 705315105 (Köln Nippes).

So in your case (Stadt Köln), it would have to be named like:

It's strange, that it's not mentioned in the documentation as dwd will mainly be used by German users, so they will likely encounter the same problem.

csoltenborn commented 1 year ago

Thanks a lot, works like a charm! And indeed a strange bug in the sense that it should show up very quickly, and should be easily fixable, so why does it (still) exist? Are we the only ones using it?

Minor comment: in the final names (for me - thanks again ;-) ), you have a typo ("advanced" should be advance as pointed out correctly above). Just for the people who (like me) copy&pasted it :-)

arboeh commented 1 year ago

Thanks a lot. Had the same problem and same typo...

MrBartusek commented 1 year ago

so why does it (still) exist? Are we the only ones using it?

You are free to make PR for that, i have quite limited time recently

kineci commented 1 year ago

Minor comment: in the final names (for me - thanks again ;-) ), you have a typo ("advanced" should be advance as pointed out correctly above). Just for the people who (like me) copy&pasted it :-)

You're right. I've corrected the original comment incase someone's just copies it and thinks it doesn't work :D