Set silent mode for Vaillant aroTHERM #1365

Kifo2023 · 2024-10-25T11:40:42Z

Kifo2023
Oct 25, 2024

My Vaillant aroTHERM plus with VRC 720 SensoComfort and VR 71 Controller is running 24/7 in silent mode at 50% most of the year to keep it quiet and to keep then number of daily starts low.

However, on very cold days I will need increase the output. I would like to control this via my home automation system.
But so far I could not get access to the silent mode percentage via ebusd. No control files seem to know this parameter.

As a work around I could also deactivate the silent mode by manipulating the silentTimer, but this seems to be not so easy, too.
I already included a sielntTimer section in my 15.ctlv2.csv file, but I could not even read the timer data. Ebusd tells "element not found".

Does anybody have experience with this topic?

dylan09 · 2024-10-25T15:36:00Z

dylan09
Oct 25, 2024

I have a register CompressorSilentOperationLevel in file 08.hmu00.csv (ID is FF3428). Maybe this is the right place to change. Couldn`t test it myself. Didn't find a way to change the silent.Timer configuration via eBus.

Could you test if that's the right register. And give some feedback?

0 replies

dylan09 · 2024-10-25T15:37:40Z

dylan09
Oct 25, 2024

One question to the timer section for the sensoComfort: Could help someone in changing this timers through eBus?
I have tried to change the definition to writable. But was not able to set some new values.

0 replies

Kifo2023 · 2024-10-27T07:23:48Z

Kifo2023
Oct 27, 2024
Author

I tried to include the CompressorSilentOperationLevel parameterin my file 08.hmu.csv, but probably I did not interpret the advise about how to work on the configuration file right.

I put a new line under
"# Heat pump configuration menu values"
with the following content:
r,,CompressorSilentOperationLevel,,,,,FF3428
and tried also
r,,CompressorSilentOperationLevel,,,,,FF3428,,,UCH,,,Percent,

but both do not work. The ebusd log file sais:
2024-10-27 08:12:24.492 [update error] unable to parse read hmu CompressorSilentOperationLevel from 3108b51a0605ff32ff3428 / 02ff01: ERR: invalid position
2024-10-27 08:12:24.492 [main error] read hmu CompressorSilentOperationLevel: decode ERR: invalid position

Can you help me to put it right?

3 replies

chrizzzp Oct 28, 2024

@Kifo2023

08.hmu.csv:

*r,,,,,,B51A,05,,,IGN:3,,,,,,,,,,,,,,,,,,,,,
*w,,,,,,B51A,06,,,,,,,,,,,,,,,,,,,,,,,,
r;w,,CompressorSilentOperationLevel,,,,,FF3428,,,percent0,,,Compressor Silent Operation level,,,,,,,,,,,,,,,,,,

The template percent0 is defined as:
percent0,UCH,,%,

The SilentOperationLevel can be set only in a limit range (40 - 60% on my split system).

@dylan09

I created two scripts in Home Assistant which activate/deactivate the 'SilentOperation' by adjusting the silent mode timers in the VRC720 via MQTT/ebusd:

to turn silent mode off:
("Flüstermodus" = silent mode)

mqtt_wp_flustermodus_aus:
  alias: 'MQTT: WP Flüstermodus Aus'
  sequence:
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Monday/set
      payload: 0;1;00:00;00:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Tuesday/set
      payload: 0;1;00:00;00:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Wednesday/set
      payload: 0;1;00:00;00:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Thursday/set
      payload: 0;1;00:00;00:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Friday/set
      payload: 0;1;00:00;00:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Saturday/set
      payload: 0;1;00:00;00:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Sunday/set
      payload: 0;1;00:00;00:00;ff ff
  mode: single
  icon: mdi:heat-pump

to turn silent mode on:

mqtt_wp_flustermodus_an:
  alias: 'MQTT: WP Flüstermodus An'
  sequence:
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Monday/set
      payload: 0;1;00:00;24:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Tuesday/set
      payload: 0;1;00:00;24:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Wednesday/set
      payload: 0;1;00:00;24:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Thursday/set
      payload: 0;1;00:00;24:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Friday/set
      payload: 0;1;00:00;24:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Saturday/set
      payload: 0;1;00:00;24:00;ff ff
  - service: mqtt.publish
    metadata: {}
    data:
      qos: '2'
      retain: false
      topic: ebusd/ctlv2/silentTimer.Sunday/set
      payload: 0;1;00:00;24:00;ff ff
  mode: single
  icon: mdi:heat-pump

Kifo2023 Oct 28, 2024
Author

r;w,,CompressorSilentOperationLevel,,,,,FF3428,,,percent0,,,Compressor Silent Operation level,,,,,,,,,,,,,,,,,,
The SilentOperationLevel can be set only in a limit range (40 - 60% on my split system).
@chrizzzp Perfect, this works nicely. Thanks a lot!

dylan09 Oct 28, 2024

@chrizzzp Great tip. Sometimes professionally blinkered 🧐 I am using MQTT commands from Node-Red already to get some register values at regular intervals.

Currently away from home. Not brave enough to try it from remote. But reading registers is working.

Kifo2023 · 2024-10-28T12:18:49Z

Kifo2023
Oct 28, 2024
Author

@chrizzzp I try to modify the noiseReductionTimer via ebusctl commands.
In my 15.ctlv2.csv file I have the following section:
# Flüsterbetrieb,,,,,,,,,,,,, *r,,,,,,B524,03000002,,,IGN:1,,,whether timeslot is valid *w,,,,,,B524,04000002,,,,,, r;w,,noiseReductionTimer.Monday,Zeitfenster Flüsterbetrieb Montag,,,,00,,,slot1-3,,, r;w,,noiseReductionTimer.Tuesday,Zeitfenster Flüsterbetrieb Dienstag,,,,01,,,slot1-3,,, r;w,,noiseReductionTimer.Wednesday,Zeitfenster Flüsterbetrieb Mittwoch,,,,02,,,slot1-3,,, r;w,,noiseReductionTimer.Thursday,Zeitfenster Flüsterbetrieb Donnerstag,,,,03,,,slot1-3,,, r;w,,noiseReductionTimer.Friday,Zeitfenster Flüsterbetrieb Freitag,,,,04,,,slot1-3,,, r;w,,noiseReductionTimer.Saturday,Zeitfenster Flüsterbetrieb Samstag,,,,05,,,slot1-3,,, r;w,,noiseReductionTimer.Sunday,Zeitfenster Flüsterbetrieb Sonntag,,,,06,,,slot1-3,,,
However, I cannot read (or write) any timer like this:
ebusctl read -c ctlv2 "noiseReductionTimer.Monday"

I always get "element not found" as reply.
What's wrong here?

2 replies

chrizzzp Oct 28, 2024

@Kifo2023 I use slightly different definitions. Reading and writing is a bit different (maybe not the most elegant way, but it works...)

# timers silent mode,,,,,,,,,,,,,
*r,,,,,,B555,a50004,,,,,,
*w,,,,,,B555,a60004,,,,,,
r,,silentTimer.Config,timer Configuration(static atm? describes featue set?),,,B555,a30004,,,HEX:9,,,Configuration
r,,silentTimer.TimeSlotsPerWeekday,Configured slot count for each weekday,,,B555,a40004,,,slotCountWeek,,,Amount of configured slots per weekday
r,,silentTimer.Monday,timer monday read,,,,00,index,m,UCH,,,,,,rTimeSlotWithoutTemp
w,,silentTimer.Monday,timer monday write,,,,00,,,wTimeSlotWithoutTemp,,,
r,,silentTimer.Tuesday,timer tuesday read,,,,01,index,m,UCH,,,,,,rTimeSlotWithoutTemp
w,,silentTimer.Tuesday,timer tuesday write,,,,01,,,wTimeSlotWithoutTemp,,,
r,,silentTimer.Wednesday,timer wednesday read,,,,02,index,m,UCH,,,,,,rTimeSlotWithoutTemp
w,,silentTimer.Wednesday,timer wednesday write,,,,02,,,wTimeSlotWithoutTemp,,,
r,,silentTimer.Thursday,timer thursday read,,,,03,index,m,UCH,,,,,,rTimeSlotWithoutTemp
w,,silentTimer.Thursday,timer thursday write,,,,03,,,wTimeSlotWithoutTemp,,,
r,,silentTimer.Friday,timer friday read,,,,04,index,m,UCH,,,,,,rTimeSlotWithoutTemp
w,,silentTimer.Friday,timer friday write,,,,04,,,wTimeSlotWithoutTemp,,,
r,,silentTimer.Saturday,timer saturday read,,,,05,index,m,UCH,,,,,,rTimeSlotWithoutTemp
w,,silentTimer.Saturday,timer saturday write,,,,05,,,wTimeSlotWithoutTemp,,,
r,,silentTimer.Sunday,timer sunday read,,,,06,index,m,UCH,,,,,,rTimeSlotWithoutTemp
w,,silentTimer.Sunday,timer sunday write,,,,06,,,wTimeSlotWithoutTemp,,,

The following templates are required:

slotIndex,UCH,,,array index for the zones. Array Index start at 0 for the first element
slotCount,UCH,,,Number of total slots in the array. May be Zero.
startTime,HTM,,,Starting time of the timeframe
endTime,HTM,,,Ending time of the timeframe
slotTimeFrame,startTime;endTime,,,Timeslot from/until
wTimeSlotWithoutTemp,slotIndex;slotCount;slotTimeFrame;HEX:2,,,Complete slot for writing the time table settings without a temperature.
rTimeSlotWithoutTemp,IGN:1;slotTimeFrame;IGN:2,,,Complete slot for reading the time table settings without a temperature.

Reading of time slots:

the index (-i) specifies the time slot

ebusctl r -f -i 0 -c ctlv2 silentTimer.Monday

Writing specific time slots:

writing of time slots without temperature, payload definition: slot_index;total_slotnumber_day;start_time;end_time;ff ff

ebusctl w -c ctlv2 silentTimer.Monday "0;1;00:00;24:00;ff ff"

IMPORTANT:
All defined time slots of the day have to be written, even if only one slot is updated!
Failure to write all time slots will result in the new settings not applied to the regulator.

chrizzzp Oct 28, 2024

@Kifo2023

> # Flüsterbetrieb,,,,,,,,,,,,, *r,,,,,,B524,03000002,,,IGN:1,,,whether timeslot is valid *w,,,,,,B524,04000002,,,,,,

BTW, this should be in separate lines:

# Flüsterbetrieb,,,,,,,,,,,,,
*r,,,,,,B524,03000002,,,IGN:1,,,whether timeslot is valid
*w,,,,,,B524,04000002,,,,,,

But I think the PBSB/ addresses are not correct for the VRC720... should be B555.

Kifo2023 · 2024-10-28T14:06:38Z

Kifo2023
Oct 28, 2024
Author

Hm, seems my VRC 720 does not like this configuration.
I put the 7 new lines into the _templates_csv and your # timers silent mode,,,,,,,,,,,,, block into my 15.ctlv2.csv and restarted ebusd.
But still get the "element not found" error when reading the new parameters. Sh...

7 replies

Kifo2023 Oct 28, 2024
Author

How can I check if
*r,,,,,,B555,a50004,,,,,,
is right for my VRC 720?
Anything I should see in the log file?

chrizzzp Oct 28, 2024

@Kifo2023 You should check the log carefully after restart of ebusd if any errors occur during reading the CSV files while the first messages come in. Ebusd will stop reading the CSV if the first error appears and you will not have the complete definitions in operation.

What do you get with ebusctl f silentTimer (or ebusctl f noiseReductionTimer)?

Kifo2023 Oct 28, 2024
Author

OK, I am getting further. Checking the log for errors was the right hint. There was an error a few lines above the silentTimer block. After fixing it, I can now read the timers as you proposed above.
E.g.: ebusctl read -f -i 0 -c ctlv2 silentTimer.Monday results in 00:00;24:00
as the silent mode is active all day currently.
And ebusctl read -f -i 2 -c ctlv2 silentTimer.TimeSlotsPerWeekday results in 1;1;1;1;1;1;1 as I have one time slot per day.

Writing seems a bit more tricky.
When trying ebusctl w -c ctlv2 silentTimer.Monday "0;1;15:00;19:00;ff ff" I get done,
but checking the timer then with ebusctl read -f -i 0 -c ctlv2 silentTimer.Monday gives again 00:00;24:00.
Seems I make a mistake with this writing, right?

chrizzzp Oct 28, 2024

@Kifo2023
Does writing values via ebusctl generally work for other settings (read-only mode of ebusd disabled)?

When trying ebusctl w -c ctlv2 silentTimer.Monday "0;1;15:00;19:00;ff ff" I get done,
but checking the timer then with ebusctl read -f -i 0 -c ctlv2 silentTimer.Monday gives again 00:00;24:00.

Write command looks OK to me. Did you force-read to check after writing?

Double check the template is correct (field type HEX:2 is important, should not be IGN:2!):

wTimeSlotWithoutTemp,slotIndex;slotCount;slotTimeFrame;HEX:2,,,Complete slot for writing the time table settings without a temperature

Maybe try a 3-slot definition and check if it is correctly written:

ebusctl write -c ctlv2 silenttimer.Friday "0;3;00:20;02:20;ff ff"
ebusctl write -c ctlv2 silenttimer.Friday "1;3;06:30;08:30;ff ff"
ebusctl write -c ctlv2 silenttimer.Friday "2;3;10:40;23:40;ff ff"

Kifo2023 Oct 28, 2024
Author

Writing works fine for other parameters, so this is not my roadblock.
I checked the timer for Monday with -f option. Also looked on my VRC 720. No effect.
Finally I checked the field type. It was on IGN:2. Now with HEX:2 ... WORKS!
You really have a good feeling (and understanding) where the issues can be.
Thanks a lot!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Set silent mode for Vaillant aroTHERM #1365

{{title}}

Replies: 5 comments 12 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Set silent mode for Vaillant aroTHERM #1365

Replies: 5 comments · 12 replies

Kifo2023 Oct 27, 2024 Author

Kifo2023 Oct 28, 2024 Author

Kifo2023 Oct 28, 2024 Author

Kifo2023 Oct 28, 2024 Author

Kifo2023 Oct 28, 2024 Author

Kifo2023 Oct 28, 2024 Author

Kifo2023 Oct 28, 2024 Author

Replies: 5 comments 12 replies

Kifo2023
Oct 27, 2024
Author

Kifo2023 Oct 28, 2024
Author

Kifo2023
Oct 28, 2024
Author

Kifo2023
Oct 28, 2024
Author

Kifo2023 Oct 28, 2024
Author

Kifo2023 Oct 28, 2024
Author

Kifo2023 Oct 28, 2024
Author