Skip to main content

Library to communicate with the Viessmann ViCare API.

Project description

PyViCare

This library implements access to Viessmann devices by using the official API from the Viessmann Developer Portal.

Breaking changes in version 2.27.x

  • Some base classes have been renamed to provide a better support for non heating devices. See PR #307

Breaking changes in version 2.8.x

  • The circuit, burner (Gaz) and compressor (Heat Pump) is now separated. Accessing the properties of the burner/compressor is moved from device.circuits to device.burners and device.compressor.

Breaking changes in version 2.x

  • The API to access your device changed to a general PyViCare class. Use this class to load all available devices.
  • The API to access the heating circuit of the device has moved to the Device class. You can now access and iterate over all available circuits via device.circuits. This allows to easily see which properties are depending on the circuit.

See the example below for how you can use that.

Breaking changes in version 1.x

  • The versions prior to 1.x used an unofficial API which stopped working on July, 15th 2021. All users need to migrate to version 1.0.0 to continue using the API.
  • Exception is raised if the library runs into a API rate limit. (See feature flag raise_exception_on_rate_limit)
  • Exception is raised if an unsupported device feature is used. (See feature flag raise_exception_on_not_supported_device_feature)
  • Python 3.4 is no longer supported.
  • Python 3.9 is now supported.

Prerequisites

To use PyViCare, every user has to register and create their personal API client. Follow these steps to create your client:

  1. Login to the Viessmann Developer Portal with your existing ViCare app username/password.
  2. On the developer dashboard click add in the clients section.
  3. Create a new client using following data:
    • Name: PyViCare
    • Google reCAPTCHA: Disabled
    • Redirect URIs: vicare://oauth-callback/everest
  4. Copy the Client ID to use in your code. Pass it as constructor parameter to the device.

Please note that not all properties from older versions and the ViCare mobile app are available in the new API. Missing properties were removed and might be added later if they are available again.

Help

We need help testing and improving PyViCare, since the maintainers only have specific types of heating systems. For bugs, questions or feature requests join the PyViCare channel on Discord or create an issue in this repository.

Device Features / Errors

Depending on the device, some features are not available/supported. This results in a raising of a PyViCareNotSupportedFeatureError if the dedicated method is called. This is most likely not a bug, but a limitation of the device itself.

Tip: You can use Pythons contextlib.suppress to handle it gracefully.

Types of heatings

  • Use asGazBoiler for gas heatings
  • Use asHeatPump for heat pumps
  • Use asFuelCell for fuel cells
  • Use asPelletsBoiler for pellets heatings
  • Use asOilBoiler for oil heatings
  • Use asHybridDevice for gas/heat pump hybrid heatings

Basic Usage:

import sys
import logging
from PyViCare.PyViCare import PyViCare

client_id = "INSERT CLIENT ID"
email = "email@domain"
password = "password"

vicare = PyViCare()
vicare.initWithCredentials(email, password, client_id, "token.save")
device = vicare.devices[1]
print(device.getModel())
print("Online" if device.isOnline() else "Offline")

t = device.asAutoDetectDevice()
print(t.getDomesticHotWaterConfiguredTemperature())
print(t.getDomesticHotWaterStorageTemperature())
print(t.getOutsideTemperature())
print(t.getRoomTemperature())
print(t.getBoilerTemperature())
print(t.setDomesticHotWaterTemperature(59))

circuit = t.circuits[0] #select heating circuit

print(circuit.getSupplyTemperature())
print(circuit.getHeatingCurveShift())
print(circuit.getHeatingCurveSlope())

print(circuit.getActiveProgram())
print(circuit.getPrograms())

print(circuit.getCurrentDesiredTemperature())
print(circuit.getDesiredTemperatureForProgram("comfort"))
print(circuit.getActiveMode())

print(circuit.getDesiredTemperatureForProgram("comfort"))
print(circuit.setProgramTemperature("comfort",21))
print(circuit.activateProgram("comfort"))
print(circuit.deactivateComfort())

burner = t.burners[0] #select burner
print(burner.getActive())

compressor = t.compressors[0] #select compressor
print(compressor.getActive())

API Usage in Postman

