- platform: optolink
name: Return temperature
address: 0x0816
bytes: 2
div_ratio: 1
filters:
multiply: 0.1
accuracy_decimals: 1
unit_of_measurement: °C
device_class: temperature
update_interval: 72s
state_class: measurement
force_update: true
and
- platform: optolink
name: Exhaust temperature
address: 0x0808
bytes: 2
div_ratio: 1
filters:
multiply: 0.1
accuracy_decimals: 1
unit_of_measurement: °C
device_class: temperature
update_interval: 78s
state_class: measurement
force_update: true
Both of them were showing the same temperature(?)… If both of them were enabled, queue did reach value of 80 within an hour. If only one of them, it took couple of hours.
And now when I keep them disabled, queue’s value is between 0 and 6.
@adorobis could you tell me exactly how you enable party mode in your heater?
Is it just toggling party mode switch or something else?
On my side, whatever I do in HA it doesn’t activate party mode… Maybe because when doing it locally (at Viessmann controller) after pushing party mode button I need also to hit OK button to confirm room temperature setpoint…
And when it comes to presets and operation mode.
Do I need to change them both simultaneously? I’m asking because when I change operation mode locally - at heater’s controller, I don’t need to choose circulation loops. Question also applies to party modes.
forcedReduced and forcedNormal operation modes, what do they do?
Are presets (eco & comfort) to be activated by Economy and Party mode switches or the other way around? In my case, only switching to eco mode works.
Naming convention:
1/ Eco preset is reduced/night room temperature?
2/ Comfort preset is party mode?
But in normal operation I can see status:
while:
and
I’m sorry for so many questions but before setting up any automation, I need to know what I’m about to do
I just need to enable the toggle switch for party mode and that’s it. One thing I’ve observed is that it does not get activated immediately but after some time (like at least a minute). So the led for the party mode (and similarly for eco mode) on the controller are also turning on with some delay. Similarly if you enable this mode from the physical controller it will get reflected in HA after some time only.
This is probably not needed. Just wait for a moment and the party (or eco) mode will get activated with the temp that was set there before.
No, preset is only used to select the party or eco modes. Like the dedicated buttons on the physical controller. Specifics of those modes are that they will turn off with the next scheduled mode.
Operation mode is the main mode of the heater.
On the controller the top row is Operation mode, the bottom row is the Preset mode.
Let me address rest of the questions in next reply as I need to disconnect now
Edit: the rest of your questions:
In essence they do what the name suggests: they override the scheduled mode and go into day / heating mode (normal) or night / reduced temp (night) mode. End it stays this way until you change the operation mode to a different one.
It is called Eco and Comfort in HA just because there is only specified set of presets that can be used in HA, if you want to add it to the climate entity. Otherwise I would call it Party and Eco. And as explained above - those presets are turn off automatically on the next scheduled mode change or based on timer (which can be set in the device settings - refer to the installer’s manual of Viessmann heater).
I have not seen such status in my unit: 773 therefore it is not mapped to a text status. You can change this mapping in esphome config of this sensor. I have also used the status names to have them in line with they official Vicare integration and I’ve mapped them according to my unit behaviour.
Hope this clarifies a bit more but I agree that this is overall a bit confusing setup. Some of it is simply caused by very specific names of operation and preset modes in HA.
Once again, thanks very much for taking a time and explaining.
In my case, Party mode M2 switch started working when I adjusted in HA “Party Floor Temperature Setpoint” and the same applies to Party mode switch after touching “Party Temperature Setpoint”. So, something was related to those temperatures set points…
BTW, do you have a list or know a website where I can find all available addresses used in opentherm/viessmann heater? I would like to map that 773 status plus find address where solar panels’ temperature is presented (solar panels controller is connected to Viessmann boiler)…
Solar collector temperature (5272) [Solar collector temperature~0x6564 (SInt)] HIDDEN:(“Solar collector temperature”>{‘CompanyId’: ‘24’, ‘Unit’: ‘Grad C’, ‘DataType’: ‘Float’, ‘Stepping’: 0.1, ‘LowerBorder’: -20.0, ‘UpperBorder’: 250.0} OR “Solar collector temperature”<{‘CompanyId’: ‘24’, ‘Unit’: ‘Grad C’, ‘DataType’: ‘Float’, ‘Stepping’: 0.1, ‘LowerBorder’: -20.0, ‘UpperBorder’: 250.0} OR “Status solar collector sensor”=“Not available”)
Solar Recharge suppression (5273) [SolarNachlade~0x6551 (Byte)]
Solar solar pump (5274) [SolarPumpe~0x6552 (Byte)]
Solar operating hours (5277) [SolarStunden~0x6568 (Int)]
Solar heat quantity (5279) [SolarWaerme~0x6560 (Int4)]
I came up with following:
binary_sensor:
- platform: optolink
name: Solar Circulation Pump
address: 0x6552
update_interval: 145s
device_class: power
sensor:
- platform: optolink
name: Solar Storage temperature
address: 0x6566
bytes: 2
div_ratio: 1
filters:
multiply: 0.1
accuracy_decimals: 1
unit_of_measurement: °C
device_class: temperature
update_interval: 185s
state_class: measurement
force_update: true
- platform: optolink
name: Solar Collector temperature
address: 0x6564
bytes: 2
div_ratio: 1
filters:
multiply: 0.1
accuracy_decimals: 1
unit_of_measurement: °C
device_class: temperature
update_interval: 170s
state_class: measurement
force_update: true
- platform: optolink
name: Solar Operating Hours
address: 0x6568
bytes: 4
device_class: duration
unit_of_measurement: h
state_class: total_increasing
icon: mdi:counter
update_interval: 1800s
filters:
- lambda: return x / 3600;
accuracy_decimals: 1
force_update: true
- platform: optolink
name: Solar Heat Quantity
address: 0x6560
bytes: 4
unit_of_measurement: J
update_interval: 493s
state_class: measurement
force_update: true
But I don’t see anywhere in those files number of bytes and/or div_ratio information. I copied configuration of similar items but I don’t think Solar Heat Quantity works
At least some of information is displayed (storage is shared with gas boiler):
I am migrating my smart home controller from FHEM to Home Assistant, the Wemos D1 Mini was working for years, I have reflashed it with ESP Home to use the Optolink module.
Our Viessmann heating is the model V200KO2B, is there a pre-configured yaml which can be used instead of manually write it from the raw addresses? I saw two files here, but it is not clear to me which model is supported
Now, the first difficulty came up in RS components I can’t find a SIR 204 EVL led, and the phototransistor SFH309 is only delivered in 2000 pieces.
I was wondering, does someone have an amazon link of an equivalent of each with a lower head count? I don’t mind to buy a few of each but 2000 is ridiculous
I tried to install in the esp32 the code from the pastebin, but I get so many errors when it is verifying to install that I’m wondering if this code is still up to date.
@adorobis can you please confirm if this code is the one you are still using in you boiler?
