Vicare Vitovent Ventilation isnt displayed

[Benleni17]

The problem

my Vitovent 300W ventilation isnt listed as an entity

What version of Home Assistant Core has the issue?

core-2024.9.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Viessmann Vicare

Link to integration documentation on our website

No response

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[bot]]

Hey there @cfenner, 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 Renames 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.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[CFenner]

Hey, please share the diagnostics and log file.

[CFenner]

Hey @Benleni17, could you share the diagnostics file?

[Benleni17]

Hello, thanks for helping. How does it work only for the integration vicare?

[CFenner]

@Benleni17 select "devices & services" in the HA settings and then "vicare", click on the ... and select download diagnostic information.

[Benleni17]

config_entry-vicare-01J8PC8V04X7R2YFHA0EC39TM5 (1).json

Ventilation is showed, but not addet as entity in Vicare

[CFenner]

What kind of device is that. Looks like a heat pump.

[Benleni17]

The Heatpump is a Vitocal 200s and the ventilation Vitovent 300W

[CFenner]

But the Vitovent 300W is no standalone device from an API perspective, right? It's somehow exposed via the heat pump via mod bus?

[Benleni17]

Yes. The ventilation is integrated into the control of the heat pump via Modbus.

This is only possible because the standalone Vitovent control system is not cloud compatible

[Benleni17]

Do you need anything else?

[Benleni17]

Aber der Vitovent 300W ist aus API-Sicht kein eigenständiges Gerät, oder? Er wird irgendwie über den Modbus der Wärmepumpe angebunden?

Moin,

Can I still help or is my problem unsolvable?

Grüße Benedikt

[Benleni17]

Aber der Vitovent 300W ist aus API-Sicht kein eigenständiges Gerät, oder? Er wird irgendwie über den Modbus der Wärmepumpe angebunden?

Hello Christopher, can you still help me?

Benedikt

[CFenner]

Only if you can develop in Python. Currently, I don't have the time to look into it.

[Benleni17]

Only if you can develop in Python. Currently, I don't have the time to look into it.

Okay, I respect that. If there’s any way I can support you, just let me know. I’ll wait for your response.

[klappsepp]

Hello, i have the same problem. I Use also the Heatpump Vitocal 200s and the ventilation Vitovent 300-f. config_entry-vicare-c1c1fb38fe05eeedc83a42f778a5ac09.json

[Benleni17]

Hallo, ich habe das gleiche Problem. Ich verwende auch die Wärmepumpe Vitocal 200s und die Lüftung Vitovent 300-f. config_entry-vicare-c1c1fb38fe05eeedc83a42f778a5ac09.json

That reassures me to know the problem isn’t just on my end. I hope we’ll receive a solution soon.

[aliex87]

I have the same challenge with my Viessmann setup. I have several devices all connected behind the primary gateway (Heat Pump), but I can’t see or control them in Home Assistant: Vitocal 151A (fully visible) None of these are visable: Vitoair FS 300E, Vitotrol 300-E Remote Control, E3 Repeater, 5x E3 Room Sensors

Any guidance on how to get these recognised or integrated would be greatly appreciated as they're visable in the log! config_entry-vicare-01J948YYMEGM9VPDWVHMRK0HCA.json

[CFenner]

@aliex87 your room devices are only usable with a advanced API plan. The ViAir in your case is a separate device and could be supported already. Unfortunately the role / model does not match and therefore it is not detected as such.

https://github.com/openviess/PyViCare/blob/master/PyViCare/PyViCareDeviceConfig.py#L86C31-L86C69

We would need to extend the library..

[aliex87]

Thanks, @CFenner! I’ve reached out to Viessmann, as both the Electric and Advanced API plans aren’t available for me to proceed with. Unfortunately, I get the message ‘The selected product is currently not available in your country,’ which I’d be willing to subscribe to if they were available in the UK. As I understand, my setup is one of only two in the UK that combines both the Heat Pump and the Vitoair FS 300E.

