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

peternash · October 29, 2025, 9:10am

@Tchirana and @spencerwebb189 - first it’s worth checking the devices really have gone from Evohome - in my experience the only way to completely clear the bindings for a zone is to delete the zone and recreate it in Evohome. Otherwise you can end up with “ghost” devices that don’t cause a problem in Evohome but show up in Ramses RF. The binary sensor for the Evohome controller status can give a clue to “ghost” bindings - it will be called something like binary_sensor.01_216136_status and shows the current Evohome bindings.

If the devices really have gone from Evohome then this worked for me - I had two HR91’s that I’d replaced with HR92’s and I’d just left them as disabled devices for now but I just tried this:

Take a backup just in case
Disable the Ramse RF integration
In the homeassistant/.storage folder edit core.device_registry and remove the line(s) for the offending device(s)
In the homeassistant/.storage folder delete ramses_cc (the cache)
Restart Home Assistant
Re-enable the Ramses RF integration

The previously disabled HR91 devices are now gone.

davidtja · October 29, 2025, 9:41am

Is anyone using this integration to manage the Evohome schedule rather than in the proprietary Evo app?
Perhaps there are some blueprints that play nicelely? Any feedback appreciated.

Tchirana · October 29, 2025, 10:08am

The evemome controller, after a fw update stopped sending this data over RF:

see this:

github.com/ramses-rf/ramses_cc

0.31.16 ramses_cc.get_zone_schedule service failing

opened 09:34AM - 16 Apr 24 UTC

closed 02:41PM - 03 Aug 25 UTC

jrb80

v0.31.16 It seems like the **ramses_cc.get_zone_schedule** service is failing ag…ain with a traceback error. ``` File "/config/custom_components/ramses_cc/climate.py", line 482, in async_get_zone_schedule await self._device.get_schedule() File "/usr/local/lib/python3.12/site-packages/ramses_rf/system/zones.py", line 152, in get_schedule await self._schedule.get_schedule(force_io=force_io) File "/usr/local/lib/python3.12/site-packages/ramses_rf/system/schedule.py", line 222, in get_schedule await asyncio.wait_for( File "/usr/local/lib/python3.12/asyncio/tasks.py", line 520, in wait_for return await fut ^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/ramses_rf/system/schedule.py", line 256, in _get_schedule self._global_ver, _ = await self.tcs._schedule_version(force_io=True) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/ramses_rf/system/heat.py", line 630, in _schedule_version self._msg_0006 = Message(pkt) ^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/ramses_tx/message.py", line 64, in __init__ self.src: Address = pkt.src ^^^^^^^ AttributeError: 'NoneType' object has no attribute 'src' ```

I think it would be possible to query directly the evohome online api and request this data over wifi but the integration would need modification and it will be also bonded to the resideo cloud account. As I understand this data is stored in the evohome controller and synced only with the cloud

Tchirana · October 29, 2025, 10:13am

@peternash I’ll give it a try . The only thing I did not do previously was disabling the integration.

Tchirana · October 29, 2025, 10:45am

hmmm, after doing all this that device was still there . I went ahead and deleted the entry from ramses integration and readded and it lost all devices and now I am waiting for the zones and other stuff to be redetected. Curious is that I have all my TRV devices renamed and they were seen with the old names I had. Yeah, weird. By the way I am using the new 0.52.1 version of the integration, but with sqlindex disabled and also using a ramses_esp and my serial port is configured to get data from mqtt.

ALSO:
@zxdavb especially but for everyone , I do not know if you already are aware but honeywell has a new fw update and they switched to ramses-III protocol. I found out this the hard way when one of my old THM failed and had to get the new DT4R. I had to talk with resideo support and they updated my evohome controller fw and now in advanced settings > system parametrs I have a new otion to enable also legacy R2 protocol (I am using a mix of HR80 and HR92 TRVs). Until now all looks good and even ramses_esp detected my new R3 protocol DT4R.

By the discussion I had with a guys from local resideo support it seems that these DT4R came in 2 versions of firmware.
Below the product code on these there is also a manufacturing date , mine is 2553 (2025 week 53) but any device with a manufacturing date up to 2550 comes with ramses II.

@zxdavb If you guys need any communication dumps and errors from what my ramses_esp sees now on the network I am happy to share. Of course any details that I might have missed , feel free to ask.

