"ViCare" integration and "Vitodens 200-W B2HF 32kw" boiler, set_vicare_mode with dhwAndHeating or dhw no longer works

[evx73]

The problem

Until recently, the following worked with no issues:

action:
    service: vicare.set_vicare_mode
    data:
      entity_id: climate.vicare_heating
      vicare_mode: dhwAndHeating

action:
    service: vicare.set_vicare_mode
    data:
      entity_id: climate.vicare_heating
      vicare_mode: dhw

Now set_vicare_mode only accepts vicare_mode = "heating" or "standby"

What version of Home Assistant Core has the issue?

core-2023.1.2

What was the last working version of Home Assistant Core?

core-2023.1.2

What type of installation are you running?

Home Assistant Supervised

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?

No response

Additional information

No response

[home-assistant]

Hey there @oischinger, mind taking a look at this issue as it has been labeled with an integration (vicare) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of vicare can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign vicare Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

vicare documentation
vicare source
_{^{(message by IssueLinks)}}

[gras55]

Can confirm same issue with Vitodens 100w b1hf 32kw

[evx73]

My guess is that the ViCare API changed over the last few days. If it's confirmed, it is simply unacceptable that Viessmann changes the API in the middle of the winter.

The DHW worked based on the schedule today. I will test if it also works when in mode "standby".

[gras55]

Mine has not worked when trying to set dhwandheating

[stef-g]

Also does not work anymore for my Vitodens 300-W (new E3-platform based model). Looks like they might have changed the API as announced in November. But in the changelog they announced that they will inform about the exact date of implementation, which has not happened. Still says "The adjustments will go live in January 2023 (exact date will be added as soon as possible). From this date, you can only request the DHW operating mode for E3 using the described new way." (https://documentation.viessmann.com/static/changelog).

[evx73]

Confirming that the DHW run on schedule while the heating mode was set to "standby". See screenshot of temperature peaking to 80 C at 1:30 pm while the boiler was off (standby) since 10am.

This leads to the question, is there a way to change the DHW "operating mode" via the API? On the mobile app, I can see two modes, "Standard" and "Off".

[oischinger]

Please see this PyVicare issue: openviess/PyViCare#285
It needs to be fixed before we can fix the integration.

I created an HA Alert here: home-assistant/alerts.home-assistant.io#604

[phipz]

Can confirm the same issue for Vitodens 100. However, "vicare.set_vicare_mode" to "off" and "heating" still works. Cannot see or change water on/off anymore.

Nice side effect: Changing the current target temperature finally works from home assistant (didn't work before the API change)... Weird.

[gras55]

Is there any ETA for E3 to be integrated?

[gras55]

Having tried the new Vicare can confirm this is still not working

[issue-triage-workflows]

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.

[gras55]

Can confirm this still isn’t working!

[vac-pav]

This is still not working

[evx73]

I am using the following to enable and disable heating:

service: vicare.set_vicare_mode
  data:
    entity_id: climate.vicare_heating
    vicare_mode: heating

service: vicare.set_vicare_mode
  data:
    entity_id: climate.vicare_heating
    vicare_mode: standby

[Matz88]

The problem is that is not possible anymore to set independently the DHW off from heating

[vac-pav]

Is this really missing in API? Because from ViCare APP it is still possible to switch-off DHW - it has two states "Standard" and "Off"

[f1ux-capacitor]

Is this really missing in API? Because from ViCare APP it is still possible to switch-off DHW - it has two states "Standard" and "Off"

Not sure if this is useful info, but I have the 050w and was having an issue with my boiler where I couldn’t set DHW temp/mode in vicare app when using opentherm heating controls.

In vicare DHW also showed standard and off As the modes.

I got the viguide app and went through commissioning (without changing settings) and just resaved its current setup.

It fixed my issue plus now It shows options for off/comfort/eco , rather than standard/off.

[gras55]

It’s a shame as this was working really well prior the changes. Has the developers got any thoughts about it?

[f1ux-capacitor]

The documentation says this is the change to API

What is being adjusted?

The planned adjustments brings the following changes to our IoT features:

adjust heating.circuits.N.operating.modes.* by removing existent DHW dependencies
remove heating.circuits.N.operating.modes.dhw* operating modes
adjust heating.circuits.N.operating.modes.active to only show the following states for the “value” property: auto, heating, cooling, heatingCooling or testMode
The DHW operating can in future be requested through the following new features:

introduce heating.dhw.operating.modes.off >> Shows whether the DHW is off
adjust heating.dhw.operating.modes.active >> Shows the current DHW operating mode with the possible states for the “value” property: balanced, comfort, eco, off
This change only affects our Viessmann One Base (E3) control platform (wifi integrated devices). For legacy devices, i.e. using a Vitoconnect, there are no changes. However, this also means, depending on the device, requesting and changing the DHW operating mode differs.

[issue-triage-workflows]

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.

[gras55]

This has not been resolved

[issue-triage-workflows]

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.