v1.15.2: HP heating status binary sensors (BLOKYSPOTREBY)
New features
Consumption prioritizer binary sensors
The heat pump has an internal BLOKYSPOTREBY (consumption block / prioritizer) system that decides which consumer gets heat at any given moment. Each consumer now has a proper binary sensor in Home Assistant:
| Entity | Meaning |
|---|---|
| �inary_sensor.*_blokyspotreby_ok | HP is currently heating the radiator/floor circuit |
| �inary_sensor.*_blokyspotreby3_ok | HP is currently heating domestic hot water (DHW) |
| �inary_sensor.*_blokyspotreby1_ok | HP is currently heating pool 1 |
| �inary_sensor.*_blokyspotreby2_ok | HP is currently heating pool room |
| �inary_sensor.*_blokyspotreby6_ok | HP is currently heating DHW 2 |
| �inary_sensor.*_blokyspotreby7_ok | HP is currently heating pool 2 |
Plus matching -utlum (attenuation) variants for each consumer.
These fields have a _BOOL_i register suffix (which the coordinator normally treats as a writable switch), but they are read-only status outputs. The new HIDDEN_BINARY_SENSORS override mechanism forces them to be binary sensors.
Bug fixes
- Fixed Missing entity_id in entity_data WARNING that appeared for all binary sensors on every poll. The entity ID is now stored inside the self.entities value dict, not only as the dict key.