so it gets worse and worse with the new firmware:

2025-10-29 20:17:57.661 DEBUG (MainThread) [custom_components.ramses_cc.number] Setting up platform
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.broker] Registering platform number
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.broker] Connecting signal for platform number: ramses_cc_new_devices_number
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.broker] Platform setup completed for number
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Processing 25 items
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 13_187431
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 13_187431 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_115445
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_115445 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_120170
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_120170 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 22_014440
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 22_014440 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_245957
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_245957 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_157378
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_157378 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_157256
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_157256 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.662 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 22_098390
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 22_098390 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_153231
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_153231 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_153233
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_153233 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 00_031413
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 00_031413 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_116909
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_116909 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_153234
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_153234 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 04_153236
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 04_153236 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_00
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_00 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_01
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_01 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_02
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_02 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_03
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_03 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_04
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_04 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_05
2025-10-29 20:17:57.663 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_05 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.664 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_06
2025-10-29 20:17:57.664 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_06 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.664 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_07
2025-10-29 20:17:57.664 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_07 does not support 2411 parameters, skipping parameter entities
2025-10-29 20:17:57.664 DEBUG (MainThread) [custom_components.ramses_cc.number] async_create_parameter_entities for 01_226586_08
2025-10-29 20:17:57.664 DEBUG (MainThread) [custom_components.ramses_cc.number] Device 01_226586_08 does not support 2411 parameters, skipping parameter entities

now almost all my zones are toast and the controller also.

I tryed wiping everything out and no matter what version I use the zones are not recreated anymore so I had to rollback from a backup.

also this looks fishy:

2025-10-29 20:23:22.851 WARNING (MainThread) [ramses_tx.message]  I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF

Yardco · October 30, 2025, 10:40am

Hi all,

Im trying to get my setup up and running but i’m a bit stuck. Would appreciate any help or direction on how to proceed.

My setup:

1x BRD91 wireless relay (13:043374)
1x Honeywell wireless thermostat (21:006924)
1x INDALO-TECH usb stick (18:134388)

Im able to pick up on RF traffic, added the Honeywell thermostat(THM) and BDR91(BDR) unit as known devices and stopped listening to all other traffic. Both devices have created entities that update as expected (the Honeywell gets a temperature entity and setpoint as an attribute, the BDR an activity and relay demand entity).

What I’m trying to achieve is being able to controle the BDR unit when I want to start heating, but I’m completely lost on how to be able to do that. Faking the thermostat does not allow me it seems to adjust its temperature or setpoint, and I’m not seeing any particular traffic from the physical thermostat that would indicate a command to open/close the relay.

Any thoughts on how I should proceed?

Tchirana · October 30, 2025, 11:11am

Setup a issue here for the new firmware 02.47.00.01 on the Evotouch:

github.com/ramses-rf/ramses_rf

RAMSES-III protocol + new firmware on honeywell controller no Zones/THR

opened 10:55AM - 30 Oct 25 UTC

Tchirana

