This component will set up the following platforms.
Platform | Description |
---|---|
climate |
|
select |
|
sensor |
|
switch |
|
water_heater |
- Open HACS
- Search for "Vaillant vSMART"
- If it doesn't exist yet, you first need to add
https://github.com/MislavMandaric/home-assistant-vaillant-vsmart
as custom repository
- If it doesn't exist yet, you first need to add
- Click "Install this repository in HACS"
- Restart Home Assistant
- In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Vaillant vSMART"
- Using the tool of choice open the directory (folder) for your HA configuration (where you find
configuration.yaml
) - If you do not have a
custom_components
directory (folder) there, you need to create it - In the
custom_components
directory (folder) create a new folder calledvaillant_vsmart
- Download all the files from the
custom_components/vaillant_vsmart/
directory (folder) in this repository - Place the files you downloaded in the new directory (folder) you created
- Restart Home Assistant
- In the HA UI go to "Configuration" -> "Integrations" click "+" and search for "Vaillant vSMART"
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
If you want to contribute to this please read the Contribution guidelines
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.