Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm

JoepW · September 12, 2025, 9:09am

Thanks for the replies and suggestions.

The indents are there in my setup and I have now replaced all double quotes by single quotes and the indents are now shown correctly here.

This is my “System schema and known devices” entry now:

'18:262143':
  alias: Ramses Bridge
  class: HGI
'01:094566':
  alias: Evohome Controller
  class: CTL
'13:215304':
  alias: Evohome Remeha Relais
  class: BDR
'34:041481':
  alias: Gang round wireless
  class: THM
'34:052245':
  alias: Badkamer round wireless
  class: THM
'34:227157':
  alias: Keuken round wireless
  class: THM
'34:227159':
  alias: Woonkamer round wireless
  class: THM
'34:232285':
  alias: Joep round wireless
  class: THM
'34:238783':
  alias: Dorien round wireless
  class: THM
'34:238785':
  alias: Hal round wireless
  class: THM
'34:238787':
  alias: Slaapkamer round wireless
  class: THM
'04:007750':
  alias: Badkamer 2 radiator klep
  class: TRV
'04:019489':
  alias: Zolder radiator klep
  class: TRV
'04:019491':
  alias: Handdoeken radiator klep
  class: TRV
'04:025691':
  alias: Toilet radiator klep
  class: TRV
'04:025733':
  alias: Dorien radiator klep
  class: TRV
'04:025739':
  alias: Joep radiator klep
  class: TRV
'04:157354':
  alias: Hal radiator klep
  class: TRV
'04:157356':
  alias: Slaapkamer radiator klep
  class: TRV
'04:157358':
  alias: Gang radiator klep
  class: TRV

And everything works fine. The Zones are all visible as devices and the Controls, Sensors and Diagnostic entities and connected devices are all visible in the Device view.

I want to switch “Accept packets from known devices IDs only” on. When I do that I have to clear the cache and reload Ramses RF. All fine so far.

But after doing this I loose some entities. For instance for Badkamer I loose the Heat Demand Sensor (sensor.01_094566_02_heat_demand). This Zone is connected through my HCC100 and gave before switching on “Accept packets from known devices IDs only” the correct values.
For other Zones (non-floor ones) and all devices I loose Battery info.

I’m sure I’m doing something wrong, but what…

Willem70 · September 12, 2025, 1:38pm

The _02 could indicate that there was a second 01_094566 CTL device at some point, or at least named 01_094566_02. And now it’s not, and it no longer accepts packets…
Check your device list, and also entitly list and check the names and status. There might even be a (new) sensor.01_094566_heat_demand available.

JoepW · September 12, 2025, 1:52pm

The _01, _02 and so on are the EvoHome zone numbers.

Willem70 · September 12, 2025, 2:06pm

Ah I see, I don’t use zones myself. Do you see any warnings or debug info in the logs ?

stevieb12345 · September 12, 2025, 2:15pm

Hi. It’s been awhile since I’ve been in this thread as everything has been working fine.

I used to have the my Nuaire PIV working with a faked remote so I could automate it. I moved house two years ago and have never gotten round to making the remote work again. A lot has changed since I started using this component and the Wiki can be hard to follow. Does anyone have a step by step to getting the fake remote working with my PIV again?

orphans_hvac:
  - "30:072506"
  - "32:123456"
  - "32:166025"
  - "32:168240"
  - "32:172522"

"01:044181":
  class: controller
"03:000001":
  faked: true
"03:000002":
  faked: true
"03:000003":
  faked: true
"03:000004":
  faked: true
"03:000005":
  faked: true
"03:000006":
  faked: true
"04:038015":
  class: radiator_valve
"04:090189":
  class: radiator_valve
"04:112546":
  class: radiator_valve
"04:190691":
  class: radiator_valve
"04:198483":
  class: radiator_valve
"04:198485":
  class: radiator_valve
"04:198487":
  class: radiator_valve
"04:257002":
  class: radiator_valve
"04:418104":
  class: radiator_valve
"13:128343":
  class: electrical_relay
"18:135447":
  class: HGI
"30:072506":
  class: FAN
