1.7.0b2

Many Many improvements !

• Data polling is splitted across multiple coordinators. It means if one coordinator fails, only entity depending on this coordinator will be unavailable.
• Some part of the API are only fetched once a day (like facility name, mac addresses, firmware version, etc.)
• If all entities depending on a coordinator are disabled, this coordinator doesn't fetch the API anymore
• Adding VR51 child lock binary_sensor
• Adding humidity for a room climate if there is VR51
• Adding cooling_for_x_days_duration attribute if the zone is in quick mode QM_COOLING_FOR_X_DAYS
• Name of the event has changed from multimatic_refresh_entities to multimatic_refresh_event when quick_mode or holiday mode is changed

1.7.0b1

• Code quality improvement
• Remove some incorrect device_class
• None safe name, unit_of_measurement, etc.
• Better logging in case of error

1.7.0b0

• BREAKING CHANGE: improvements of the unique_id of some entities (entity_id is untouched).
  You may have to delete old entities which will be unavailable and change the entity_id of newly created entities (because they may have entity_id like xxx_2)
• Names and units of sensors are None safe
• Many technical improvements on entity updates
• Better handling and logging in case of error
• Update pymultimatic to 0.4.x (= improvement in handling wrong responses coming from the API)
• It should be possible to create multiple instance of the integration

Add iot_class in manifest

Support iot_class for HA > 2021.5.x

Full Hacs integration

• Logos (will be available after next HA release)
• Version alignment between releases and manifest
• Integration into the HACS default repositories
• Special thanks to @vit-

Welcome to HACS

Make integration compatible with HACS

1.5.0 Welcome to multimatic

BREAKING CHANGES Foreseen some time for the migration:

• Renaming integration from vaillant to multimatic
• entity_id doesn't contain anymore the domain (e.g: climate.vaillant_bathroom becomes climate.bathroom).
  Only few entities keep the domain inside their id (quick_mode, holiday, system_online, system_update and errors),
  otherwise, the name is too generic
• Services are also renamed from vailant.xxx to multimatic.xxx
• Add multimatic in unique_id in order to avoid collision
• Dynamic errors are removed in favor of a single binary_sensor (binary_sensor.multimatic_errors). This is
  much easier to create an automation

Other changes:

• Moving to DataUpdateCoordinator
• Allowing multiple instance of the integration
• IO optimization when quick mode or holiday mode is changing.
• Add scan interval option
• Fix error when a live report is not available from the API anymore
• Add fan support
• Fix for room climate to detect if the room is heating or not
• Add version in the manifest (for HA 2021.4.x)

You may sometimes see (around 3:30 am) an error like the following.
It seems the API server is restarted every night, so the integration can't fetch data.
I can't do anything about that.

Unable to fetch data from multimatic, API says:`xxx Service Unavailable, status: xxx

How to migrate ?

1. Delete vaillant integration from HA UI
2. Delete vaillant folder from custom_component
3. Copy multimatic folder (from 1.5.0 release)
   and past it to custom_component
4. Restart HA
5. Add multimatic integration from HA UI
6. The hard job is starting now, you have to find old entity_id you were using in automation or somewhere else.
   You can do some find and replace (e.g. climate.vaillant_bathroom-> climate.bathroom)

1.5.0b7

• Add senso app support
• fix for multiple integration

1.5.0b6

add version in the manifest to be compatible with > HA 2021.3.x

1.5.0b5

Fan entity for HA > 2021.3.x