Open nepozs opened 1 year ago
The real problem is that since v2.0.0 it's possible for users to change entity names to anything they want. You can check out my solution for this problem here. This code allows me to retrieve all entities from the same device as the entity passed in the argument. Then I recognize every entity by comparing its unique id. I believe a similar approach might be possible to be used for this card as well.
Quick and dirty workaround for users (2024.07.14 - still works, MeteoalarmCard v2.7.1 + Burze.dzis.net sensor v2.0.1) - entity names should be changed to compatible with burze_dzis_net versions prior to 2.0.0 https://forum.arturhome.pl/t/integracja-burze-dzis-net-jak-wyswietlic-tylko-ostrzezenia-wlaczone/5189/10
Describe the bug
There are new entities generated after update (with breaking changes) https://github.com/PiotrMachowski/Home-Assistant-custom-components-Burze.dzis.net/releases/tag/v2.0.0
error:
Integration state attributes
Examples of active state (state on ) New entities have new names
Example of new format entity, alert active new entity name
binary_sensor.burze_dzis_net_ostrzezenie_upal
attributes:example of new format secondary entity, alert active new entity name
binary_sensor.burze_dzis_net_ostrzezenie_aktywne_upal
attributes:old version entity (from different installation)
entity name
binary_sensor.burze_dzis_net_heat_warning
attributes:Example of inactive (state off)`
binary_sensor.burze_dzis_net_ostrzezenie_mroz
state off, attributessecondary entity
binary_sensor.burze_dzis_net_ostrzezenie_aktywne_mroz
state off, attributesold version burze_dzis_net
binary_sensor.burze_dzis_net_frost_warning
state off, attributesScreenshots
Card version
v2.5.3
Installation type
Home Assistant Community Store (HACS)
Card Configuration
Integration type
Burze.dzis.net
Integration configuration
GUI
Integration Configuration
new version has only GUI config
error exist also with primary entities