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

[CFenner]

Select your ViCare device, click on ... and Download diagnostic information

[pduchnovsky]

config_entry-vicare-b3c098d8afd913ad522036c2a452e168.json.txt There you go, I dont see intensive ventilation however, just ventilation.operating.programs.levelFour but this one doesnt seem to be actual 'program' (as from the app pov where it has limits etc), intensive ventilation program has set time limit of 45 minutes for me in the heat pump settings for the ventilation so idk if enabling this mode would work the same as via vicare app. But anyway, enabling level 4, setting time limti and then enabling scheduled mode back would also work in HA I think. I'd just create some automation and trigger it via zigbee switch, this would allow me to put the switch(es) in bathroom(s) and kitchen and thus fully automate ventilation :)

[CHTHSCH]

Documentation of the various Data Points, also for Ventilation, can be found here https://documentation.viessmann.com/static/iot/data-points

[pduchnovsky]

Yeah so based on the above docu, this is missing for example in my diagnostics data: ventilation.operating.programs.intensive as well as ventilation.operating.programs.forcedLevelFour

[LarsTh86]

I have a Vitovent 200-W connected to Vitocal 200-S which is then connected to Vitoconnect OPTO2 and a VX3.

Intensiv Mode is not call Intensiv. Intensive mode can activate with this:

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

I used this already in iobroker and it works. But you have to activate and deactivate and after 2 hours. It will deactivate them self but this is configuration of the heating

If you want to use your statement with "programm" you can change schedule. But this is not so easy. This will be not only a button.

Also in my last comment a sensor for the state of Ventilation and energy safe mode.

[pduchnovsky]

@LarsTh86 kinda weird, in viessmann own documentation they mention ventilation.operating.programs.intensive Also, how to use this from HA right now, is there a way how to assign this to a button already or have to wait for integration ?

[LarsTh86]

@LarsTh86 kinda weird, in viessmann own documentation they mention ventilation.operating.programs.intensive Also, how to use this from HA right now, is there a way how to assign this to a button already or have to wait for integration ?

But this data point is for change a schedule with a json. I don't know, if is there a comfortable way to implementing this. But deactivate and activate the "comfort"-modus works. At the moment, i have an iobroker with link to ha and I implementing this so ha trigger an automation on iobroker which activate this data point and intensive modus switch on.

[SaschaWeitekemper]

Do I understand this in the right manner? Are you working on the integration of the Vitocharge VX3 and if everything goes well, will it be released with an update in May?

Thank you for your work.

[LarsTh86]

config_entry-vicare-a1c2d8d88e9e884a25242de183daac49.json.txt Configuration-file

This is active program, perhaps we can used it as Sensor or Diagontic like state of the Compressor

This is the intensiv-modus. For this will be a button like one-time-charging fine

This is the eco-modus. For this will be a button like one-time-charging also fine. But here you also need the butto to deactivate the modus

Is there something new about entries for ventilation? Perhaps we open a new ticket for ventilation.

Thx for your work.

KR

[CFenner]

I think having a switch would only be a short term solution. I would rather implement a fan entity, I guess. @LarsTh86 come to Discord so we can have a chat there (Hafenstrand).

[Benleni17]

This is good news that they are working on implementing vitovent ventilation units. Can we expect an implementation in HA Vicare with the Ventilation entity soon?

[konairius]

Should the VX3 work now?

I assumed #106600 would have added support. However, it doesn't show up after the update.

Is there so Cache I have to clear or something? I have tried to remove and re-add the Integration.

[CHTHSCH]

Should the VX3 work now?

I assumed #106600 would have added support. However, it doesn't show up after the update.

Is there so Cache I have to clear or something? I have tried to remove and re-add the Integration.

It is working in my instance. All data are updated and correct. I guess some sensors / data points are still missing to be implemented, but a big thanks to @CFenner for the work done 👏🏻👍🏻

Reminder: You need the subscription of the advanced features in the API.

Note: The documentation of the ViCare integration needs updating.

[CFenner]

Note: The documentation of the ViCare integration needs updating.

Could you suggest what should be changed in a PR?

[konairius]

@CHTHSCH Thank You, I seem to have missed the thing about the "advanced" API.

It is working fine now! Thank you for your Work!

[Benleni17]

This is good news that they are working on implementing vitovent ventilation units. Can we expect an implementation in HA Vicare with the Ventilation entity soon?

[ViPtAd]

Hi guys, regarding ventilation I think we should wait. There are two different ways of controlling the ventilation level (one for the old Vitovent devices connected over a heat pump and one for the OneBase components like VitoAir FS and Vitoconnect V devices). I am in contact with Viessmann and try to unify the commands / access for all ventilation devices. In my opinion it is double work if we implement now the "old" devices (which most of you seem to use) and ignore the new ones or implement both ways...

[LarsTh86]

