Hey! This is the first release candidate for the new version Hey everyone! I'm proud to announce the release of the new major MeteoalarmCard version 2.0! This update brings a lot of exciting features, improvements and fixes. But first, I want to say Thank You! to every single one of you! Without contributors, translators and users this project wouldn't grow so much. A couple of months ago MeteoalarmCard turned one year old and in this period accumulated over 13k downloads of 25 releases and, was translated to 11 languages. Your existing card configuration won't work with this update, and thus this is a major release.
Starting from this update Since version v1.0.0 the vision of the project changed a bit. I've made this card mostly because there wasn't any viable option for cleanly displaying alerts. This card was, back then, focused on only one thing - MeteoAlarm integration. But this started to change as the project gained popularity.
v1.5.0 - Added first multi-integration support for xlcnd/meteoalarmeu. It was very seamless and worked without even the user knowing it. And from update to update this feature became more and more annoying. For example, the Visual card editor doesn't really know what integration will be selected by the card, it only knows that it is Starting from this update Pre 2.0.0 configuration
Post 2.0.0 configuration
More on why this decision was taken below.
This may not look like it but this is the biggest change in this update. Instead of providing only one entity, you can now provide multiple! There are a couple of ways to do it.
One entity ID:
List of entity IDs:
List of entity objects:
This project was waiting for this ability for a long time. It finally gives the possibility to implement new muli-entity integrations.
Home Assistant 2022.3 made a bit of revolution in the way of handling visual editor by the cards. It broke MeteoalarmCard visual editor (#81) and other cards while bringing the new Material Web Components (MWC). Starting from 2.0 MeteoalarmCard ships with the new and improved graphical card editor. It now supports multiple entities and uses MWC.
Before this update, only the first alert was displayed on the card. This caused any other alerts to be hidden from the user. Now, when the card detects more than one alert it enables the swiper and populates each slide with one alert. When the swiper is activated, it shows pagination (white and grey dots) in the lower part of the card. This behaviour can be disabled with Caption is a new card element displayed in the top right of the card. This element is currently only used to inform users using DWD if they are looking at future alerts (coming from the For the past year, the code became a bit messy so I took the time to rethink and rewrite the whole codebase.
Other changes in this update not listed above:
This release adds a bunch of new translation keys and you will see a lot of missing strings in this version. The current translation progress is as follows:
You can help to add missing keys in existing languages or add a new language - see CONTRIBUTING.md!
v2.0.0. This version may still contain a lot of issues and shortcomings. Please report all issues that you find to the issue tracker. There are a lot of new translation keys. You can help to add missing keys in existing languages or add a new language - see CONTRIBUTING.md!
Release notes (subject to change)
Table of contents
integration: automatic has been removed
entity was renamed to entities ⚠️ BREAKING:
integration: automatic has been removed. automatic is not a valid integration type. Please switch to using the name of the currently used integration.
meteoalarm
meteofrance
dwd
weatheralerts
Why this decision was taken
v1.6.0 - It was a huge update code-wide @Nsbx wrote the first code for the support of the multi-integration system. Back then I suggested the ability to set integration: automatic since integrations were easy to detect and this didn't cause any problems.
automatic. That really blocks any ability to make anything in the editor to be dependent on the integration. For example, the Override headline was displayed when automatic was selected even if the selected entity doesn't provide a headline and thus, this option was useless. You may say, this wasn't that bad, and yes, it wasn't. The real problem begins if you look at the new editor when virtually the whole experience is now based on which integration you will select. That's the reason this integration is gone.
⚠️ BREAKING:
entity was renamed to entities entity config value has been removed and replaced with entities. Future use of entity will result in an error. Please switch to using entities.
type: 'custom:meteoalarm-card'
integration: 'meteoalarm'
entity: 'binary_sensor.meteoalarm'
type: 'custom:meteoalarm-card'
integration: 'meteoalarm'
entities: 'binary_sensor.meteoalarm'
Multiple entity support & new integrations
entities: binary_sensor.sensor_1
entities:
- binary_sensor.sensor_1
- binary_sensor.sensor_2
entities:
- entity: binary_sensor.sensor_1
- entity: binary_sensor.sensor_2
New integrations
New Visual Editor
Alerts swiper
disable_swiper.
New element: caption
advance_warning_level sensor). This element may find more use in future updates.
General project cleanup
ScopedRegistryHost for HA 2022.03.
Other changes
CONTRIBUTING.md and README.md readablity updates @MrBartusek
hide_when_no_warning @MrBartusek in #92
New translations
+ English - 100% translated
+ Spanish - 100% translated
+ Polish- 100% translated
- Czech - 90% translated
- French - 57% translated
- German - 55% translated
- Estonian - 55% translated
- Croatian - 55% translated
- Slovak - 55% translated
- Swedish - 50% translated
- Dutch - 40% translated
- Italian- 29% translated