ViCare Integration with Vitocharge VX3 electricity storage system - Bug or missing feature?

[owstr]

The problem

After setting up this integration i got errors and no entities. I strictly followed the instructions when setting up the Intehration. I can't tell if it's a bug or an incompatibility. If my device (Energy Storage VX3 type 6.0A10) does not work with it please extend the integration. In the IOS App ViCare all values are displayed correctly.

What version of Home Assistant Core has the issue?

2023.4.3

What was the last working version of Home Assistant Core?

2023.4.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ViCare

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vicare/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-04-13 10:07:24.760 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry ViCare for vicare
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 52, in async_setup_entry
    await hass.async_add_executor_job(setup_vicare_api, hass, entry)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 82, in setup_vicare_api
    device = vicare_api.devices[0]
IndexError: list index out of range

Additional information

No response

[home-assistant[bot]]

vicare documentation vicare source

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[DenisFFM]

still an issue - would be so great if this would work

[LarsTh86]

Please add this and also the support for ventilation systems. That would be fine.

[CFenner]

You probably should raise this in https://github.com/somm15/PyViCare which is the library used to query the Viessmann API.

[konairius]

It seems PyViCare has support for Vitocharge VX3 since June, what do we need to get support in home assistant?

[CFenner]

We need to update the library, currently a version from may is used.

[CHTHSCH]

I am also interested to have support for the Vitocharge VX3 added and also the Viessmann Charging Station

[CFenner]

I pushed the dependency to 2.28.1 which was released in May, but unfortunately the relevant change was contributed in June and has not yet been released.

https://github.com/home-assistant/core/pull/103064

[CFenner]

Just asked for a new release of https://github.com/somm15/PyViCare, #104516.

[CFenner]

@owstr @konairius @LarsTh86 @DenisFFM @CHTHSCH E3 should be available since December release in HA, any feedback?

I guess we would need to add some sensors in HA. What do you miss?

[LarsTh86]

I am still missing all Button for the ventilation system. For example "Intensivlüftung" or "sparbetrieb". For example from iobroker:

