4. HVAC systems - ramses-rf/ramses_cc GitHub Wiki

The ramses_cc integration supports HVAC systems (HRUs, CVEs, and PIVs), such as from Itho Daalderop and Orcon. Support extends to their remotes and sensors.

These notes apply to release 0.59.0 and later.

Seeing up the integration for HVAC devices is fully covered in Configuration, step 4

HVAC devices that are not showing up in the Device Scan, may be added as 'orphans' for Ramses RF to create them. Add the device IDs to your System schema as follows:

orphans_hvac:
  - 30:111111
  - 32:333333
  - 32:555555
  - 32:666666

Beware: For your system, a 29: may be a fan, and not a remote, or a 32: may be a sensor and not a fan, etc..

To control HVAC systems from Home Assistant, remote faking can be used. To do so, the Config Schema needs to be extended. An example is shown below:

"28:111111": { class: REM,  faked: true, scheme: orcon }  # NB: `scheme` is not yet implemented
"29:123456":
  class: REM
  faked: True
  commands:
    low:    ' I --- 29:123456 --:------ 29:123456 22F1 003 000107'
    medium: ' I --- 29:123456 --:------ 29:123456 22F1 003 000207'
    high:   ' I --- 29:123456 --:------ 29:123456 22F1 003 000307'

The extra options here are faked, scheme, and commands.

• faked: a boolean indicator used to set the device as faked - this is required to send messages from Ramses RF.
• commands: allows for the user to explicitly specify commands that can be send using the faked remote if scheme cannot be used
• scheme: used to provide the set of commands from a remote, which can vary by manufacturer/model

To discover/add commands from your physical remote, a service call can be used. In Home Assistant, go to Tools, tab Actions and select the service call Remote: Learn Command. In UI-mode select a target remote and fill in a timeout. You may switch to the YAML-mode to paste this example or check your details:

action: ramses_cc.learn_command
data:
  command: Auto
  timeout: 30
target:
  entity_id: remote.29_123456

With everything filled in, click Perform Action. ramses_cc will now start to listen for the command. Press the button on your remote that you want your faked remote to learn and you will see a green checkmark appear. The command is now learned and will be registered to your entity.

Similar to command learning there is a 'command send' service call. In Home Assistant, go to Tools, tab Actions and select the service call Remote: Send Command. In UI-mode select your target remote from the list of remotes. You may switch to YAML-mode to check the details, for example:

action: ramses_cc.send_command
target:
  entity_id: remote.29_123456
data:
  command: Auto
  num_repeats: 3
  delay_secs: 0.05

The last two lines are optional.

Click the Perform Action button and ramses_cc will send the command named Auto. Note that capitalisation is important, as the command name should match. If your faked remote is defined as bound: 29:123456 under your FAN in the Scheme, as in the example above, it should respond to the command. To see which commands are supported for your remote, go to Tools, tab States and select your remote entity. Available commands appear under State Attributes (as far as you previously defined them in your Schema).

Older ramses_cc releases used a different format where you manually had to enter your device, but HomeAssistant now presents all remotes for you to pick one.

• to be added

Supported fans return data structures (31DA and 31D9) that contain climate information like temperature, humidity and CO₂ levels.

• You can collect the relevant items from your HVAC device on a custom deshboard, effectively hiding unused items that you always see in the Climate or Remote entity under Integrations > Ramses RF.

Read more about schemes (command sets tied to a particular Fan model) and how to customise the command set in this segment.