**Describe the bug** I had been running strong and true with a device from Ind…aloTech/ramses_esp in latest Homeassistant and latest version of the integration when one of my DT92 THM failed. So I got it replaced by a DT4R and here the show starts: Had to contact Resideo because the DT4R was not binding to my controller and they knew the problem. Seems like the DT4R with production date over 2530 come by default with RAMSES-III protocol. They pushed an update on my evotouch controller (02.47.00.01 / wifi 02.00.20.00). Because I use a mix of TRV and THM (HR80, HR92, HR93 DT92, DT4R) which use different versions of RAMSES , Resideo instructed that after the update to go in advanced settings > System Parameters and enable the last option there LEGACY RF COMPONENTS. On honeywell side all looks good, all my zones are ok and basically I see no functionality change. On HA side things went haywire. Because I had a ghost THM left from this move to DT4R I completely removed the ramses_cc integration, deleted the ramses_cc cache file from .storage of HomeAssistant , reboot HAOS server, redownloaded from HACS the integration , set it up again (i use ramses_esp over mqtt) and surprize, my zones (RAD) are not detected anymore. I have some logs saved also. This was not ok so I reverted my backup of HA and now I have all the zones back because they were in the ramses_cc cache file but they have status unavailable. I also have logs from the integration and I see that the zones are detected: ``` 025-10-30 12:49:44.815 INFO (MainThread) [ramses_rf.dispatcher] || 01:226586 | | I | setpoint | [..] || [{'zone_idx': '00', 'setpoint': 20.0}, {'zone_idx': '01', 'setpoint': 5.0}, {'zone_idx': '02', 'setpoint': 21.5}, {'zone_idx': '03', 'setpoint': 5.0}, {'zone_idx': '04', 'setpoint': 20.0}, {'zone_idx': '05', 'setpoint': 19.5}, {'zone_idx': '06', 'setpoint': 20.5}, {'zone_idx': '07', 'setpoint': 18.0}, {'zone_idx': '08', 'setpoint': 20.0}] 2025-10-30 12:49:44.838 INFO (MainThread) [ramses_rf.dispatcher] || 01:226586 | | I | temperature | [..] || [{'zone_idx': '00', 'temperature': 21.28}, {'zone_idx': '01', 'temperature': 24.27}, {'zone_idx': '02', 'temperature': 22.5}, {'zone_idx': '03', 'temperature': 21.54}, {'zone_idx': '04', 'temperature': 20.69}, {'zone_idx': '05', 'temperature': 20.89}, {'zone_idx': '06', 'temperature': 23.71}, {'zone_idx': '07', 'temperature': 20.57}, {'zone_idx': '08', 'temperature': 21.8}] 2025-10-30 12:49:45.253 INFO (MainThread) [ramses_rf.dispatcher] || 04:153234 | | I | temperature | || {'temperature': 20.44} 2025-10-30 12:49:51.254 INFO (MainThread) [ramses_rf.dispatcher] || 04:153234 | 01:226586 | I | device_battery | 06 || {'zone_idx': '06', 'battery_low': False, 'battery_level': None} 2025-10-30 12:49:51.265 INFO (MainThread) [ramses_rf.dispatcher] || 04:153234 | | I | device_battery | || {'battery_low': False, 'battery_level': None} 2025-10-30 12:49:52.963 INFO (MainThread) [ramses_rf.dispatcher] || 18:109940 | 01:226586 | RQ | zone_mode | 04 || {'zone_idx': '04'} 2025-10-30 12:49:56.252 INFO (MainThread) [ramses_rf.dispatcher] || 04:157378 | 01:226586 | I | setpoint | 04 || {'zone_idx': '04', 'setpoint': 20.0} 2025-10-30 12:50:04.254 INFO (MainThread) [ramses_rf.dispatcher] || 04:153236 | 01:226586 | I | heat_demand | 06 || {'zone_idx': '06', 'heat_demand': 0.0} 2025-10-30 12:50:04.752 INFO (MainThread) [ramses_rf.dispatcher] || 04:245957 | 01:226586 | I | heat_demand | 03 || {'zone_idx': '03', 'heat_demand': 0.0} 2025-10-30 12:50:05.252 INFO (MainThread) [ramses_rf.dispatcher] || 04:153236 | 01:226586 | I | setpoint | 06 || {'zone_idx': '06', 'setpoint': 20.5} 2025-10-30 12:50:07.253 INFO (MainThread) [ramses_rf.dispatcher] || 04:115445 | | I | temperature | || {'temperature': 21.28} 2025-10-30 12:50:09.250 INFO (MainThread) [ramses_rf.dispatcher] || 04:153233 | 01:226586 | I | setpoint | 08 || {'zone_idx': '08', 'setpoint': 20.0} 2025-10-30 12:50:12.253 INFO (MainThread) [ramses_rf.dispatcher] || 04:245957 | | I | temperature | || {'temperature': 21.54} 2025-10-30 12:50:17.751 INFO (MainThread) [ramses_rf.dispatcher] || 04:245957 | 01:226586 | I | heat_demand | 03 || {'zone_idx': '03', 'heat_demand': 0.0} ``` But I also see these errors: ``` 2025-10-30 09:43:30.266 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 09:52:03.221 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=1/4>: echo_timeout=0.5 2025-10-30 09:52:04.225 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=2/4>: echo_timeout=1.0 2025-10-30 09:52:06.229 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=3/4>: echo_timeout=2.0 2025-10-30 09:52:08.294 WARNING (paho-mqtt-client-) [ramses_tx.transport] MqttTransport(QosProtocol(WantEcho, len(queue)=0)): the ESP device is offline (via LWT): RAMSES/GATEWAY/18:109940 2025-10-30 09:52:10.232 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=4/4>: echo_timeout=4.0 2025-10-30 09:52:10.233 WARNING (MainThread) [ramses_rf.entity_base] 01:226586 (evohome): Failed to send discovery cmd: 2E04|RP|01:226586: <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=4/4>: Exceeded maximum retries 2025-10-30 09:57:03.223 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:03:30.509 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 10:21:39.204 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=12B0|RQ|01:226586|02, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:21:40.208 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=12B0|RQ|01:226586|02, tx_count=2/4>: echo_timeout=1.0 2025-10-30 10:23:30.649 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 10:42:36.842 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|02, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:42:55.472 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|05, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:43:30.912 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 10:51:15.986 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=12B0|RQ|01:226586|07, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:01:19.810 WARNING (paho-mqtt-client-) [ramses_tx.transport] MqttTransport(QosProtocol(IsInIdle, len(queue)=0)): the ESP device is offline (via LWT): RAMSES/GATEWAY/18:109940 2025-10-30 11:01:30.033 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:03:31.101 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 11:04:39.802 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:15:14.468 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:17:15.191 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:23:31.247 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 11:28:23.744 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:31:26.030 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=0008|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:32:34.091 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|07, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:32:36.041 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|06, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:37:36.173 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|06, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:39:15.299 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|00, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:42:55.572 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|03, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:43:32.277 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 11:47:06.135 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=1/4>: echo_timeout=0.5 2025-10-30 12:02:57.641 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|05, tx_count=1/4>: echo_timeout=0.5 2025-10-30 12:03:31.647 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF ``` Any more info requests or ways to how I should investigate this further I am happy and willing to provide.

