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

Share your Projects!
5078

Hi all, like a few people on here I accidently upgraded ramses_rf to the pre-release versions and I've managed to just about get by with it for my evohome setup until the last couple of updates. To help others I've create a copy of version 0.55.3 and fixed config flow so that you can install and maintain via the gui until the evohome issues are fixed.

Like others in the thread, I followed the guide on ramses_cc github to install from scratch to get back up and running but it seems happy now. The only file changed in my version is config_flow.py.

Hope it helps someone else out.

Cheers
Spence

5079

That sounds fantastic. Ill give it a try when i get back home. Do i totally uninstall and remove any remnants from folders beforehand? Thanks

5080

Hi, I followed these slightly edited steps from the wiki.

Completely install from scratch

  • backup the ramses_cc folder and ramses_cc file from home assistant
  • Screenshot and or copy all settings from the config flow setup, known device list and schema etc..
  • remove the Ramses RF integration from home assistant
  • restart HA
  • delete the ramses_cc file from the .storage folder. For this you may use the HA Terminal add-on, type cd /config/.storage/ to access the hidden dir and remove the ramses_cc file in there by typing rm ramses_cc. The ramses_cc folder should be gone at this point.
  • restart HA again
  • now install Ramses RF by either
  1. download the ramses_cc folder from my repo and manually copy it to the custom_components folder (probably more desirable as the main ramses repo will remain and can be used to upgrade once the bugs are ironed out.
  2. remove the existing ramses repo from HACS and add mine then install via the usual method
  • and restart HA...
  • Now re-add the integration via the devices and services page as usual, follow config flow, fingers crossed everything should work.....
5081

Thanks so much for your efforts will report back next weekend.

5082

Thanks @spencerwebb189, I've got it up and running and it looks promising. If all works out and my DHW automation works again I'll be over the moon.

Thanks again for your effort.

5083

Thanks @spencerwebb189 I'm up and running too.
I did notice that it did not automatically find my evofw3 and I had to enter it manually. After that everything was found fine.

5084

Ramses RF pre-release 0.57.10 is out in HACS. Work ongoing under the hood to modernize the code.

Works fine for HVAC.with your existing config.

For CH/DHW evohome, copy your existing schema into the Config > Schema box to try it out.

5085

Evohome Cooling Mode RF Captures — offering data

Following up on this thread about cooling support where @zxdavb mentioned needing captures from a system running in cooling mode — I have exactly that running right now and I'm happy to provide whatever data is useful.

My setup:

  • Evohome controller 01:075103 in cooling mode

  • 3× HCC100 UFH controllers (02:089804, 02:089971, 02:089979)

  • 6× DT92 wireless thermostats (22:xxxxxx)

  • Vaillant aroTHERM plus heat pump providing chilled water

  • Elecram ESP32-C6 Sub-GHz bridge via MQTT → ramses_cc v0.57.10

Observations during active cooling (all zones above setpoint, full demand):

2D49 — sent by controller every few sync cycles:

038  I --- 01:075103 --:------ 01:075103 2D49 003 F6C8FF

3EF0 — HCC100 actuator state (identical on both units):

082  I --- 02:089804 --:------ 02:089804 3EF0 009 760000100000000000
077  I --- 02:089971 --:------ 02:089971 3EF0 009 760000100000000000

3150 — zone demand from HCCs (same format as heating):

082  I --- 02:089804 --:------ 01:075103 3150 002 04C8  (zone 04, C8=100%)
082  I --- 02:089804 --:------ 01:075103 3150 002 03C8  (zone 03, 100%)
082  I --- 02:089804 --:------ 01:075103 3150 002 02BA  (zone 02, BA=93%)
076  I --- 02:089971 --:------ 01:075103 3150 002 0090  (zone 00, 90=72%)
078  I --- 02:089971 --:------ 01:075103 3150 002 01C8  (zone 01, 100%)

3B00 — actuator sync from controller:

039  I --- 01:075103 --:------ 01:075103 3B00 002 FCC8

2E04 — controller mode (queried by gateway):

000 RQ --- 18:217260 01:075103 --:------ 2E04 001 00
038 RP --- 01:075103 18:217260 --:------ 2E04 008 00FFFFFFFFFFFF00

Notes:

  • 2D49 payload F6C8FF is consistent across multiple captures during cooling with full demand. The protocol wiki lists this as "Unknown" — presumably it carries the heating/cooling mode flag.

  • 2E04 responds with 00 in byte 0, which existing docs map to "Auto" — yet the system is definitely in cooling. The cooling state might live exclusively in 2D49.

  • 3150 demand packets appear structurally identical to what's documented for heating. No extra byte or flag to distinguish cooling demand from heating demand.

  • I plan to capture the same system in heating mode when the season changes, for a proper byte-by-byte diff.

Happy to provide extended packet logs, specific message captures, or test anything that would help document the cooling protocol. Let me know what format/duration would be most useful.

5086

Hi all — long-time reader. I've built an ESP32 controller for Orcon HRC ventilation (HRC400 / 15RF) and wanted to share it back, since it leans heavily on the RAMSES-II decoding work here — huge thanks @zxdavb, ramses_rf is credited in the repo.

What it is: a standalone Orcon 15RF emulator/controller (not a gateway) on a single ESP32 — modes, bypass, an unbalanced "AC" night-cooling mode, and deliberate pairing. Plus a few things this crowd might appreciate:

  • MQTT + Home Assistant auto-discovery (works with Domoticz too) — so a single unit drops into HA without needing the full ramses_cc stack;
  • an on-device RF log — rolling RX/TX in ramses_rf string form with RSSI, so you can watch frames without a USB capture;
  • a /debug page with 31DA byte-rulers for calibrating decode offsets against a real unit.

Two bits that might be genuinely new here:

  1. SX1276 (SX127x) in direct/continuous FSK mode as a drop-in CC1101 alternative — demodulated data comes out on DIO2 into a UART, same trick as the CC1101, so it runs on the on-board radio of common boards (e.g. Heltec V2). I haven't seen it documented for RAMSES before.
  2. Open question I'd love input on: has anyone got RX working on an SX1262 (SX126x)? TX works, but the SX126x has no transparent/continuous mode, so the packet engine never frames a RAMSES packet (rx_n stays 0). Full details + everything I tried are in the README.

Repo (MIT): GitHub - me-processware/orcon-15rf-controller · GitHub — feedback and tips very welcome!

5087

Ramses RF pre-release 0.57.12 is out in HACS.

Still a few sensors missing running evohome but the foundation is in place.
HVAC bypass_position and filter_remaining have been fixed. See the release notes for details.

5088

Ramses RF 0.58.0 is out, featuring the Passive Discovery Scan service that helps you fill in the schema. Tested with HVAC and evohome. Make a backup first, then give it a spin!

Pre-release 0.58.1 has a fix to load last values from packet cache after restart. You must clear your existing history cache in prefs first.

5089

Ramses RF 0.58.2 is now in HACS, it pops up in HA.

We made this into a “real” release, stable enough with evohome and hvac bugs fixed.

In Config you have to fill in a Schema. The new passive device scan can assist with this task if you turn it on in the background. It’s a worthy successor to the ‘eavesdropping’ of legacy releases. Besides, it also works for HVAC. See the Wiki for details.

And: make a backup before any update, of course. Development and support is focussed on the latest version, but if Ramses RF currently “just works” for you, feel free to “Skip” this (or any update.

5090

It’s clear that a lot of work has gone into this integration recently, thanks so much to all involved!!

I’ll give the new release a go with my evohome today and report back.

Thanks

5091

Wow, thanks guys - it appears to work now. I have the climate entities back! Glad I waited, looks a slicker integration with less work for those starting from scratch. The only thing it didnt do was pick up the area name but thats easy to manually update. Thank you.

5092

It’s still a work in progress, some big changes under the hood will still be needed. And with changes new issues will pop-up.
So keep testing and do post issues on github, or here if you don’t have/want an account there.

5093

I said that as I was’nt sure its an issue or just me. I know it can take days for these things to poulate.

5094

Ah yeah, no worries, I wasn’t even reacting on the issue, that should be fixed anyways, just waiting on confirmation.

5095

One other potential bug (again not sure). The Entity shows the name of the zone (manually added) but shows the temperature element as unknown, yet it appears in the the actual full card. Top is Ramses below is Evohome API.

image
image715×177 7.65 KB

5096

Thanks, is it a battery device ? We did find an issue with those .

5097

Yes it is. Its a TRV. Thanks.