Currently, the Vitoair isn’t operating quite as expected, with room devices not influencing any operations (e.g., humidity levels triggering airflow steps). There’s conflicting documentation from Viessmann, so my hope was that by integrating the ventilation system and, ideally, climate sensors into Home Assistant, I could set up triggers and automations alongside other devices in my home—like increasing airflow when bathroom humidity rises or when the kitchen hob is activated. I’m actively working with Viessmann UK, who have hopefully forwarded my request for advanced API access, but progress is slow.

I previously tried using a custom ViCare integration, but given the role/model isn’t in the library, that approach didn’t work either. If I can support or test anything, I’d be more than happy to help wherever needed!

[Benleni17]

@aliex87deine Raumgeräte sind nur mit einem erweiterten API-Plan nutzbar. Das ViAir ist in deinem Fall ein separates Gerät und könnte bereits unterstützt werden. Leider stimmt die Rolle/das Modell nicht überein und daher wird es nicht als solches erkannt.

https://github.com/openviess/PyViCare/blob/master/PyViCare/PyViCareDeviceConfig.py#L86C31-L86C69

Wir müssten die Bibliothek erweitern.

i‘m happy to help as well, just let me know how…

[LarsTh86]

Is now ventilation available? I still waiting for this support

[Benleni17]

@aliex87 your room devices are only usable with a advanced API plan. The ViAir in your case is a separate device and could be supported already. Unfortunately the role / model does not match and therefore it is not detected as such.

https://github.com/openviess/PyViCare/blob/master/PyViCare/PyViCareDeviceConfig.py#L86C31-L86C69

We would need to extend the library..

Do I understand correctly that the Vitovent is not listed as a device_type?

# see: https://vitodata300.viessmann.com/vd300/ApplicationHelp/VD300/1031_de_DE/Ger%C3%A4teliste.html
def asAutoDetectDevice(self):
    device_types = [
        (self.asFuelCell, r"Vitovalor|Vitocharge|Vitoblo", []),
        (self.asGazBoiler, r"Vitodens|VScotH|Vitocrossal|VDensH|Vitopend|VPendH|OT_Heating_System", ["type:boiler"]),
        (self.asHeatPump, r"Vitocal|VBC70|V200WO1A|CU401B", ["type:heatpump"]),
        (self.asOilBoiler, r"Vitoladens|Vitoradial|Vitorondens|VPlusH|V200KW2_6", []),
        (self.asPelletsBoiler, r"Vitoligno|Ecotronic|VBC550P", []),
        (self.asElectricalEnergySystem, r"E3_VitoCharge_03", ["type:ees"]),
        (self.asVentilation, r"E3_ViAir", ["type:ventilation"]),
        (self.asVentilation, r"E3_VitoPure", ["type:ventilation;purifier"]),
        (self.asRadiatorActuator, r"E3_RadiatorActuator", ["type:radiator"]),
        (self.asRoomSensor, r"E3_RoomSensor", ["type:climateSensor"]),
        (self.asGateway, r"E3_TCU41_x04", ["type:gateway;TCU100"]),
        (self.asGateway, r"E3_TCU19_x05", ["type:gateway;TCU200"]),
        (self.asGateway, r"E3_TCU10_x07", ["type:gateway;TCU300"]),
        (self.asGateway, r"Heatbox1", ["type:gateway;VitoconnectOpto1"]),
        (self.asGateway, r"Heatbox2", ["type:gateway;VitoconnectOpto2/OT2"])
    ]

[CFenner]

@aliex87 the ViAir should already be detected if you set heating type to auto. Please verify if that is the case.

@Benleni17

Do I understand correctly that the Vitovent is not listed as a device_type?

This is correct and the vitovent is from the api perspective to standalone device. With https://github.com/openviess/PyViCare/pull/360 we could check if a device supports ventilation and activate the fan control for the heating device.