But will Viessmann one way for both? Normally Viessmann is not so flexible. KR

[Benleni17]

Great. :) Thank you very much for your effort. I use the old version Vitovent 300 W from 2021, which is connected to my Vitocall 200s heat pump.

[CHTHSCH]

Note: The documentation of the ViCare integration needs updating.

Could you suggest what should be changed in a PR?

The work you did with respect to the Vitocharge or electric systems is not yet reflected here.

What device is supported? The remark, that the advanced API is necessary The meaning of the different data points (entities).

Thats what I meant.

[CHTHSCH]

I guess there are two data points, that perhaps can be implemented in a later release

✓ ess.operationState Shows the status of the electrical energy operation state, e.g. charge, discharge, standby ✓ ess.stateOfCharge Shows the state of charge battery in percent ✓ ess.power Shows the power of the battery in Watt ✗ ess.transfer.discharge.cumulated Shows the throughput of the electrical energy storage in different periods, e.g. current day, week, month

✓ pcc.transfer.consumption.total Shows the value of total consumption over the point of coupling in Wh ✓ pcc.transfer.power.exchange Shows the value power of exchange in Watt ✓ pcc.transfer.feedIn.total Shows the value of total feed in over the point of coupling in Wh

✗ photovoltaic.production.cumulated Shows the cumulated value of produced power of the photovoltaic in Wh, i.e. current day, week, month, year ✓ photovoltaic.production.total Shows statistics of the power production of the photovoltaic in kWh, i.e. days, weeks, months, years ✓ photovoltaic.production.current Shows the power which the photovoltaic panel affords in Watt ✓ photovoltaic.status Shows the status of the photovoltaic (nothing, ready, production, unknown)

Is that a correct interpretation? For those data points that can display by day, weeks, month, year, what timeframe is retrieved?

[CFenner]

Only the daily values are retrieved. My idea was that everything else can be calculated on the energy dashboard.

[CFenner]

@CHTHSCH lets continue the discussion from https://github.com/home-assistant/core/pull/113502#issuecomment-2001962903 here.

The third column would be interesting here.

[CHTHSCH]

Here we go. I think that looks correct.

With this and PR you will have implemented all data points from the API related to ESS, PCC and PHOTOVOLTAIC I guess, except photovoltaic.production.cumulated. Correct?

As for photovoltaic.production.total, you might also want to split in multiple entities for day, week, month, total, as you did for ess.transfer.discharge.cumulated in the other PR.

I will have the final step of my installation done end of May 2024, when the heat pump and the EV Charging Station will be installed. I may be able to better provide feedback and test things.

✓ ess.operationState Shows the status of the electrical energy operation state, e.g. charge, discharge, standby ✓ ess.stateOfCharge Shows the state of charge battery in percent ✓ ess.power Shows the power of the battery in Watt ✓ ess.transfer.discharge.cumulated Shows the throughput of the electrical energy storage in different periods, e.g. current day, week, month

✓ pcc.transfer.consumption.total Shows the value of total consumption over the point of coupling in Wh ✓ pcc.transfer.power.exchange Shows the value power of exchange in Watt ✓ pcc.transfer.feedIn.total Shows the value of total feed in over the point of coupling in Wh

✗ photovoltaic.production.cumulated Shows the cumulated value of produced power of the photovoltaic in Wh, i.e. current day, week, month, year ✓ photovoltaic.production.total Shows statistics of the power production of the photovoltaic in kWh, i.e. days, weeks, months, years ✓ photovoltaic.production.current Shows the power which the photovoltaic panel affords in Watt ✓ photovoltaic.status Shows the status of the photovoltaic (nothing, ready, production, unknown)

[ViPtAd]

Hey guys, big news around the corner: Regarding ventilation devices the features of the old and new devices will be made the same. Unfortunately will this be done in the API overhaul which they are working on at this moment - the planned release is in September 2024.

[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.

[LarsTh86]

Es sollte noch ein Update für die Ventilation folgenGesendet von Outlook für AndroidVon: issue-triage-workflows[bot] @.>Gesendet: Sonntag, Juli 7, 2024 1:05:53 PMAn: home-assistant/core @.>Cc: LarsTh86 @.>; Mention @.>Betreff: Re: [home-assistant/core] ViCare Integration with Vitocharge VX3 electricity storage system - Bug or missing feature? (Issue #91417) 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.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[Benleni17]

Thank you for your work. What is the current status of the implementation of Vitovent ventilation?

[CFenner]

@Benleni17 it's in review https://github.com/home-assistant/core/pull/114175

I think the issue title is fulfilled and we should close it. Please track ventilation device in https://github.com/home-assistant/core/issues/113865

@pduchnovsky @LarsTh86 @Benleni17 it would be welcome if you test the PR, as I do not own such a device.

[CFenner]

@home-assistant close