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

Hamamatsu · April 20, 2026, 9:31pm

I also only using the integration.

EgbertB · April 21, 2026, 9:41am

Config via the integration’s Config “wheel” is the only way to set up and adjust Ramses RF since 0.42.0.
HA dropped setup via a yaml a year ago. Only because we reimport it, it still seems to work. But since last February it contains deprecated keys, so beyter remove the ramses_cc part from your configuration.yaml.
See the ramses wiki for current configuration steps.

EgbertB · April 21, 2026, 9:52am

Are you sure your remote actually sends those commands, or did you copy them from an example?
My Vasco fan responds to a few, like yours. But its remote uses different codes, so that was more of a coincidence.

Can you turn on the Ramses Packet log (by default it is), press your remote and mark down in which sequence you pressed the buttons?
Zip the last hour of your packet log and add it to a new issue on GitHub ramses_cc.
I will have a look

Vedovatod · April 21, 2026, 2:55pm

Hi, thanks for the idea: I digged more in the topic.
I have edited climate.py to add away and boost and it works.
_attr_fan_modes: list[str] | None = [
FAN_OFF,
FAN_AUTO,
FAN_LOW,
FAN_MEDIUM,
FAN_HIGH,
“away”,
“boost”,

My question: if I would use your known list and relative commands, they would not be matching the climate.py defaults (off, medium, low, high). What have you modified to make them work?. Even if working now away and boost will stop to work as soon as I will update Rameses.

Vedovatod · April 21, 2026, 3:00pm

Many thanks for the reply. I have done it to figure out which command my physical remote was sending to the unit. I simply copied them and as of now I’ve been able to make them work (Off, low, medium, high, boos, away) but I modified the climate.py to add them.

EgbertB · April 21, 2026, 6:01pm

The Vasco responded to some of the default commands that were built into Ramsrs RF recently. My Known List (in Config) included a correct set, but I used Dutch names, like ‘laag’ instead of ‘low’. The Climate controller will look for a n exact match to low, so I added a copy of the laag command and renamed it to

low: " I --- 29:123456 29:123456 --:------ 22F1 003 000206"

When wr add your boost and away keys to the dropdown, the problem for other users would be that their fan might not support away, and they wonder why it is in the dropdown.
Instead, you can create 2 helper buttons that call the ramses.send_cmd Action with ‘boost’ as the command.

davidtja · April 23, 2026, 10:51am

Im still not seeing any climate entities, the thread is a little unclear on whether we should be seeing these from Evohome since the recent changes. If we should perhaps my schema is wrong I have literally tried everything.
Heres my found devices

"01:081083":
  class: CTL
"10:118573":
  class: OTB
"18:203270":
  class: HGI
  
  "01:081083":
  class: CTL
"04:023774":
  class: radiator_valve
"04:023780":
  class: radiator_valve
"04:027356":
  class: radiator_valve
"04:027358":
  class: radiator_valve
"04:027360":
  class: radiator_valve
"04:027646":
  class: radiator_valve
"04:027648":
  class: radiator_valve
"04:027650":
  class: radiator_valve
"04:027656":
  class: radiator_valve
"04:027714":
  class: radiator_valve
"04:027716":
  class: radiator_valve
"04:027718":
  class: radiator_valve
"04:027720":
  class: radiator_valve
"04:027722":
  class: radiator_valve
"07:025191":
  class: dhw_sensor
"10:118573":
  class: OTB
"13:001489":
  class: electrical_relay
"13:001522":
  class: electrical_relay
"13:003271":
  class: electrical_relay
"13:055679":
  class: electrical_relay
"13:173107":
  class: electrical_relay
"13:224329":
  class: electrical_relay
"18:203270":
  class: HGI
"34:027677":
  class: thermostat
"34:063533":
  class: thermostat
"34:150571":
  class: thermostat
"34:150655":
  class: thermostat
"34:150657":
  class: thermostat

I have now just got the following in known devices:

"01:081083":
  class: CTL
"18:203270":
  class: HGI

EgbertB · April 23, 2026, 2:32pm

We are still sorting this out, step by step. Some steps had undesired side-effects. But some improvements are already in place. Expect another pre-release in a few days.
For evohome you don’t need to add the schema in config, as it should be picked up. That’s why you see a warning about it not being “minimal”. It does help to run you system, until we fully repair discovery of Zones, in particular.
Thanks for all test feedback.

Vedovatod · April 29, 2026, 12:27pm

Hi. It seems I’ve been able to handle Ramses (enough for what I need now) and experimented Ramses_Extra. Nice tool. I’m playing with it but I’m having some issue on the Dashboard. The graphic part Reset every hour and give the message “HVAC Fan Card Feature Disabled” - Enable this feature in Ramses Extra configuration. So I have to configure it again to make it work. Than after some time I get same message. What am I doing wrong? Next step is CO2 Fake sensor and Humidity Fake sensor. Where can I read something (I’m using a Tuya device configured in HA which is giving me a lot of parameters and I would like to use them to complete FAN info). Thanks

Willem70 · April 29, 2026, 6:05pm

@Vedovatod Hi, nice to hear you are trying Ramses Extras.

I have opened an issue on github with some questions for you, so we can solve this strange behaviour. My first thought is that it’s loading an old cached version. Try to hard-refresh the browser (Ctrl-Shft-R or another method).

The wiki should give you info on how to use the extra sensors.
A few tips:

Did you configure the default feature for your fan ? It will add some extra entities for it (in combination with the temp/humidity sensors)
External sensors can be used by the FAN Configuration feature. Enable it - Select your FAN - Internal Fan Sensors - choose eg indoor_humidity_kind: external, External (from HA entity) and choose your humidity sensor.
The same for CO2 sensor…
If you have enabled default feature for your FAN, it will now calculate an absolute humidity. But…it depends on both temperature and relative humidity, so if these sensors are not near each other (best in the same device) the value will not be accurate.

There is another way to add sensors. You can add ‘area sensors’. You can even define DIY-zones (see the wiki on how to create, and use your own dampers for this), but this is still a bit experimental. It works ok, but not tested on a live system yet.

These sensors can then be used to control the FAN on humidity or CO2.
For humidity, it checks the absolute indoor and outdoor humidity. If it is high inside, but the outside air contains even more water/m3, then there is no use to ventilate more…

Willem70 · April 29, 2026, 6:32pm

@Vedovatod, I think I found the issue…a new release is on it’s way…can you try it ?

Vedovatod · May 5, 2026, 7:50pm

Hi. I found a mistake on my way of configuring (I have followed Claude AI suggestions…).It seems ok now. I’ve added external CO2, Humidity and other sensors but absolute Indoor and outdoor are not showing. Is there some setting I need to do? Also temperature on bottom right is showing “?” and I don’t know what it refers. Also calendar below CO2 in the graphic part is not showing. Some of commands are not matching: when I press “Low” command in the Graphic part is actually setting “Away”. When I press “Medium” in graphic part I get “Low” setting. Any help really appreciated. Thanks

Willem70 · May 6, 2026, 5:46pm

@Vedovatod

Bottom right temp. is the temperature of the air coming into your house (from outside, but heated or cooled by the outgoing air). Possible that your FAN doesn’t have a sensor built-in for it. Check the Supply temperature entity. There is currently no option to redirect this on this position on the card. But you could look at area sensors for now.

Absolute humidity is calculated by the default feature. It’s used by multiple features so that’s why I made it available from there. Default feature is always enabled, but you still need to select the devices it should be enabled for…so enable your fan. But, I think you have done that ?

–

I noticed you may have selected derived for indoor temperature/humidity. I’m afraid that’s an option I intended to work out, but never did and it should be removed. (I will if time allows it, issue created as a reminder). So, just select external + your entity.

To get the absolute humidity working with external sensors here’s a little recipe:

Configuration for Absolute Humidity

For indoor absolute humidity (indoor_abs_humidity):

Temperature part: Set indoor_abs_humidity_temperature_kind to "External temperature" and select a temperature entity
Humidity part: Set indoor_abs_humidity_humidity_kind to "External (%)" and select a relative humidity entity

For outdoor absolute humidity (outdoor_abs_humidity):

Temperature part: Set outdoor_abs_humidity_temperature_kind to "External temperature" and select a temperature entity
Humidity part: Set outdoor_abs_humidity_humidity_kind to "External (%)" and select a relative humidity entity

How it Works

The system then:

Takes the temperature from the first entity
Takes the relative humidity from the second entity
Calculates absolute humidity using the Magnus formula
Shows "derived" on the HVAC fan card because it's calculated, not directly measured

Alternative Options

"External absolute humidity": If you have a sensor that directly measures absolute humidity, you can select this and only provide one entity
"Internal": Uses the FAN device's built-in sensors for both temperature and humidity

rieschard · May 14, 2026, 3:05pm

Should evohome and fake sensors be working again with the last updates?