[Benleni17]

@aliex87heating typeWenn Sie auf eingestellt haben, sollte das ViAir bereits erkannt werden auto. Bitte überprüfen Sie, ob dies der Fall ist.

@Benleni17

Verstehe ich das richtig, dass der Vitovent nicht als Gerätetyp aufgeführt ist?

Dies ist korrekt und der Vitovent ist aus API-Sicht ein Standalone-Gerät. Mit openviess/PyViCare#360 könnten wir prüfen, ob ein Gerät Lüftung unterstützt und die Lüftersteuerung für das Heizgerät aktivieren.

That makes sense. As far as I can tell, I’m not the only one with a Vitovent system, so I’m happy to help for everyone’s benefit. If you could explain how I can test my system, that would be great, as I’m not very experienced with development.

[aliex87]

Thank you, @CFenner I must’ve removed and re-added the integration multiple times before, but not recently. It’s now finally exposed the second device: E3_ViAir_300F_01, along with the following new entities, which are functioning well:

preset_modes:

• permanent
• ventilation
• sensor_driven
• sensor_override percentage: 75 percentage_step: 25 preset_mode: sensor_driven friendly_name: Ventilation supported_features: 9

While I’m glad to have these entities, I was hoping for a few more. The logs indicate that some may be deprecated. Ideally, it would be helpful to see entities for both of the following, which are invaluable for specific ventilation scenarios:

• ventilation.quickmodes.forcedLevelFour: Perfect for triggering a ventilation burst when there’s an increase in humidity or other ventilation needs.
• ventilation.quickmodes.silent: Useful for quiet operation when necessary. (aware I can setup an automation/script as a workaround)

Additionally, there are quite a few temperature stats within the device itself, though I can’t find any documentation on these being exposed via the Viessmann API. Are these API-dependent, or could they be exposed as well?

Thanks for your assistance!

[CFenner]

@aliex87 great that this works for you. Unfortunately there seems to be no further datapoint beside the quick modes that we could leverage from the free API. I got myself a Vitopure lately and will try to make the quick modes work.

[aliex87]

Thanks, @CFenner It’s definitely a nice-to-have, so no worries. I’ll look into gaining access to the advanced API and any additional ViCare devices or sensors that might then become available. For now, having the ventilation exposed is a big step forward – should keep me quiet for a while! Good luck with the Vitopure, and let me know how the quick modes work out!

[CFenner]

@Benleni17 @klappsepp @LarsTh86 I prepared the feature to detect ventilation support with https://github.com/openviess/PyViCare/pull/360.

Now the question would be how to integrate it into HA.

1. The climate entity also supports a fan_mode, so on the entity that controls the heating temperature, you could also set a mode for the fan (e.g. auto, off, silent, ..)
2. There is a fan entity that supports preset_mode and also percentage, so with this entity you would be able to set the fan intensity beside the mode.

What would be the more appropriate way to display the feature? Note that the second one is already implemented for standalone ventilation units.

[Benleni17]

@Benleni17 @klappsepp @LarsTh86 I prepared the feature to detect ventilation support with openviess/PyViCare#360.

Now the question would be how to integrate it into HA.

1. The climate entity also supports a fan_mode, so on the entity that controls the heating temperature, you could also set a mode for the fan (e.g. auto, off, silent, ..)
2. There is a fan entity that supports preset_mode and also percentage, so with this entity you would be able to set the fan intensity beside the mode.

What would be the more appropriate way to display the feature? Note that the second one is already implemented for standalone ventilation units.

Thanks for the information! I prefer Option 2, as it offers more flexibility for adjusting fan intensity and is already implemented for standalone ventilation devices.

If there’s already an entity that supports fan, I’d like to build on that to use preset_mode and percentage for controlling fan intensity. This way, we can manage the fan mode and intensity independently from the heating system.

How can I get the entity displayed?