Can you confirm that evohome fake sensors work again in the latest versions? I think you said earlier that you use fake sensors
I’ve been using this integration for many years with faked sensors no problems. Last few months they haven’t worked after updating so I always went back to the last working one which was possibly 46 something. I’m now on 50.3 and with help from Claude I have them working.
The automation to update the sensors has changed but all six of my faked sensors have been works for a few days now.
Ramses RF 0.59.6 is available in HACS.
Many improvements both in the integration and in the library: optimised memory demand, reduced writing to the SD card, fetching 2411 parameters, sensor faking, and passive device discovery (config schema).
I’ve updated the Wiki to match the current schema format and options.
Thank you Egbert, I really appreciate all the work you’ve put into this integration 
A next stable version of Ramses RF is almost here. Testers are invited to try pre-release 0.59.9 from HACS over the weekend.
0.59.11 (RC-4) is available on HACS.
You are welcome to test this version. Please post any issues on Issues · ramses-rf/ramses_cc · GitHub.
Ramses RF stable release 0.60.0 is now available in HACS. The updated Wiki will guide you through the update procedure.
The Schema is at the heart of the config and your existing Known List is merged into it. Any device marked as yours in the schema, will be instantiated immediately. Passive Device Scan - on by default - will prompt you to accept or decline newly found devices.
I updated to the latest version (0.60.1). I have an underfloor heating with 3 zones, each with a thermostat (DT92E) as well as TRVs on radiators . Previously, the heat_demand attribute for my underfloor heating appeared on one of the UFH zones but now the attribute returns unknown…is this a bug or has it moved elsewhere? I’m trying to displaying it on a dashboard ( {{states.sensor[‘01_068717_03_heat_demand’].state|int }}%) as well as use it in automations.
@PaulHo If you inspect the Integration entities, you will find the supported names.
heat_demand was renamed to thermal_demand (as cooling support was added, sort of a negative heating…) in 0.60.0, so you might try that in your template. It should also pop up in the editor when you start typing the id.
As for UFH, some improvements were included in pre-release 0.60.2 that is out in HACS since this evening. More to come.
Ramses RF pre-release 0.60.2 is out in HACS since this evening, and is advised for users who keep up the HA Core updates to 2026.9.0 so they are prepared once that update pops up in HA.
Among other fixes, 0.60.2 contains specific fixes for changes introduced in HA Core beta. If you see specific “validation” issues, please file a bug report on GitHub under ramses_cc. It will also run fine with HA Core 2026.8.x.
Ramses RF pre-release 0.60.3 is out in HACS since this evening, once more fixed to support existing HA Core 2026.8.x as well as new 2026.9.0b4.
Also added UFH support (check entity names) and strategy-based fan_modes (orcon, vasco, etc.)
Thanks for adding UFH Support. I can see one of my zones, but not the second one.
The controller and both thermometers are present
02:022960:
_class: UFC
_owner: me
34:007977:
_class: RND
_owner: me
34:009973:
_class: RND
_owner: me
zones:
0A:
_name: Living Room
Please post code between backticks. Use the </> button for the markup, so that we can support you better.
Any difference between your two zones?
Turn on debug logging on the Integration, and restart. See wiki for details how to share the debug log (don’t paste it).
After many a month I’ve now bit the bullet. When HA/the old ramses crapped out after the core update I tried the latest version and so far it seems to be running fine.
Great job. Faked sensors are working and faked remote also working as intended.
Could have done with a culture shock greatest hits of what to expect, what changed and what to look out for and do since 56.5 or something like that because the change is massive!
So, just a few quick questions:
-Is it possible the passive scan has picked up some additional devices from neighbours? Because I see some new ones I don’t know.
-Ramses thinks my REM is actually a FAN, and I don’t agree. Because I actually faked/cloned/spoofed that remote 
Will this message stay or can I do something about it?
-Really nice the ventilation unit now reacts to the fan settings button, but can I keep the commands in there for if I have to start over or will this have negative effects?
-Anything I need to be aware of?
Oh and last: what is the role of the owner field?
@PyroPath Well, it’s all in the Wiki and we had an extensive 0.58>0.60 listing in the 0.60.0 and 0.60.1 release notes too.
Just thought I’d share an amazing find for scheduling in Evohome. I have been using the dreadful Evohome app and its associated pain of such an awkward implementation. I found an add-on called Velair and approached the developer, Cristian, about the possiblity of using with Ramses_CC. Within a day he had a running Beta, I tested over a couple of days and now he’s released it. Be great to see it taken up within the Evohome community to support the already incredible development.
From Cristian:
Velair is a free and open-source, local-first climate scheduler for Home Assistant. Version 1.7.0 adds external schedule execution for compatible Evohome systems through ramses_cc.
It provides a visual weekly schedule editor and can publish the effective Default, Profile, or Mode schedule directly to the Evohome controller. Once published, the controller retains responsibility for executing the schedule independently of Velair.
Velair clearly separates this external ownership from its normal local climate control. Direct features such as Boost, pause, Room Assist, and Adaptive Preconditioning are not sent to zones executed by the external controller.
The integration supports Evohome’s six daily switchpoints, including the midnight continuity point when required, and shows the current switchpoint usage while editing.
More information and installation instructions are available here:
The external execution feature was refined using feedback from a real Evohome installation, and additional experiences, suggestions, and edge cases are welcome through GitHub Discussions.
Thank you for the link, I missed that, obviously. Is there also a quick way to remove a device which I accidentally accepted as being mine, but isn’t?
me → not me
Just change the _owner to not-me or anything other than the default ‘me’.
To remove it from HA, there is a new Action remove_device
Ramses RF pre-release 0.60.5 is out in HACS.
It contains numerous fixes and UI tweaks, plus a brand new feature to extend the RF coverage in large setups (or with thick walls) by using multiple HGI RF units (MQTT only, for now but a mix with USB dongles is planned).
Backup first!