"32:123456":
  class: REM
  faked: true
  commands:
    boost: " I --- 32:123456 30:072506 --:------ 22F1 003 00030A"
    normal: " I --- 32:123456 30:072506 --:------ 22F1 003 00020A"
"32:166025":
  class: CO2
"32:168240":
  class: HUM
"32:172522":
  class: REM

JoepW · September 13, 2025, 6:42am

The only error I see is this one:

Logger: homeassistant.util.loop
Source: util/loop.py:137
First occurred: 08:44:48 (5 occurrences)
Last logged: 08:44:48

Detected blocking call to glob with args (‘/dev/rfcomm*’,) inside the event loop by custom integration ‘ramses_cc’ at custom_components/ramses_cc/broker.py, line 146: await self.client.start(cached_packets=cached_packets()) (offender: /usr/local/lib/python3.13/site-packages/ramses_tx/transport.py, line 166: devices.update(glob.glob(items[1] + ““))), please create a bug report at GitHub · Where software is built For developers, please see Blocking operations with asyncio | Home Assistant Developer Docs Traceback (most recent call last): File “”, line 198, in _run_module_as_main File “”, line 88, in _run_code File “/usr/src/homeassistant/homeassistant/main.py”, line 223, in sys.exit(main()) File “/usr/src/homeassistant/homeassistant/main.py”, line 209, in main exit_code = runner.run(runtime_conf) File “/usr/src/homeassistant/homeassistant/runner.py”, line 156, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 712, in run_until_complete self.run_forever() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 683, in run_forever self._run_once() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 2050, in _run_once handle._run() File “/usr/local/lib/python3.13/asyncio/events.py”, line 89, in _run self._context.run(self._callback, self._args) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 896, in async_setup_locked await self.async_setup(hass, integration=integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 662, in async_setup await self.__async_setup_with_context(hass, integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 751, in __async_setup_with_context result = await component.async_setup_entry(hass, self) File “/config/custom_components/ramses_cc/init.py”, line 94, in async_setup_entry await broker.async_setup() File “/config/custom_components/ramses_cc/broker.py”, line 146, in async_setup await self.client.start(cached_packets=cached_packets())
Detected blocking call to iglob with args ('/dev/rfcomm’,) inside the event loop by custom integration ‘ramses_cc’ at custom_components/ramses_cc/broker.py, line 146: await self.client.start(cached_packets=cached_packets()) (offender: /usr/local/lib/python3.13/glob.py, line 31: return list(iglob(pathname, root_dir=root_dir, dir_fd=dir_fd, recursive=recursive,), please create a bug report at GitHub · Where software is built For developers, please see Blocking operations with asyncio | Home Assistant Developer Docs Traceback (most recent call last): File “”, line 198, in _run_module_as_main File “”, line 88, in _run_code File “/usr/src/homeassistant/homeassistant/main.py”, line 223, in sys.exit(main()) File “/usr/src/homeassistant/homeassistant/main.py”, line 209, in main exit_code = runner.run(runtime_conf) File “/usr/src/homeassistant/homeassistant/runner.py”, line 156, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 712, in run_until_complete self.run_forever() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 683, in run_forever self._run_once() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 2050, in _run_once handle._run() File “/usr/local/lib/python3.13/asyncio/events.py”, line 89, in _run self._context.run(self._callback, self._args) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 896, in async_setup_locked await self.async_setup(hass, integration=integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 662, in async_setup await self.__async_setup_with_context(hass, integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 751, in __async_setup_with_context result = await component.async_setup_entry(hass, self) File “/config/custom_components/ramses_cc/init.py”, line 94, in async_setup_entry await broker.async_setup() File “/config/custom_components/ramses_cc/broker.py”, line 146, in async_setup await self.client.start(cached_packets=cached_packets())
Detected blocking call to scandir with args (‘/dev’,) inside the event loop by custom integration ‘ramses_cc’ at custom_components/ramses_cc/broker.py, line 146: await self.client.start(cached_packets=cached_packets()) (offender: /usr/local/lib/python3.13/glob.py, line 170: with os.scandir(arg) as it:), please create a bug report at GitHub · Where software is built For developers, please see Blocking operations with asyncio | Home Assistant Developer Docs Traceback (most recent call last): File “”, line 198, in _run_module_as_main File “”, line 88, in _run_code File “/usr/src/homeassistant/homeassistant/main.py”, line 223, in sys.exit(main()) File “/usr/src/homeassistant/homeassistant/main.py”, line 209, in main exit_code = runner.run(runtime_conf) File “/usr/src/homeassistant/homeassistant/runner.py”, line 156, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 712, in run_until_complete self.run_forever() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 683, in run_forever self._run_once() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 2050, in _run_once handle._run() File “/usr/local/lib/python3.13/asyncio/events.py”, line 89, in _run self._context.run(self._callback, self._args) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 896, in async_setup_locked await self.async_setup(hass, integration=integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 662, in async_setup await self.__async_setup_with_context(hass, integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 751, in __async_setup_with_context result = await component.async_setup_entry(hass, self) File “/config/custom_components/ramses_cc/init.py”, line 94, in async_setup_entry await broker.async_setup() File “/config/custom_components/ramses_cc/broker.py”, line 146, in async_setup await self.client.start(cached_packets=cached_packets())
Detected blocking call to glob with args ('/dev/',) inside the event loop by custom integration ‘ramses_cc’ at custom_components/ramses_cc/broker.py, line 146: await self.client.start(cached_packets=cached_packets()) (offender: /usr/local/lib/python3.13/site-packages/ramses_tx/transport.py, line 147: for device in glob.glob("/dev/”) + glob.glob("/dev/serial/by-id/”):), please create a bug report at GitHub · Where software is built For developers, please see Blocking operations with asyncio | Home Assistant Developer Docs Traceback (most recent call last): File “”, line 198, in _run_module_as_main File “”, line 88, in _run_code File “/usr/src/homeassistant/homeassistant/main.py”, line 223, in sys.exit(main()) File “/usr/src/homeassistant/homeassistant/main.py”, line 209, in main exit_code = runner.run(runtime_conf) File “/usr/src/homeassistant/homeassistant/runner.py”, line 156, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 712, in run_until_complete self.run_forever() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 683, in run_forever self._run_once() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 2050, in _run_once handle._run() File “/usr/local/lib/python3.13/asyncio/events.py”, line 89, in _run self._context.run(self._callback, *self._args) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 896, in async_setup_locked await self.async_setup(hass, integration=integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 662, in async_setup await self.__async_setup_with_context(hass, integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 751, in __async_setup_with_context result = await component.async_setup_entry(hass, self) File “/config/custom_components/ramses_cc/init.py”, line 94, in async_setup_entry await broker.async_setup() File “/config/custom_components/ramses_cc/broker.py”, line 146, in async_setup await self.client.start(cached_packets=cached_packets())
Detected blocking call to open with args (‘/sys/devices/platform/axi/1000120000.pcie/1f00200000.usb/xhci-hcd.0/usb1/1-2/bNumInterfaces’,) inside the event loop by custom integration ‘ramses_cc’ at custom_components/ramses_cc/broker.py, line 146: await self.client.start(cached_packets=cached_packets()) (offender: /usr/local/lib/python3.13/site-packages/serial/tools/list_ports_linux.py, line 84: with open(os.path.join(*args)) as f:), please create a bug report at GitHub · Where software is built For developers, please see Blocking operations with asyncio | Home Assistant Developer Docs Traceback (most recent call last): File “”, line 198, in _run_module_as_main File “”, line 88, in _run_code File “/usr/src/homeassistant/homeassistant/main.py”, line 223, in sys.exit(main()) File “/usr/src/homeassistant/homeassistant/main.py”, line 209, in main exit_code = runner.run(runtime_conf) File “/usr/src/homeassistant/homeassistant/runner.py”, line 156, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 712, in run_until_complete self.run_forever() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 683, in run_forever self._run_once() File “/usr/local/lib/python3.13/asyncio/base_events.py”, line 2050, in _run_once handle._run() File “/usr/local/lib/python3.13/asyncio/events.py”, line 89, in _run self._context.run(self._callback, *self._args) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 896, in async_setup_locked await self.async_setup(hass, integration=integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 662, in async_setup await self.__async_setup_with_context(hass, integration) File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 751, in __async_setup_with_context result = await component.async_setup_entry(hass, self) File “/config/custom_components/ramses_cc/init.py”, line 94, in async_setup_entry await broker.async_setup() File “/config/custom_components/ramses_cc/broker.py”, line 146, in async_setup await self.client.start(cached_packets=cached_packets())

EgbertB · September 13, 2025, 10:16am

@cezar.florin I crated a new issue #295 for you on our GitHub repo. As mentioned before, UFH is not well supported, and there are more UFC issues.

Willem70 · September 13, 2025, 10:42am

Look into your home-assistant.log file for messages like: ‘received packet from unknown device’ or ‘dropped packet from …’
You may have to include the HCC id to your known list, or find other id’s that are filtered out.

EgbertB · September 13, 2025, 10:50am

@JoepW @Willem70 I created an issue #296 in the ramses_cc repo. Please follow that

JoepW · September 13, 2025, 12:07pm

Thanks for that.
For the time being I don’t force the known list…

PaulHo · September 18, 2025, 2:03pm

Hi, everything has been working fine except I have one evohome radiator value that has not shown a heat demand for a couple of months so thought I should try and sort it out - it did work initially. I’ve tried clearing the cache and restarting HA but no change. What are the next steps?

JoepW · September 18, 2025, 7:02pm

I have the same issue with the heat demand value in one zone.
In my case it concerns the last zone in the config file stored in the hidden .storage directory.

roblom · September 18, 2025, 7:07pm

That’s strange indeed because I have also the same issue. For me it’s indeed the last added zone. The zone seems to function normal but only the heat demand is unavailable.

EgbertB · September 23, 2025, 9:27am

A user has reported that the TRV and heat_demand were eventually picked up, only after he configured the correct role in the system schema. From the above user reports, typically this only happens to the last Zone added (which could just as well be 01).
Please follow ramses_cc issue 299.

PaulHo · September 24, 2025, 2:49pm

Hi EgbertB, I checked the ramses_cc file and the the zone isn’t the last one and is defined as a “radiator_valve” and has an actuator assigned…it looks just like the rest of the valve entries, here’s an extract, the one that doesn’t work is 08, Annies:

            "07": {
              "_name": "Blue Room",
              "class": "radiator_valve",
              "sensor": "04:009576",
              "actuators": [
                "04:009576"
              ]
            },
            "08": {
              "_name": "Annies",
              "class": "radiator_valve",
              "sensor": "04:088991",
              "actuators": [
                "04:088991"
              ]
            },
            "09": {
              "_name": "Hall Down",
              "class": "radiator_valve",
              "sensor": "04:088993",
              "actuators": [
                "04:088993"
              ]
            },

roblom · September 24, 2025, 3:46pm

In my case the issue of the missing demand is there for months, where in HA is rebooted several times so it doesn’t solves itself in my case. I’ve investigated it further.

I have a RAD, TVR and THM in this zone “Zolder”.

The RAD is connected to the controller and has a heat demand which is unavailable.
The TVR is connected to the (zone?) “Woonkamer” and has a heat demand with a value.
The THM is connected to the RAD “Zolder” and has no heat demand.

It seems like the problem is that the TVR it’s connected to the wrong zone. But in Evohome itself it functions correct. Also deleting the zone, and recreating it in Evohome does not change anything in HA.

EgbertB · September 24, 2025, 6:03pm

I do not have a CH system myself, but I take it the class was assigned automatically or did you edit it in Ramses RF config_flow > System schema? More often I see:
class: TRV
instead of
class: radiator_valve

Tim_Br · September 25, 2025, 2:00pm

Hello, I’m trying to get Ramses ESP working, but it’s not quite working. I’ve managed to set the Wi-Fi SSID and password, and with “idf.py -p COM3 monitor,” I see it’s working and I see messages coming in. I just don’t understand how and where to add/adjust the MQTT settings because I can’t connect Ramses ESP to the Synology/Docker host via USB. Can someone point me in the right direction?

EgbertB · September 25, 2025, 2:24pm

You didn’t tell us: have you followed the wiki?

Tim_Br · September 25, 2025, 2:40pm

the wiki only explains the configuration in Home assistant. I can’t even get it in home assistant without mqtt broker settings.