{% if installed %}
Updating to v0.10.0 or later release, from v0.9.0, introduces new breaking change. Dedicated switch for hot water boost is reintroduced, as part of the water heater device, which removes HWB feature from the water heater itself.
water_heater.{boiler_name}
now only has three operation modes -heating
,hot_water_only
orstand_by
- If the removed
hot_water_boost
operation mode was used in automations, solution is to change automations to useswitch.turn_on
orswitch.turn_off
targeting the newswitch.{boiler_name}_hot_water_boost
entity instead ofwater_heater.set_operation_mode
- If the removed
Updating to v0.9.0 or later release, from any release before v0.9.0, introduces some breaking changes. The list is the following:
switch.{thermostat_name}_hwb
is now removed and integrated intowater_heater.{boiler_name}
entity, as one of the operations of the water heater- If this switch was used in automations, solution is to change automations to use
water_heater.set_operation_mode
service instead ofswitch.turn_on
andswitch.turn_off
- operation mode to turn on HWB ishot_water_boost
, while any other operation mode turns it off
- If this switch was used in automations, solution is to change automations to use
number.{thermostat_name}_dhw_temperature
is now removed and integrated intowater_heater.{boiler_name}
entity, as desired temperature of the water heater- If this value was used in automations, solution is to change automations to use
water_heater.set_temperature
service instead ofnumber.set_native_value
- If this value was used in automations, solution is to change automations to use
climate.{thermostat_name}
now has onlyauto
andheating
modes,off
is removed- This means thermostat "can't be turned off", but boiler can. Turn it off by setting water heater operation mode to
stand_by
-water_heater.set_operation_mode(stand_by)
- This means thermostat "can't be turned off", but boiler can. Turn it off by setting water heater operation mode to
climate.{thermostat_name}
now has onlyAWAY
preset (in addition toNONE
),SUMMER
,WINTER
andHOME
presets are removed- To toggle between away and home presets, simply toggle between away and none
- Other presets are now also water heater operations, which can be set by calling
water_heater.set_operation_mode
service- To use
WINTER
preset, useheating
operation mode - To use
SUMMER
preset, usehot_water_only
operation mode
- To use
In addition to these breaking changes, all entities now follow new conventions for naming entities. This will not rename any of the existing entities after upgrading, but if the integration is removed and reinstalled, all the entities will have the new names, instead of the old names, which will break automations referencing entities by names.
These changes align the integration better with the newly redesigned releases of the Vaillant vSMART app, while also making them more consistent and native to the Home Assistant.
{% endif %}
This component will set up the following platforms.
Platform | Description |
---|---|
climate |
|
select |
|
sensor |
|
switch |
|
water_heater |
{% if not installed %}
- Click "Install this repository in HACS"
- Restart Home Assistant
- In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Vaillant vSMART".
{% endif %}
Check out the community page. You can find out how to extract client ID and client secret there.
For Vaillant Vsmart
- Client ID : na_client_android_vaillant
- Client secret : XXXXXXXXXXXXXXXXXXXXXXX (see above)
- Username : MY_VAILLANT_APP_USERNAME
- Password : MY_VAILLANT_APP_PWD
- User prefix : vaillant
- App version : 1.0.4.0
For MiGo
- Client ID : na_client_android_sdbg
- Client secret : XXXXXXXXXXXXXXXXXXXXXXX (see above)
- Username : MY_MIGO_APP_USERNAME
- Password : MY_MIGO_APP_PWD
- User prefix : sdbg
- App version : 1.3.0.4
This project was generated from @oncleben31's Home Assistant Custom Component Cookiecutter template.
Code template was mainly taken from @Ludeeus's integration_blueprint template
This integration is a complete rewrite of @pjmaenh's original Vaillant integration.
Thanks to @philippelt, @jabesq, @samueldumont, @jabesq, @pjmaenh and @superbunika for providing many details of the underlying API, which this component uses.