Do you have any other device or indication that your PIV should be able to provide any of the fields in the RP message ?
From the RP packet you can see it contains little info. The FF and 7F bytes all stand for unavailable. So that leaves only 21 and 18 (halfway) for ramses_rf to make sense of. Iāve seen other simple fans reply in the same way. Perhaps you can add an optional sensor?
Do you receive 22F4 or 31D9 messages from the PIV? (assuming Nuaire DRI-ECO) That might give speed feedback in Ramses RF.
Spent quite some time watching and capturing all of the traffic to and from the PIV. This is the total of what I know:
The device and IDs are as follows:
18:238432 The Ramses gateway
30:095696 Nuaire Eco PIV with heater
32:123456 Nuaire 4 button remote (Faked)
The PIV sends out 31D9 packet every 30 mins but it is always the same and doesnāt change with the mode of the PIV.
2026-02-15T00:11:30.994415 "I 147 30:095696 --:------ 30:095696 31D9 017 2100FF0000000000000000000000000000"
Every 3.5 mins the PIV sends out a 1F09 info packet but again it is always the same and doesnāt change with the mode of the PIV.
2026-02-15T11:20:16.289245 " I --- 30:095696 --:------ 30:095696 1F09 003 000820"
2026-02-15T11:23:44.299158 " I --- 30:095696 --:------ 30:095696 1F09 003 000820"
2026-02-15T11:27:12.309088 " I --- 30:095696 --:------ 30:095696 1F09 003 000820"
2026-02-15T11:30:40.319032 " I --- 30:095696 --:------ 30:095696 1F09 003 000820"
Periodically the Ramses gateways sends out a series of RQ messages to the PIV. One of them is a 22F4:
2026-02-15T11:19:53.942383 "RQ --- 18:238432 30:095696 --:------ 22F8 001 00"
2026-02-15T11:19:57.021370 "RQ --- 18:238432 30:095696 --:------ 2210 001 00"
2026-02-15T11:20:16.264133 "RQ --- 18:238432 30:095696 --:------ 22E0 001 00"
2026-02-15T11:20:19.637543 "RQ --- 18:238432 30:095696 --:------ 22E5 001 00"
2026-02-15T11:20:23.222192 "RQ --- 18:238432 30:095696 --:------ 22E9 001 00"
2026-02-15T11:20:26.392396 "RQ --- 18:238432 30:095696 --:------ 22F2 001 00"
2026-02-15T11:20:29.561984 "RQ --- 18:238432 30:095696 --:------ 22F4 001 00"
2026-02-15T11:20:32.805880 "RQ --- 18:238432 30:095696 --:------ 313E 001 00"
2026-02-15T11:20:36.013101 "RQ --- 18:238432 30:095696 --:------ 3222 001 00"
The PIV doesnāt seem to respond in any way to any of the requests.
When a remote command is sent using the spoofed 4 button remote (22F1) The PIV responds with a info packet (31DA):
2026-02-15T11:50:43.018459 " I --- 32:123456 30:095696 --:------ 22F1 003 00090A" # Heater Off
2026-02-15T11:50:43.044434 " I --- 30:095696 --:------ 30:095696 31DA 030 21EF007FFFEFEF7FFF7FFF7FFF7FFF0002EF18FFFF000000EF7FFF7FFF00"
2026-02-15T11:51:15.690172 " I --- 32:123456 30:095696 --:------ 22F1 003 000A0A" # Heater Auto
2026-02-15T11:51:15.716014 " I --- 30:095696 --:------ 30:095696 31DA 030 21EF007FFFEFEF7FFF7FFF7FFF7FFF0002EF18FFFF000000EF7FFF7FFF00"
2026-02-15T11:51:52.782262 " I --- 32:123456 30:095696 --:------ 22F1 003 00020A" # Fan Normal
2026-02-15T11:51:52.808762 " I --- 30:095696 --:------ 30:095696 31DA 030 21EF007FFFEFEF7FFF7FFF7FFF7FFF0002EF18FFFF000000EF7FFF7FFF00"
2026-02-15T11:55:54.904035 " I --- 32:123456 30:095696 --:------ 22F1 003 00030A" # Fan Boost
2026-02-15T11:55:54.929962 " I --- 30:095696 --:------ 30:095696 31DA 030 21EF007FFFEFEF7FFF7FFF7FFF7FFF0002EF18FFFF000000EF7FFF7FFF00"
The 31DA responses are always identical and so it seems the fan doesnāt report any info in them.
So it seems as I have everything set up, the PIV is never sending out any useful information. Iām assuming there is no need for binding the Ramses controller to the PIV which Iāve missed somehow?
One other thing Iāve noticed - whenever I send a command from the spoofed 4 button remote, the gateway seems to send it 3 times. Not sure if this is intended/expected behaviour? Iām assuming it might be to overcome lost packets?
I also have a Nuaire Drimaster PIV (DRI-ECO-HEAT-HC) and Iām interested to see what can be achieved.
I note the Nuaire Drimaster Remote Monitoring Device (DRI-ECO-RM) provides filter status and run-time hours. I donāt have this device myself, the picture is taken from their datasheet.
Itās unclear which HVAC codes they map too, but if that is known then entities could be created.
Note that @zxdavb previously observed that a packet is sent every 30 minutes by the Nuaire Drimaster PIV described as āBRDG-02JAS01ā by its 10E0 packet.
Some progress investigating what happens, see 0.53.3: `remote.py` Error sending command Ā· Issue #455 Ā· ramses-rf/ramses_cc Ā· GitHub
To be on the safe side, use the ramses_cc.send_command Action instead of the HA built-in remote.send_command
This is interesting - I didnāt know this device existed. Iām guessing this is going to be like the CO2 and humidity sensors where we wonāt know how to spoof them until someone buys one and captures the packets and shares them. All of these accessories for the Nuaire PIVs are crazy prices.
I hadnāt spotted the 10E0 packet before, but having just searched for it in the packet logs, my PIV seems to only send one once a day:
2026-02-13T13:51:32.944882 060 I --- 30:095696 63:262142 --:------ 10E0 038 000001C90023006CFEFEFFFFFFFF1C0707E5425244472D30324A415330310000000000000000
2026-02-14T13:51:34.369835 051 I --- 30:095696 63:262142 --:------ 10E0 038 000001C90023006CFEFEFFFFFFFF1C0707E5425244472D30324A415330310000000000000000
2026-02-15T13:51:36.044494 056 I --- 30:095696 63:262142 --:------ 10E0 038 000001C90023006CFEFEFFFFFFFF1C0707E5425244472D30324A415330310000000000000000
Iāve no idea what the 63:262142 device is. The only other packets to/from that device code seem to be coming from the my Ramses RF bridge which sends one every 5 minutes:
2026-02-13T13:45:15.641935 000 I --- 18:238432 63:262142 --:------ 7FFF 023 0011019C573FA70733304339204930333A303031323934
2026-02-13T13:45:20.442186 000 I --- 18:238432 63:262142 --:------ 7FFF 023 0011019C573FBA9033304339204930333A303031323935
2026-02-13T13:45:25.405922 000 I --- 18:238432 63:262142 --:------ 7FFF 023 0011019C573FCE1A33304339204930333A303031323936
I have them both.
I have temperature and humidity and CO2 showing in home assistant.
They were working in my old house and I did send some stuff to David.
Iāve got a new PIV setup in my new house but not been able to get the remote faking working this time round.
It took me several attempts to get the faked remote to bind with the PIV. It just seemed to work on about the 5th attempt and I donāt think I did anything different.
I might be wrong but as far as I understood it, the missing piece of the puzzle for the temp/humidity and CO2 sensors was what they send to the PIV when they are being bound. Knowing this weād be able to fake those devices and send readings from other HA devices to the PIV as if they were proper Nuaire sensors.
That is correct. This binding sequence needs to be captured, preferably a couple of time to make sure it is always identical. We need to see the whole series, not just the reply.
From the Wiki:
Successful bindings will have an
I-W-Isequence in the packet log similar to:
> ~ cat config/packet.log | grep ' 1FC9 '
15:27:30.775 000 I --- 03:123456 --:------ 03:123456 1FC9 012 0030C90DE240001FC90DE240
15:27:30.789 032 W --- 01:145038 03:123456 --:------ 1FC9 006 00230906368E
15:27:30.794 000 I --- 03:123456 01:145038 --:------ 1FC9 001 00
stevieb12345 Please send me the packets you previously sent to David; I donāt have access to his archive. Fine to use a DM for that.
Egbert
Happy to test this should we get the packet info. Big thanks to @EgbertB and @stevieb12345 in advance!
New Ramses RF (pre)release is out, with remote.send_packet fix; select 0.54.3 from the HACS Download dropdown.
Stevieās packets are in ramses_rf PR 480.
They report temp and hum from an ECO-RM.
It will take some time to see this in the integration as we are working on some background stuff.
1 Like
The next pre-release of Ramses RF 0.55.0 is out.
User who want to help in testing the improved non-blocking library are invited to install it from the HACS Redownload dropdown. Already works fine here at home.
When installed version 0.55 I get the following error during startup.
Going back to 0.54.3 all works fine againā¦
2026-02-28 15:10:49.013 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry RAMSES RF for ramses_cc
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 762, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ramses_cc/__init__.py", line 154, in async_setup_entry
await coordinator.async_setup()
File "/config/custom_components/ramses_cc/coordinator.py", line 244, in async_setup
await self.client.start(**start_kwargs)
File "/usr/local/lib/python3.13/site-packages/ramses_rf/gateway.py", line 306, in start
load_schema(self, known_list=self._include, **self._schema) # create faked too
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/schemas.py", line 366, in load_schema
load_tcs(gwy, ctl_id, schema) # type: ignore[arg-type]
~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/schemas.py", line 408, in load_tcs
ctl.tcs._update_schema(**schema)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/system/heat.py", line 1025, in _update_schema
[self.get_htg_zone(idx, **s) for idx, s in _schema.items()]
~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/system/heat.py", line 562, in get_htg_zone
zon = zone_factory(self, zone_idx, msg=msg, **schema) # type: ignore[unreachable]
File "/usr/local/lib/python3.13/site-packages/ramses_rf/system/zones.py", line 1041, in zone_factory
zon: DhwZone | Zone = best_zon_class( # type: ignore[type-var]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...<4 lines>...
**schema,
~~~~~~~~~
).create_from_schema(tcs, idx, **schema)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/system/zones.py", line 120, in create_from_schema
zon._update_schema(**schema)
~~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/system/zones.py", line 539, in _update_schema
self._sensor = self._gwy.get_device(dev_id, parent=self, is_sensor=True)
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/gateway.py", line 612, in get_device
dev.set_parent(parent, child_id=child_id, is_sensor=is_sensor)
~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/entity_base.py", line 1523, in set_parent
parent, child_id = self._get_parent(
~~~~~~~~~~~~~~~~^
parent, child_id=child_id, is_sensor=is_sensor
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/ramses_rf/entity_base.py", line 1463, in _get_parent
raise TypeError(
...<2 lines>...
)
TypeError: for Parent 01:007149_02 (ELE): not a valid parent (it must be ('DhwZone', 'System', 'Evohome', 'UfhController', 'Zone', 'ElecZone', 'MixZone', 'RadZone', 'UfhZone', 'ValZone'))
Thanks for reporting.
Please add your system schema in issue 0.55.0 evohome TypeError Ā· Issue #508 Ā· ramses-rf/ramses_cc Ā· GitHub
Ramses RF pre-release 0.55.2 is now in HACS, with a confirmed fix for the aforementioned issue. Youāre welcome to test it on more systems, before we push it to all users.
1 Like
Hello evebody i am a new user of ramses-cf but i have a couple issues and i think the better for fix it is describe my system:
Home Assistan OS: RPi 5
Evo Home
6 x HR92
Relay box type: R9H911RF3000 (maybe my problem came of this)
Relay box: BDR91 (not conected yet i can conect but i dont make the test yet)
Ramses_ESP: i buy it last week version 0.55
Boiler type: very simple, closed contacts, boiler send hot water to my radiators
i conected the USB to my RPi and im not an advanced user, i pluged and smashed next button for a ābasicā configuration and well, all the items are detected by the integration the evohome, the relay box, and the HR92 but this last apear on home assistant as sensors not like a TRV and i can,t control them.
My itention is simple control all my TRV and set the temperatures and see when the relay its closed to can manage how many time are heating up the system.
i read on HACS ramses cant work with R3 protocol and this is the protocol that use my relay box, if i change to a BDR91 relay box the HR92 apear like TRV can be controled?
the problem is this relay box or are some āsolutionā to use this relay box?
Thank you all and excuse my bad english, im not be very good student when i was young and this is the result, i dont like to use google translator.
Thank for you responses and your time.
to talk
It looks like you answered your own question, the R9H911RF3000 isnāt supported by RAMSES is my understanding and yes the BDR91 will provide the control that you require. Here is what my system looks like in HA.
1 Like
Thanks for your quickly response, i apreciate a lot, i change the relay box this morning and, yes it appear a relay in home assistant like i wanted, but the other issue is the HR92 doesnt appear like TRV and i dont know how fix that, reset the cache integration? reinstal de integration ?
Than you a lot for your time and your help