Follow these steps to access the API in Postman:

  1. Create an access token in the Authorization tab with type OAuth 2.0 and following inputs:

    • Token Name: PyViCare
    • Grant Type: Authorization Code (With PKCE)
    • Callback URL: vicare://oauth-callback/everest
    • Authorize using browser: Disabled
    • Auth URL: https://iam.viessmann-climatesolutions.com/idp/v3/authorize
    • Access Token URL: https://iam.viessmann-climatesolutions.com/idp/v3/token
    • Client ID: Your personal Client ID created in the developer portal.
    • Client Secret: Blank
    • Code Challenge Method: SHA-256
    • Code Veriefier: Blank
    • Scope: IoT User
    • State: Blank
    • Client Authentication: Send client credentials in body.

    A login popup will open. Enter your ViCare username and password.

  2. Use this URL to access your installationId, gatewaySerial and deviceId:

    https://api.viessmann-climatesolutions.com/iot/v1/equipment/installations?includeGateways=true

    • installationId is data[0].id
    • gatewaySerial is data[0].gateways[0].serial
    • deviceId is data[0].gateways[0].devices[0].id
  3. Use above data to replace {installationId}, {gatewaySerial} and {deviceId} in this URL to investigate the Viessmann API:

    https://api.viessmann-climatesolutions.com/iot/v1/features/installations/{installationId}/gateways/{gatewaySerial}/devices/{deviceId}/features

Rate Limits

Due to latest changes in the Viessmann API rate limits can be hit. In that case a PyViCareRateLimitError is raised. You can read from the error (limitResetDate) when the rate limit is reset.

More different devices for test cases needed

In order to help ensuring making it easier to create more test cases you can run this code and make a pull request with the new test of your device type added. Your test should be committed into tests/response and named <family><model>.

The code to run to make this happen is below. This automatically removes "sensitive" information like installation id and serial numbers. You can either replace default values or use the PYVICARE_* environment variables.

import sys
import os
from PyViCare.PyViCare import PyViCare

client_id = os.getenv("PYVICARE_CLIENT_ID", "INSERT CLIENT_ID")
email = os.getenv("PYVICARE_EMAIL", "email@domain")
password = os.getenv("PYVICARE_PASSWORD", "password")

vicare = PyViCare()
vicare.initWithCredentials(email, password, client_id, "token.save")

with open(f"dump.json", mode='w') as output:
   output.write(vicare.devices[0].dump_secure())

To make the test data comparable with future updates, it must be sorted. No worries, this can be done automatically using jq.

jq ".data|=sort_by(.feature)" --sort-keys testData.json > testDataSorted.json

Testing

Home Assistant

To test a certain change in Home Assistant, one needs to have a ViCare integration installed as a custom component. Change the dependency in the manifest.json to point to a GitHub branch or commit SHA:

  "requirements": [
    "PyViCare@git+https://github.com/openviess/PyViCare.git@<branchname>"
  ],

To install ViCare as a custom component, one can use the terminal addon to install the changes from a certain Home Assistant PR:

curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d vicare -p <pr-number>

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pyvicare-2.59.0.tar.gz (31.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

pyvicare-2.59.0-py3-none-any.whl (41.1 kB view details)

Uploaded Python 3

File details

Details for the file pyvicare-2.59.0.tar.gz.

File metadata

  • Download URL: pyvicare-2.59.0.tar.gz
  • Upload date:
  • Size: 31.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.13

File hashes

Hashes for pyvicare-2.59.0.tar.gz
Algorithm Hash digest
SHA256 38afe8728c90c341ca90de366b3849d66176529d60b5f187d19986eb45b56ea9
MD5 7f3de011124b552157984e9cdcbfc4a8
BLAKE2b-256 7527d83dbe02627013979766b97a1e4c88347d9663dc734640c5e3f2e2c79b33

See more details on using hashes here.

File details

Details for the file pyvicare-2.59.0-py3-none-any.whl.

File metadata

  • Download URL: pyvicare-2.59.0-py3-none-any.whl
  • Upload date:
  • Size: 41.1 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.13

File hashes

Hashes for pyvicare-2.59.0-py3-none-any.whl
Algorithm Hash digest
SHA256 0dc8835d762d1f1f09ad776fa6b2bef8cb38536eda8278145f3751564d185a9c
MD5 1121193ea233bb7ac963e34928cd7adc
BLAKE2b-256 e41e69cad2b82767860004297a640b8872c82338e7bf74c72de5d92151f23e42

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page