{ "type": "state", "common": { "name": "name", "role": "text", "type": "string", "write": false, "read": true }, "native": {}, "from": "system.adapter.viessmannapi.0", "user": "system.user.admin", "ts": 1667985008062, "_id": "viessmannapi.0.900247.0.features.ventilation.operating.programs.comfort.commands.activate.name", "acl": { "object": 1636, "state": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" } }

-->" Intensivlüftung "

And also I still missing the opportunity to change the hot water temperature 2. This temperature is the temperature für "onetimecharging". With this opportunity you could implement an onetime charging for photovoltaic. E.g if you export xxKW, you could activate "onetime charging" with high temperature. But for this automation, you need opportunity to adapt the temperature 2.

[CHTHSCH]

I guess we would need to add some sensors in HA. What do you miss?

Thanks for your efforts.

Unlike before, the Viessmann integration gets installed without problems. At the moment I only have a Vitocharge VX3 and an energy monitor installed. For those NO device or entity is generated. No heat pump yet and no Viessmann Charging station, that will come in May

[CFenner]

@CHTHSCH looking at the sample API response in PyViCare repository Vitocharge has just a few datapoints. I just added two of them in a PR https://github.com/home-assistant/core/pull/106600, would you be able to verify if this is what you need?

To test the changes simply go to your terminal in Home Assistant and use this script.

cd /config
curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d vicare -p 106600

The script will copy the code of the linked PR to your custom_components folder. After a restart the vicare integration will load from there. To fallback to the default, just remove the folder. No need to reinstall the integration.

PS: if we're fast, we may get the changes in the Januar release 😉

What is the energy monitor? What is the model name? Do you see the device name in this list?

[CFenner]

@LarsTh86 ventilation device was just added to the PyViCare library and can from now on be used in general. But like for Vitocharge, there are no sensors defined in HA yet. To be honest I do not know how the ventilation unit works and from the sample file it's not clear to me how the different programs interact.

I also added a PR https://github.com/home-assistant/core/pull/106612 to provide an ability to change the temp2 (secondary temperature?). Please verify and report back as I do not have the devices to test this.

[CHTHSCH]

@CHTHSCH looking at the sample API response in PyViCare repository Vitocharge has just a few datapoints. I just added two of them in a PR #106600, would you be able to verify if this is what you need?

To test the changes simply go to your terminal in Home Assistant and use this script.

cd /config
curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d vicare -p 106600

The script will copy the code of the linked PR to your custom_components folder. After a restart the vicare integration will load from there. To fallback to the default, just remove the folder. No need to reinstall the integration.

PS: if we're fast, we may get the changes in the Januar release 😉

What is the energy monitor? What is the model name? Do you see the device name in this list?

Thanks! I performed the commands, but still see this after a restart:

[CHTHSCH]

What is the energy monitor? What is the model name? Do you see the device name in this list?

Not in there, but also not necessary I suppose, because the Wh or kWh produced and stored by the Vitocharge VX3 are in the sample response of the API

[CFenner]

@CHTHSCH looking at the sample API response in PyViCare repository Vitocharge has just a few datapoints. I just added two of them in a PR #106600, would you be able to verify if this is what you need? To test the changes simply go to your terminal in Home Assistant and use this script.

cd /config
curl -o- -L https://gist.githubusercontent.com/bdraco/43f8043cb04b9838383fd71353e99b18/raw/core_integration_pr | bash /dev/stdin -d vicare -p 106600

The script will copy the code of the linked PR to your custom_components folder. After a restart the vicare integration will load from there. To fallback to the default, just remove the folder. No need to reinstall the integration. PS: if we're fast, we may get the changes in the Januar release 😉 What is the energy monitor? What is the model name? Do you see the device name in this list?

Thanks! I performed the commands, but still see this after a restart:

Then what do you see in the logs? You should see something like this:

2023-12-29 08:07:51.616 INFO (SyncWorker_1) [ViCare] Token restored from file
2023-12-29 08:07:51.861 INFO (SyncWorker_1) [ViCare] Device found: VScotHO1_40
2023-12-29 08:07:51.861 INFO (SyncWorker_1) [ViCare] Device found: Heatbox1
2023-12-29 08:07:51.861 INFO (SyncWorker_1) [ViCare] Device found: VScotHO1_72
2023-12-29 08:07:51.861 INFO (SyncWorker_1) [ViCare] Device found: Heatbox1

[CHTHSCH]

Then what do you see in the logs? You should see something like this:

I turned on Debug and restarted again. I still do not see a device or entity

2023-12-29 08:51:55.893 INFO (SyncWorker_9) [custom_components.vicare] Found device: E3_VitoCharge_03 (online: True) 2023-12-29 08:51:55.893 INFO (SyncWorker_9) [custom_components.vicare] Found device: E3_TCU10_x07 (online: True) 2023-12-29 08:51:55.893 INFO (SyncWorker_9) [custom_components.vicare] Found device: E3_HEMS (online: True) 2023-12-29 08:52:00.829 ERROR (SyncWorker_6) [homeassistant.components.fritzbox_callmonitor.sensor] Cannot connect to 169.254.1.1 on port 1012: [Errno 111] Connection refused 2023-12-29 08:52:02.767 DEBUG (SyncWorker_5) [custom_components.vicare.utils] Feature not supported solar_pump_active: 'ElectricalEnergySystem' object has no attribute 'getSolarPumpActive' 2023-12-29 08:52:02.767 DEBUG (SyncWorker_5) [custom_components.vicare.utils] Feature not supported charging_active: 'ElectricalEnergySystem' object has no attribute 'getDomesticHotWaterChargingActive' 2023-12-29 08:52:02.767 DEBUG (SyncWorker_5) [custom_components.vicare.utils] Feature not supported dhw_circulationpump_active: 'ElectricalEnergySystem' object has no attribute 'getDomesticHotWaterCirculationPumpActive' 2023-12-29 08:52:02.767 DEBUG (SyncWorker_5) [custom_components.vicare.utils] Feature not supported dhw_pump_active: 'ElectricalEnergySystem' object has no attribute 'getDomesticHotWaterPumpActive' 2023-12-29 08:52:02.767 DEBUG (SyncWorker_5) [custom_components.vicare.utils] No circuits found: 'ElectricalEnergySystem' object has no attribute 'circuits' 2023-12-29 08:52:02.774 DEBUG (SyncWorker_5) [custom_components.vicare.utils] No burners found: 'ElectricalEnergySystem' object has no attribute 'burners' 2023-12-29 08:52:02.774 DEBUG (SyncWorker_5) [custom_components.vicare.utils] No compressors found: 'ElectricalEnergySystem' object has no attribute 'compressors' 2023-12-29 08:52:02.788 DEBUG (SyncWorker_12) [custom_components.vicare.utils] Feature not supported activate_onetimecharge: 'ElectricalEnergySystem' object has no attribute 'getOneTimeCharge' 2023-12-29 08:52:02.806 DEBUG (SyncWorker_12) [custom_components.vicare.utils] No circuits found: 'ElectricalEnergySystem' object has no attribute 'circuits' 2023-12-29 08:52:02.812 DEBUG (SyncWorker_12) [custom_components.vicare.utils] No circuits found: 'ElectricalEnergySystem' object has no attribute 'circuits' 2023-12-29 08:52:02.816 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported outside_temperature: 'ElectricalEnergySystem' object has no attribute 'getOutsideTemperature' 2023-12-29 08:52:02.816 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported return_temperature: 'ElectricalEnergySystem' object has no attribute 'getReturnTemperature' 2023-12-29 08:52:02.816 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported boiler_temperature: 'ElectricalEnergySystem' object has no attribute 'getBoilerTemperature' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported boiler_supply_temperature: 'ElectricalEnergySystem' object has no attribute 'getBoilerCommonSupplyTemperature' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported primary_circuit_supply_temperature: 'ElectricalEnergySystem' object has no attribute 'getSupplyTemperaturePrimaryCircuit' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported primary_circuit_return_temperature: 'ElectricalEnergySystem' object has no attribute 'getReturnTemperaturePrimaryCircuit' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported secondary_circuit_supply_temperature: 'ElectricalEnergySystem' object has no attribute 'getSupplyTemperatureSecondaryCircuit' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported secondary_circuit_return_temperature: 'ElectricalEnergySystem' object has no attribute 'getReturnTemperatureSecondaryCircuit' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_out_temperature: 'ElectricalEnergySystem' object has no attribute 'getDomesticHotWaterOutletTemperature' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_max_temperature: 'ElectricalEnergySystem' object has no attribute 'getDomesticHotWaterMaxTemperature' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_min_temperature: 'ElectricalEnergySystem' object has no attribute 'getDomesticHotWaterMinTemperature' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_consumption_today: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionDomesticHotWaterToday' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_week: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionDomesticHotWaterThisWeek' 2023-12-29 08:52:02.817 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_month: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionDomesticHotWaterThisMonth' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_consumption_heating_this_year: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionDomesticHotWaterThisYear' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_consumption_heating_today: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionHeatingToday' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_consumption_heating_this_week: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionHeatingThisWeek' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_consumption_heating_this_month: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionHeatingThisMonth' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_consumption_heating_this_year: 'ElectricalEnergySystem' object has no attribute 'getGasConsumptionHeatingThisYear' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentday: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionHeatingCurrentDay' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentmonth: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionHeatingCurrentMonth' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_summary_consumption_heating_currentyear: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionHeatingCurrentYear' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported gas_summary_consumption_heating_lastsevendays: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionHeatingLastSevenDays' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentday: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterCurrentDay' 2023-12-29 08:52:02.818 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentmonth: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterCurrentMonth' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_currentyear: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterCurrentYear' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported hotwater_gas_summary_consumption_heating_lastsevendays: 'ElectricalEnergySystem' object has no attribute 'getGasSummaryConsumptionDomesticHotWaterLastSevenDays' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentday: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionHeatingCurrentDay' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentmonth: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionHeatingCurrentMonth' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_summary_consumption_heating_currentyear: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionHeatingCurrentYear' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_summary_consumption_heating_lastsevendays: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionHeatingLastSevenDays' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentday: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterCurrentDay' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentmonth: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterCurrentMonth' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_dhw_summary_consumption_heating_currentyear: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterCurrentYear' 2023-12-29 08:52:02.819 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported energy_summary_dhw_consumption_heating_lastsevendays: 'ElectricalEnergySystem' object has no attribute 'getPowerSummaryConsumptionDomesticHotWaterLastSevenDays' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power_production_current: 'ElectricalEnergySystem' object has no attribute 'getPowerProductionCurrent' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power_production_today: 'ElectricalEnergySystem' object has no attribute 'getPowerProductionToday' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power_production_this_week: 'ElectricalEnergySystem' object has no attribute 'getPowerProductionThisWeek' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power_production_this_month: 'ElectricalEnergySystem' object has no attribute 'getPowerProductionThisMonth' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power_production_this_year: 'ElectricalEnergySystem' object has no attribute 'getPowerProductionThisYear' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported solar storage temperature: 'ElectricalEnergySystem' object has no attribute 'getSolarStorageTemperature' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported collector temperature: 'ElectricalEnergySystem' object has no attribute 'getSolarCollectorTemperature' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported solar power production today: 'ElectricalEnergySystem' object has no attribute 'getSolarPowerProductionToday' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported solar power production this week: 'ElectricalEnergySystem' object has no attribute 'getSolarPowerProductionThisWeek' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported solar power production this month: 'ElectricalEnergySystem' object has no attribute 'getSolarPowerProductionThisMonth' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported solar power production this year: 'ElectricalEnergySystem' object has no attribute 'getSolarPowerProductionThisYear' 2023-12-29 08:52:02.820 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power consumption today: 'ElectricalEnergySystem' object has no attribute 'getPowerConsumptionToday' 2023-12-29 08:52:02.821 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power consumption this week: 'ElectricalEnergySystem' object has no attribute 'getPowerConsumptionThisWeek' 2023-12-29 08:52:02.821 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power consumption this month: 'ElectricalEnergySystem' object has no attribute 'getPowerConsumptionThisMonth' 2023-12-29 08:52:02.821 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported power consumption this year: 'ElectricalEnergySystem' object has no attribute 'getPowerConsumptionThisYear' 2023-12-29 08:52:02.821 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported buffer top temperature: 'ElectricalEnergySystem' object has no attribute 'getBufferTopTemperature' 2023-12-29 08:52:02.821 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported buffer main temperature: 'ElectricalEnergySystem' object has no attribute 'getBufferMainTemperature' 2023-12-29 08:52:02.821 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported volumetric_flow: 'ElectricalEnergySystem' object has no attribute 'getVolumetricFlowReturn' 2023-12-29 08:52:02.834 DEBUG (SyncWorker_12) [custom_components.vicare.utils] No circuits found: 'ElectricalEnergySystem' object has no attribute 'circuits' 2023-12-29 08:52:03.064 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform deutschebahn is taking over 10 seconds. 2023-12-29 08:52:03.126 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported ess_state_of_charge 2023-12-29 08:52:03.126 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported ess_power 2023-12-29 08:52:03.126 DEBUG (SyncWorker_4) [custom_components.vicare.utils] No circuits found: 'ElectricalEnergySystem' object has no attribute 'circuits' 2023-12-29 08:52:03.127 DEBUG (SyncWorker_4) [custom_components.vicare.utils] No burners found: 'ElectricalEnergySystem' object has no attribute 'burners' 2023-12-29 08:52:03.127 DEBUG (SyncWorker_4) [custom_components.vicare.utils] No compressors found: 'ElectricalEnergySystem' object has no attribute 'compressors'

[CFenner]

2023-12-29 08:52:03.126 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported ess_state_of_charge
2023-12-29 08:52:03.126 DEBUG (SyncWorker_4) [custom_components.vicare.utils] Feature not supported ess_power

This means your device does not have the features I tried in the PR. Can you please share the diagnostic info of your setup? Go to the vicare device and click on the ... to download the file and share it here. In there all API values of your device will be visible. Then we can try to implement them.

[CHTHSCH]

Then we can try to implement them.

config_entry-vicare-3079563c2956b9bf2baf468d5f6606a3.json.txt

[CFenner]

Ok, so all of your three devices shows only the data point heating.boiler.serial, device.serial, device.productIdentification and device.messages.errors.raw. None of these are exposed as sensors in Home Assistant.

So, there are some limitations to the API I got to know. Some of the data points are only available in Germany (?) others you need to pay for. The Viessmann App is not constraint by this limitation, so you see more values in there. Looks like your devices do not expose anything expect their serials and error messages.

You could also try to access the API directly via Postman to double check this.

[CHTHSCH]

None of these are exposed as sensors in Home Assistant.

Thanks for your support and a Happy New Year

In May I will get the heat pump installed. Perhaps by that time I will see more, also from the Vitocharge VX3

[CFenner]

There is a 30 days free trial for the paid api, if this is interesting to you: https://developer.viessmann.com/start/pricing.html

Perfect to play around during the holidays 😉

[CHTHSCH]

There is a 30 days free trial for the paid api, if this is interesting to you: https://developer.viessmann.com/start/pricing.html

Perfect to play around during the holidays 😉

Subscribed to the Advanced option.

The integration now detected the Vitocharge VX3 and is displaying two entities.

Thanks for the hint. Although a bit expensive I gave it a try.

Is the any other log file, that you would like to get uploaded here? I attached the new info file

config_entry-vicare-3079563c2956b9bf2baf468d5f6606a3.json.txt

[CFenner]

No, that file is enough. Though I do not have enough understanding of the device. All three devices have the same data points. Is it a device that consists of multiple components? This is not an issue now, but once #96044 is ready, all devices will be displayed, leading to three devices with the same sensors. Not to mention that each device increases the scan interval for the API.

[CHTHSCH]

Though I do not have enough understanding of the device

The Vitocharge VX3 is a inverter with a variable number of battery modules. I think the TCU is the communication module and the HEMS the energy management module. According to my installer, only with the Vitocal 250A everything will be integrated in the HEMS, incl. the Viessmann Charging Station, which is originally from Mennekes. Physically, the Vitocharge VX3 is one device.

the detailed display in the ViCare app looks like this

That would mean, that

• The energy produced by the pannels
• The energy obtained from the grid or put in the grid
• The energy consumed
• The charging level of the battery modules should be available

[LarsTh86]

[cid:59274e50-2db2-44e2-9718-90f278c38e83] I didn´t work. I will tried later again

---

From: Thomas Schmidt @.> Sent: Friday, December 29, 2023 12:49 PM To: home-assistant/core @.> Cc: LarsTh86 @.>; Mention @.> Subject: Re: [home-assistant/core] ViCare Integration with Vitocharge VX3 electricity storage system - Bug or missing feature? (Issue #91417)

Though I do not have enough understanding of the device

The Vitocharge VX3 is a inverter with a variable number of battery modules. I think the TCU is the communication module and the HEMS the energy management module. According to my installer, only with the Vitocal 250A everything will be integrated in the HEMS, incl. the Viessmann Charging Station, which is originally from Mennekes. Physically, the Vitocharge VX3 is one device.

the detailed display in the ViCare app looks like this

IMG_2058.PNG (view on web)https://github.com/home-assistant/core/assets/50621196/4bb8c8d8-78bf-466b-9879-7835a8676f7d

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/91417#issuecomment-1871987489, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXE3ZKB4GOBJM7M6UCCVPWLYL2U45AVCNFSM6AAAAAAW6GQN5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZRHE4DONBYHE. You are receiving this because you were mentioned.Message ID: @.***>

[CFenner]

That would mean, that

• The energy produced by the pannels
• The energy obtained from the grid or put in the grid
• The energy consumed
• The charging level of the battery modules should be available

I added some more sensors, they're not labelled properly.

ess state pv state grid export pv production today pv power

[CHTHSCH]

Do I have to do the curl command again (in a different way)? to test what you have added?

If yes, what is the correct command and do I have to delete the vicare directory in custom_components before?

[CFenner]

Just run the command again and restart.

[CFenner]

@LarsTh86 remove the ~ at the end of the command, just specify the number of the PR.

PS: the screenshot shows your device serial number and I guess your street name.

[LarsTh86]

Thx for your advice. I get it installed but nevertheless all the new sensors are not available.

[LarsTh86]

I have found my mistake. I had manually updated the vicare integration but not all value. This was also my mistake. But i am still missing dhw temp2. https://api.viessmann.com/iot/v1/features/installations/xxxxxx/gateways/xxxxx/devices/0/features/heating.dhw.temperature.temp2

heating.dhw.temperature.temp2

[LarsTh86]

And this two commands for ventilation as a button-solution like dhw one-time-charging. That will be great.

https://api.viessmann.com/iot/v1/features/installations/xxxx/gateways/xxx/devices/0/features/ventilation.operating.programs.eco/commands/activate

https://api.viessmann.com/iot/v1/features/installations/xxxxx/gateways/xxxcc/devices/0/features/ventilation.operating.programs.comfort/commands/activate

[ViPtAd]

@LarsTh86 ventilation device was just added to the PyViCare library and can from now on be used in general. But like for Vitocharge, there are no sensors defined in HA yet. To be honest I do not know how the ventilation unit works and from the sample file it's not clear to me how the different programs interact.

Hi all, regarding ventilation I may give you some additional input. The information for the API obejects shall be found in the documentation (here):

• Vitovent 300 maybe connected to a heating device via bus (i assume modbus) and then over the vitoconnect opto2 it is accessible in the ViCare App / API
• Vitovent 300 may also be connected to a Vitoconnect V box directly, then nearly the same datapoints are shared as the Vitoair FS has
• Vitoair FS 330E has own tcu and connection and may be accessed via ViCare App / Api directly. In addition to Vitovent with box there are some more features available over API, e.g. automatic sensor mode

The basic operating mode is permanent mode, which means: Run this ventilation level forever. To select ventilation level by hand you need to set the operating mode to permanent: ventilation.operating.modes.active/commands/setMode

If the device is in permanent operating mode, you can set a level with ventilation.operating.modes.permanent.commands.setLevel.setValue The values are listed in ventilation.operating.modes.permanent.commands.setLevel.params.level.constraints.enum, from the json object:

          {
            "apiVersion": 1,
            "commands": {
              "setLevel": {
                "isExecutable": true,
                "name": "setLevel",
                "params": {
                  "level": {
                    "constraints": {
                      "enum": [
                        "levelOne",
                        "levelTwo",
                        "levelThree",
                        "levelFour"
                      ]
                    },
                    "required": true,
                    "type": "string"
                  }
                },
                "uri": "https://api.viessmann.com/iot/v1/features/installations/#######/gateways/################/devices/0/features/ventilation.operating.modes.permanent/commands/setLevel"
              }
            }

So when I enter the setLevel command with value levelOne, the ventilation device switches to Level 1.

Other modes available on the Vitoair FS are:

"permanent",
"ventilation",
"sensorOverride",
"sensorDriven"

Where permanent is the "manual" mode where yo can set a ventilation level directly, ventilation - not really sure about this, maybe this is the time scheduled mode (at least there is a smal clock/calendar icon in my ViCare App, when I enable the mode)? sensorOverride is the time schedule mode with sensor override, so that the ventilation levels from your schedule are slightly adjusted based on the time schedule and sensor data. sensorDriven shall be driven by sensor (CO2_Sensor).

The ventilation.operating.modes.active will display the actual ventilation mode. Setting the mode may be achieved by ventilation.operating.modes.active.commands.setMode.setValue - but this i was only able to test with permanent and ventilation operating mode.

In addition to this there are some modes which are time based. So the mode forcedLevelFour is kind of a boost mode, which will activate ventilation level four for a specific time (timeout). On my device it immediately enters this mode, when I enter a timeout value in minutes into the following object: ventilation.operating.programs.forcedLevelFour.commands.setTimeout.setValue.

I can test more commands on my device if you are interested.

Thank you for your good work so far!

[LarsTh86]

The sensor are not so important for the Ventilation. From my side it will sufficient, if I have button for eco-mode and comfort mode. Is this already integrated in vicare Integration for testing?

[CHTHSCH]

That would mean, that

• The energy produced by the pannels
• The energy obtained from the grid or put in the grid
• The energy consumed
• The charging level of the battery modules should be available

I added some more sensors, they're not labelled properly.

ess state pv state grid export pv production today pv power

So I now have 7 sensors in total, when they were created, they were not correctly names. I compared with the API documentation. I renamed the 7 sensors to what I think is the correct match with the API documentation

ess.power ess.operationState ess.stateOfCharge pcc.transfer.power.exchange photovoltaic.production.current photovoltaic.production.total photovoltaic.status

Are these the datapoints you implemented as sensors?

See also here: https://documentation.viessmann.com/static/iot/data-points

Perhaps you could correct the unit of measure for the ess.stateOfCharge to % and the default icon to a battery

[CFenner]

Perhaps you could correct the unit of measure for the ess.stateOfCharge to % and the default icon to a battery

This was already set to percent. Weird that it did not show up as such.

@CHTHSCH can you check the naming please. It's probably not reflected in your instance if your update the integration, but maybe your can check here. https://github.com/home-assistant/core/pull/106600/files#diff-4c4e86ac233d7d80489a4d73eee68b2924307b9fbef3486124dfbe5e99aebbe2

Icons I will check later.

[CHTHSCH]

@CHTHSCH can you check the naming please. It's probably not reflected in your instance if your update the integration, but maybe your can check here. https://github.com/home-assistant/core/pull/106600/files#diff-4c4e86ac233d7d80489a4d73eee68b2924307b9fbef3486124dfbe5e99aebbe2

Looks ok - when would this be available in the standard and how to move over?

Is deleting the custom component enough or do I need to remove and re-add the device as well?

[CFenner]

@CHTHSCH can you check the naming please. It's probably not reflected in your instance if your update the integration, but maybe your can check here. https://github.com/home-assistant/core/pull/106600/files#diff-4c4e86ac233d7d80489a4d73eee68b2924307b9fbef3486124dfbe5e99aebbe2

Looks ok - when would this be available in the standard and how to move over?

next mayor release if merged before. Voting on the PR would help.

Is deleting the custom component enough or do I need to remove and re-add the device as well?

yes

[CHTHSCH]

Voting on the PR would help.

How to?

[CFenner]

Voting on the PR would help.

How to?

On the PR click on review changes

[CHTHSCH]

Thank you for all the effort

[pduchnovsky]

The sensor are not so important for the Ventilation. From my side it will sufficient, if I have button for eco-mode and comfort mode. Is this already integrated in vicare Integration for testing?

Add intensive ventilation mode and it's golden :) For my simple use-case I'd just need ability of enabling and disabling intensive ventilation mode

[LarsTh86]

The sensor are not so important for the Ventil

### This would be great and perhaps the actual state as a sensor: viessmannapi.0.xxxxx.0.features.ventilation.operating.programs.active.properties.value.value https://api.viessmann.com/iot/v1/features/installations/xx/gateways/xx/devices/0/features/ventilation.operating.programs.active

Intensive Ventilation activate:

viessmannapi.0.xxx.0.features.ventilation.operating.programs.comfort.commands.activate https://api.viessmann.com/iot/v1/features/installations/xx/gateways/xxx/devices/0/features/ventilation.operating.programs.comfort/commands/activate

Intensive Ventilation deactivate:

viessmannapi.0.xx.0.features.ventilation.operating.programs.comfort.commands.deactivate https://api.viessmann.com/iot/v1/features/installations/xxx/gateways/xxxxx/devices/0/features/ventilation.operating.programs.comfort/commands/deactivate

The eco-modus would be really really nice-to-have:

Spar-Modus activate:

viessmannapi.0.xxxx.0.features.ventilation.operating.programs.eco.commands.activate https://api.viessmann.com/iot/v1/features/installations/xxx/gateways/xxx/devices/0/features/ventilation.operating.programs.eco/commands/activate

Spar-Modus deactivate:

viessmannapi.0.xxx.0.features.ventilation.operating.programs.eco.commands.deactivate https://api.viessmann.com/iot/v1/features/installations/xxxx/gateways/xxxxxx/devices/0/features/ventilation.operating.programs.eco/commands/deactivate

this would be really nice

[ViPtAd]

@pduchnovsky and @LarsTh86 : What devices do you own? A Vitovent 300 connected to a Heatpump which is connected to a Vitoconnect OPTO 2?

I got a Vitoair FS 300E and the response matches with the response provided in the repository. But there the commands under programs are not available.

May you post your response JSON here (or did you already and I was not able to find it?)?

I even checked the response JSON for a Vitovent 300-W with a connected Vitoconnect V and they have the similar response JSON as the Vitoair FS 300E, the programm commands are missing here, too.

Now I searched the repo response files for ventilation.operating.programs.comfort.commands and I had 0 hits (Suche "ventilation.operating.programs.comfort.commands" (0 Treffer in 0 Dateien von 27 gesucht)). It does not help the developers if they implement a ventilation program command and this is not working. As mentioned in my previous post the Viessmann ventilation system I have access to do not support the commands you requested. But I have no access to the combination Vitovent 300W connected via Vitoconnect OPTO 2 :-/

[pduchnovsky]

Vitovent 200-W connected to Vitocal 200-S which is then connected to Vitoconnect OPTO2 I haven't managed to get it running locally the last time I tried this which is why I am waiting for HA integration to work :)

[ViPtAd]

Even with HA integration this is not working "locally" because the API runs over Viessmann cloud server :)

back to the topic: Are you able to generate a response file from the HA integration for your device combo and post it here?

[pduchnovsky]

@ViPtAd tell me how :)