KeyError: '2' in sensor.py blocks HA startup (zone parsing issue?)

[Maciolus]

Hi,
after updating Home Assistant (2026.x, Python 3.13, HA OS – Home Assistant Green), the tauron_amiplus integration throws an exception during startup and significantly delays (or interferes with) HA initialization.
Error from logs:
Waiting for integrations to complete setup: {('tauron_amiplus', ...)}
File "/config/custom_components/tauron_amiplus/sensor.py", line 255, in get_balanced_data
zone = zone_names[consumption["Zone"]]
KeyError: '2'
It looks like consumption["Zone"] returns "2", but "2" is not present in zone_names.
Observed behavior
Home Assistant waits for integration setup during boot
Supervisor logs show:
Another job is running for job group addon_xxx
Add-ons (e.g. Node-RED) fail to start properly during boot
Disabling tauron_amiplus resolves the issue immediately
Questions
Has Tauron changed the format of zone identifiers?
Should the integration handle dynamic/unknown zone values?
Would it make sense to add defensive handling, e.g.:
zone = zone_names.get(consumption.get("Zone"))
if zone is None:
_LOGGER.warning("Unknown zone received: %s", consumption.get("Zone"))
continue
At the moment, a single unexpected zone value causes a full setup failure.
I can help test a fix if needed.
Thanks for your work on this integration.

[PiotrMachowski]

Yeah, it seems that data returned by eLicznik is not so reliable