Tchirana · October 30, 2025, 11:12am

@Yardco what type of thermostat do you have? Evohome? usually you cannot control directly the BDR. You have to set the temperature higher that what the thermostat reads.

Yardco · October 30, 2025, 11:23am

It’s a Honeywell wireless (round) thermostat (T87RF1003).

If I understand correctly, the only way to make the BDR unit open/close is by adjusting the temperature of the (faked) thermostat? I’ve tried to do this by using the services in developer tools, but none of them seem to be able to adjust the temperature/setpoint of the temperature entity. In the log it shows that it should be a 03:xxxxxx device_id, yet mine uses 21:xxxxxx

Tchirana · October 30, 2025, 11:35am

I’m no expert on this,I have a evohome, but I think you may want to try and fake a controller and a zone for you to get the controls to operate temp changes on that round. But I may be wrong.

EgbertB · October 30, 2025, 1:20pm

Nothing ‘fishy’, just a new format we’ve never seen before.
Add (only) that line as an issue on ramses_cc GitHub, with your device details and packet log (zipped).
The rest is of interest, for this forum. But don’t quote closed issues from 3 months ago. That’s confusing for you.

Yardco · October 30, 2025, 1:25pm

Thanks for the suggestion! I’ll look in to faking a controller/zone to see if that will work.

Tchirana · October 30, 2025, 2:25pm

Ok. Let me get more details and i’ll put a issue. On cc or rf github? Now I have the integration disabled in HA because i see some weird stuff in the evotouch controller with my zones getting weird overrides. Fraking hel…

Tchirana · October 30, 2025, 2:27pm

I may need to do the same because of the new protocol. Please report back if it works for you and how you did it

Tchirana · October 30, 2025, 10:06pm

I did not have time today to look into it but i managed to get client.py and parse a packet log:

23:50:33.646  I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF
23:50:33.851  I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF
23:50:34.029 RQ --- 01:226586 04:157378 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:157378 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.030 RQ --- 01:226586 04:153233 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:153233 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.134 RQ --- 01:226586 04:157378 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:157378 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.135 RQ --- 01:226586 04:153233 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:153233 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.135 RQ --- 01:226586 04:157256 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:157256 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.136 RQ --- 01:226586 13:187431 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 13:187431 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.137 RQ --- 01:226586 04:153231 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:153231 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.138 RQ --- 01:226586 04:120170 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:120170 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.138 RQ --- 01:226586 22:098390 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 22:098390 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.139 RQ --- 01:226586 04:245957 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:245957 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.140 RQ --- 01:226586 04:115445 --:------ 2309 001 00 < PacketInvalid(RQ --- 01:226586 04:115445 --:------ 2309 001 00 < Unexpected verb/code for src (CTL) to Tx)
23:50:34.143  I --- 01:226586 --:------ 01:226586 1100 008 01180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 01180100007FFF01
23:50:34.143  I --- 01:226586 --:------ 01:226586 1100 008 06180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 06180100007FFF01
23:50:34.144  I --- 01:226586 22:098390 --:------ 1060 003 060000 < PacketInvalid( I --- 01:226586 22:098390 --:------ 1060 003 060000 < Unexpected code for src (CTL) to Tx)
23:50:34.145  I --- 01:226586 --:------ 01:226586 1100 008 03180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 03180100007FFF01
23:50:34.147  I --- 01:226586 --:------ 01:226586 1100 008 08180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 08180100007FFF01
23:50:34.147  I --- 01:226586 13:187431 --:------ 1060 003 FC0000 < Payload doesn't match '^0[0-9A-F](FF|[0-9A-F]{2})0[01]$': FC0000
23:50:34.148  I --- 01:226586 04:120170 --:------ 1060 003 010000 < PacketInvalid( I --- 01:226586 04:120170 --:------ 1060 003 010000 < Unexpected code for src (CTL) to Tx)
23:50:34.149  I --- 01:226586 04:157378 --:------ 1060 003 040000 < PacketInvalid( I --- 01:226586 04:157378 --:------ 1060 003 040000 < Unexpected code for src (CTL) to Tx)
23:50:34.149  I --- 01:226586 --:------ 01:226586 1100 008 02180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 02180100007FFF01
23:50:34.150  I --- 01:226586 04:157256 --:------ 1060 003 050000 < PacketInvalid( I --- 01:226586 04:157256 --:------ 1060 003 050000 < Unexpected code for src (CTL) to Tx)
23:50:34.150  I --- 01:226586 04:245957 --:------ 1060 003 030000 < PacketInvalid( I --- 01:226586 04:245957 --:------ 1060 003 030000 < Unexpected code for src (CTL) to Tx)
23:50:34.151  I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF
23:50:34.151  I --- 01:226586 --:------ 01:226586 1100 008 07180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 07180100007FFF01
23:50:34.152  I --- 01:226586 --:------ 01:226586 1100 008 05180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 05180100007FFF01
23:50:34.153  I --- 01:226586 --:------ 01:226586 1100 008 04180100007FFF01 < Payload doesn't match '^(00|FC)[0-9A-F]{6}(00|FF)([0-9A-F]{4}0[01])?$': 04180100007FFF01
23:50:34.153  I --- 01:226586 04:153233 --:------ 1060 003 080000 < PacketInvalid( I --- 01:226586 04:153233 --:------ 1060 003 080000 < Unexpected code for src (CTL) to Tx)
23:50:34.154  I --- 01:226586 04:115445 --:------ 1060 003 000000 < PacketInvalid( I --- 01:226586 04:115445 --:------ 1060 003 000000 < Unexpected code for src (CTL) to Tx)
23:50:34.155  I --- 01:226586 04:153231 --:------ 1060 003 070000 < PacketInvalid( I --- 01:226586 04:153231 --:------ 1060 003 070000 < Unexpected code for src (CTL) to Tx)
23:50:34.155  I --- 01:226586 --:------ 01:226586 1100 008 00180100007FFF01 < AssertionError(01)

I’ll get more info in this issue tomorrow:

github.com/ramses-rf/ramses_rf

RAMSES-III protocol + new firmware on honeywell controller no Zones/THR

opened 10:55AM - 30 Oct 25 UTC

Tchirana

