Ramses_rf /Nuaire PIV

Third party integrations
1

I have been running Ramses_rf in Home Assistant for some months with a Honeywell Evohome system. I am not an IT or coding whizz but found the installation and configuration process logical and successful. Recently I have been trying to integrate a Nuaire PIV system and found the exact opposite. I’ve scoured the forums and Wikis but am floundering. I’m hoping for some guidance.

I’m running Ramses_rf 0.60.4 and Home Assistant core-2026.9.2 . Everything is fully updated as of 15/9/26. The PIV is a DRI-ECO-HEAT-HC Nuaire PIV Unit with Heater & RF.

Ramses has detected a number of IDs from the PIV but I’m afraid I don’t understand them. I have created a dummy remote 32:111111 and put it in the schema. However discovery insists it is a FAN. Also I’m pretty sure 30:080071 is a FAN and have amended the schema accordingly but discovery insists it is a CTL.

Discovery also detected 30:077002 as CTL. I have skipped that for now.

This is the message I get on startup:-

RAMSES CC: Schema mismatches detected

**1 class mismatch(es):**

* 30:080071 — schema=FAN, discovery=CTL

**1 missing \_class:**

* 32:111111 — discovery=FAN

**1 weak signal device(s):**

* 13:001788 — RSSI -77 dBm (weak)

I have not yet been able to bind the faked remote to the fan, awaiting a ramses_rf bug fix, but this confusion will not help I’m sure.

I have cleared the cache and re-installed ramses-rf a couple of times but get the same confusing results. Any guidance to resolve would be very much appreciated.

Here is my current ramses-rf schema with the obvious (to me) Evohome stuff removed.:-

30:077002: >-

Likely CTL. zone 00. codes: 10E0, 1F09, 31D9, 31DA. RSSI -83.

(auto-generated — do not edit)

30:080071: >-

Likely CTL. zone 00. codes: 10D0, 10E0, 1F09, 2411, 3150. RSSI -34.

(auto-generated — do not edit)

34:023769: >-

Likely RND (confidence: medium). codes: 30C9. RSSI -65. (auto-generated — do

not edit)

32:111111: >-

Likely FAN. may also be DIS (31DA is sent by both). codes: 2411.

(auto-generated — do not edit)

01:213901:

_class: CTL

_owner: me

_name: Hall

12:253992:

_class: THM

_owner: me

_skipped: true

30:077002:

_owner: me

_skipped: true

30:080071:

_bound: 32:111111

_class: FAN

_owner: me

18:104912:

_class: HGI

_owner: me

32:111111:

_owner: me

class: REM

commands:

battery_ok: ’ I — 32:111111 --:------ 32:111111 1060 003 00FF01’

boost: ’ I — 32:111111 30:080071 --:------ 22F1 003 00030A’

get_fan_info: RQ — 32:111111 30:080071 --:------ 31DA 001 00

heater_auto: ’ I — 32:111111 30:080071 --:------ 22F1 003 000A0A’

heater_off: ’ I — 32:111111 30:080071 --:------ 22F1 003 00090A’

normal: ’ I — 32:111111 30:080071 --:------ 22F1 003 00020A’

faked: true

2

If this helps - here is my schema. I have the same Nuaire unit with the 4 button remote switch. It was set up a good while ago though and I’ve forgotten the details, but remote triggering of Boost/Auto via faked remote has been robust.

In the Schema
30:075494 is the fan
32:206615 is the real remote
32:222222 is faked remote
18:137759 is the usb controller

I have just installed 0.60.6 from 060.1 and now i have started getting regular Ramses_CC notifications about Schema mismatches - although everything appears to still work fine - this is a bit annoying and no idea how to stop it.

_owner: me
device_comments:
  30:075494: >-
    Likely FAN. may also be DIS (31DA is sent by both). belongs to 32:206615.
    zone 00. codes: 10D0, 1F09, 22F1, 2411, 31DA. RSSI -57. (auto-generated — do
    not edit)
  32:206615: 'Likely REM. codes: 22F1. (auto-generated — do not edit)'
  18:137759: 'Likely HGI. codes: 10D0, 2411. (auto-generated — do not edit)'
  32:222222: >-
    Likely FAN (confidence: medium). may also be DIS (31DA is sent by both).
    codes: 10E0. (auto-generated — do not edit)
30:075494:
  _class: FAN
32:206615:
  _class: REM
  _commands:
    boost: ' I --- 32:206615 30:075494 --:------ 22F1 003 00030A'
    heater_auto: ' I --- 32:206615 30:075494 --:------ 22F1 003 000A0A'
    heater_off: ' I --- 32:206615 30:075494 --:------ 22F1 003 00090A'
    normal: ' I --- 32:206615 30:075494 --:------ 22F1 003 00020A'
  _faked: true
32:222222:
  _commands:
    boost: ' I --- 32:222222 30:075494 --:------ 22F1 003 00030A'
    heater_auto: ' I --- 32:222222 30:075494 --:------ 22F1 003 000A0A'
    heater_off: ' I --- 32:222222 30:075494 --:------ 22F1 003 00090A'
    normal: ' I --- 32:222222 30:075494 --:------ 22F1 003 00020A'
18:137759:
  _class: HGI
  _comment: 'Supports: usb (don''t edit here — adapt with the Pool Management config)'
  _owner: me
  _preferred_type: usb
3

Thank you Arwyn, very helpful. I have realised there are several errors in the schema I posted. I will correct those right away. I’ve downloaded the development version 0.60.6 and will try to install it.

Done, now to try binding again.

4

Well that was fun. To get the faked remote to bind I installed the pre-release ramses_rf 0.60.6 to get round the binding bug.That worked but device discovery gave me very confusing results. So, having bound the faked remote I re-installed 0.60.4 and it worked. I was able to get Boost, Auto Heater, Heater Off and Normal control from the faked remote. I’ve got another one to install. I hope I can remember what I did.