**Describe the bug** I had been running strong and true with a device from Ind…aloTech/ramses_esp in latest Homeassistant and latest version of the integration when one of my DT92 THM failed. So I got it replaced by a DT4R and here the show starts: Had to contact Resideo because the DT4R was not binding to my controller and they knew the problem. Seems like the DT4R with production date over 2530 come by default with RAMSES-III protocol. They pushed an update on my evotouch controller (02.47.00.01 / wifi 02.00.20.00). Because I use a mix of TRV and THM (HR80, HR92, HR93 DT92, DT4R) which use different versions of RAMSES , Resideo instructed that after the update to go in advanced settings > System Parameters and enable the last option there LEGACY RF COMPONENTS. On honeywell side all looks good, all my zones are ok and basically I see no functionality change. On HA side things went haywire. Because I had a ghost THM left from this move to DT4R I completely removed the ramses_cc integration, deleted the ramses_cc cache file from .storage of HomeAssistant , reboot HAOS server, redownloaded from HACS the integration , set it up again (i use ramses_esp over mqtt) and surprize, my zones (RAD) are not detected anymore. I have some logs saved also. This was not ok so I reverted my backup of HA and now I have all the zones back because they were in the ramses_cc cache file but they have status unavailable. I also have logs from the integration and I see that the zones are detected: ``` 025-10-30 12:49:44.815 INFO (MainThread) [ramses_rf.dispatcher] || 01:226586 | | I | setpoint | [..] || [{'zone_idx': '00', 'setpoint': 20.0}, {'zone_idx': '01', 'setpoint': 5.0}, {'zone_idx': '02', 'setpoint': 21.5}, {'zone_idx': '03', 'setpoint': 5.0}, {'zone_idx': '04', 'setpoint': 20.0}, {'zone_idx': '05', 'setpoint': 19.5}, {'zone_idx': '06', 'setpoint': 20.5}, {'zone_idx': '07', 'setpoint': 18.0}, {'zone_idx': '08', 'setpoint': 20.0}] 2025-10-30 12:49:44.838 INFO (MainThread) [ramses_rf.dispatcher] || 01:226586 | | I | temperature | [..] || [{'zone_idx': '00', 'temperature': 21.28}, {'zone_idx': '01', 'temperature': 24.27}, {'zone_idx': '02', 'temperature': 22.5}, {'zone_idx': '03', 'temperature': 21.54}, {'zone_idx': '04', 'temperature': 20.69}, {'zone_idx': '05', 'temperature': 20.89}, {'zone_idx': '06', 'temperature': 23.71}, {'zone_idx': '07', 'temperature': 20.57}, {'zone_idx': '08', 'temperature': 21.8}] 2025-10-30 12:49:45.253 INFO (MainThread) [ramses_rf.dispatcher] || 04:153234 | | I | temperature | || {'temperature': 20.44} 2025-10-30 12:49:51.254 INFO (MainThread) [ramses_rf.dispatcher] || 04:153234 | 01:226586 | I | device_battery | 06 || {'zone_idx': '06', 'battery_low': False, 'battery_level': None} 2025-10-30 12:49:51.265 INFO (MainThread) [ramses_rf.dispatcher] || 04:153234 | | I | device_battery | || {'battery_low': False, 'battery_level': None} 2025-10-30 12:49:52.963 INFO (MainThread) [ramses_rf.dispatcher] || 18:109940 | 01:226586 | RQ | zone_mode | 04 || {'zone_idx': '04'} 2025-10-30 12:49:56.252 INFO (MainThread) [ramses_rf.dispatcher] || 04:157378 | 01:226586 | I | setpoint | 04 || {'zone_idx': '04', 'setpoint': 20.0} 2025-10-30 12:50:04.254 INFO (MainThread) [ramses_rf.dispatcher] || 04:153236 | 01:226586 | I | heat_demand | 06 || {'zone_idx': '06', 'heat_demand': 0.0} 2025-10-30 12:50:04.752 INFO (MainThread) [ramses_rf.dispatcher] || 04:245957 | 01:226586 | I | heat_demand | 03 || {'zone_idx': '03', 'heat_demand': 0.0} 2025-10-30 12:50:05.252 INFO (MainThread) [ramses_rf.dispatcher] || 04:153236 | 01:226586 | I | setpoint | 06 || {'zone_idx': '06', 'setpoint': 20.5} 2025-10-30 12:50:07.253 INFO (MainThread) [ramses_rf.dispatcher] || 04:115445 | | I | temperature | || {'temperature': 21.28} 2025-10-30 12:50:09.250 INFO (MainThread) [ramses_rf.dispatcher] || 04:153233 | 01:226586 | I | setpoint | 08 || {'zone_idx': '08', 'setpoint': 20.0} 2025-10-30 12:50:12.253 INFO (MainThread) [ramses_rf.dispatcher] || 04:245957 | | I | temperature | || {'temperature': 21.54} 2025-10-30 12:50:17.751 INFO (MainThread) [ramses_rf.dispatcher] || 04:245957 | 01:226586 | I | heat_demand | 03 || {'zone_idx': '03', 'heat_demand': 0.0} ``` But I also see these errors: ``` 2025-10-30 09:43:30.266 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 09:52:03.221 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=1/4>: echo_timeout=0.5 2025-10-30 09:52:04.225 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=2/4>: echo_timeout=1.0 2025-10-30 09:52:06.229 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=3/4>: echo_timeout=2.0 2025-10-30 09:52:08.294 WARNING (paho-mqtt-client-) [ramses_tx.transport] MqttTransport(QosProtocol(WantEcho, len(queue)=0)): the ESP device is offline (via LWT): RAMSES/GATEWAY/18:109940 2025-10-30 09:52:10.232 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=4/4>: echo_timeout=4.0 2025-10-30 09:52:10.233 WARNING (MainThread) [ramses_rf.entity_base] 01:226586 (evohome): Failed to send discovery cmd: 2E04|RP|01:226586: <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=4/4>: Exceeded maximum retries 2025-10-30 09:57:03.223 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:03:30.509 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 10:21:39.204 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=12B0|RQ|01:226586|02, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:21:40.208 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=12B0|RQ|01:226586|02, tx_count=2/4>: echo_timeout=1.0 2025-10-30 10:23:30.649 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 10:42:36.842 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|02, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:42:55.472 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|05, tx_count=1/4>: echo_timeout=0.5 2025-10-30 10:43:30.912 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 10:51:15.986 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=12B0|RQ|01:226586|07, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:01:19.810 WARNING (paho-mqtt-client-) [ramses_tx.transport] MqttTransport(QosProtocol(IsInIdle, len(queue)=0)): the ESP device is offline (via LWT): RAMSES/GATEWAY/18:109940 2025-10-30 11:01:30.033 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:03:31.101 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 11:04:39.802 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:15:14.468 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:17:15.191 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:23:31.247 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 11:28:23.744 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=3EF1|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:31:26.030 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=0008|RQ|13:187431, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:32:34.091 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|07, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:32:36.041 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|06, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:37:36.173 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|06, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:39:15.299 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|00, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:42:55.572 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|03, tx_count=1/4>: echo_timeout=0.5 2025-10-30 11:43:32.277 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF 2025-10-30 11:47:06.135 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2E04|RQ|01:226586, tx_count=1/4>: echo_timeout=0.5 2025-10-30 12:02:57.641 WARNING (MainThread) [ramses_tx.protocol_fsm] TOUT.. = <ProtocolContext state=WantEcho cmd_=2349|RQ|01:226586|05, tx_count=1/4>: echo_timeout=0.5 2025-10-30 12:03:31.647 WARNING (MainThread) [ramses_tx.message] I --- 01:226586 --:------ 01:226586 30C9 003 FC7FFF < Payload doesn't match '^(0[0-9A-F][0-9A-F]{4})+$': FC7FFF ``` Any more info requests or ways to how I should investigate this further I am happy and willing to provide.

brucemiranda · October 31, 2025, 11:03am

This message traffic is quite intriguing. Why is the controller suddenly trying to RQ battery operated devices. They will never respond because they will be asleep.
The new firmware seems to be EU specific for now.

EgbertB · October 31, 2025, 7:36pm

Please always quote that these are from the evohome update v3. We shouldn’t mix the new formats with what we have in place in Ramses RF.

EgbertB · October 31, 2025, 7:47pm

Ramses RF 0.52.3 was released today.

Try the new options for MQTT logging (default Off) and the MessageIndex database (default Off) in Config Flow.

Tchirana · October 31, 2025, 9:02pm

i’ll get them enabled.

Tchirana · October 31, 2025, 9:18pm

nice work. logs look a bit more explicit now. can we add also the qos in the Config Flow?
gateway config:

disable_qos: false