Check your system controller sensor in Developer Tools, you should see the the TRVs associated with the zone as actuators, they start with 04:xxxxxx
It should be automatic without any special configuration, best practice is to add all devices to your known list.
this is the point that my problem become complicated, i read something about to make a list but i dont how and i dont know where.
i am in developers tools and for my apprear like this.
Thank for your help friend 
Follow the steps from our Wiki on Configuration: 2. Configuration ¡ ramses-rf/ramses_cc Wiki ¡ GitHub
A next âstableâ Ramses RF release 0.55.3 is available in HACS.
yes i read it and the USB dongle its correct, it appear in home assistant but the entities that it give me, are wrong it give me sensor.room and i need climate.room i read that i need to create a list called known_list and i think it refer in configuration.yaml of home assistant.
im doing that rigth now but the issues still happend.
Itâs all done through the UI workflow through the integration page
Here is an example system. However, you want to disable âaccept packets from known devices IDs onlyâ until you have a fully working system. Once everything is working, set this to true/on.
Here is the documentation link with more information
i do it
Than you for all your help
yes it should refresh once you put in the gateway
"18:123456":
alias: Gateway
class: HGI
123456 = your gateway ID
ok the configuration is correct if i do this ?
Hello All,
I have four ramses_esp dongles (various versions, but two are the latest) I no longer use/want. I also have a HGI80.
Is anyone interested in having these at no cost (UK) or cost of postage (EU)?
@EgbertB WOudl teh HGI80 be of use to you?
It would be a shame to throw them in the bin.
Please PM me - first in, best dressedâŚ
Iâm a little stuck here, and couldnât find an answer.
We have an EvoHome installation with an HGI80. My aim is to switch off the heating if I have an open window, and turn it back on as soon as the window is closed. For that I have placed a (zWave) sensor on the window.
If I do this with the Honeywell Total Connect Comfort integration, I can switch the room to off (and auto), as follows:
action: climate.set_hvac_mode
metadata: {}
data:
hvac_mode: "off"
target:
entity_id: climate.slaapkamer
However, with the RAMSES_RF integration, I cannot turn off the room. I can only choose between Heat and Auto. Off is not in the drop down box. If I replave Heat with Off in the yaml, it gives an error.
The only place I (think I) can set the HVAC mode to âoffâ is when lowering the temperature. This results in the following YAML:"
action: climate.set_temperature
metadata: {}
target:
device_id: 08358f4e9c15d2f89b478c3b3fec4daa
data:
temperature: 5
hvac_mode: "off"
However, this only turns it off temporarily. The next time there is a scheduled temperature, the device is turned on again.
Setting the preset mode to âpermanentâ like the following:
actions:
- action: climate.set_temperature
metadata: {}
target:
device_id: 08358f4e9c15d2f89b478c3b3fec4daa
data:
temperature: 5
- action: climate.set_preset_mode
metadata: {}
data:
preset_mode: permanent
target:
device_id: 08358f4e9c15d2f89b478c3b3fec4daa
Results in only the last action taking place, so either the temperature is set to 5 degrees, but temporarily, or the current temperature is fixed permanently but not lowered.
Any ideas?
Welcome to long standing ramses_cc issue 129
Fix not expected yet.
OK, so switching the room off cannot be done (yet).
How about setting the room temperature permanently to 5 degrees? Because I couldnât get that to work either.
Anyone else having issues with 0.55.3 and 0.55.5? When I install it my faked temperature sensors are stuck on the last reported temperature and become unavailable after a reboot, as do some BDR91 readings. Had to revert back to 0.55.2 to get it working again.
Iâve created issue 537 to investigate.
Please add your current config plus a 24h ramses packet log there so we can study exactly what happens.
Note that HA has changed the way entities are named. We had to adapt the code, or the Ramses RF integration would no longer load in a few months.
See the 0.55.3 release notes.
Can you check the entities (names) available in the 0.55.5 integration/device?
Tried 0.55.3 again and so far, so good, so maybe itâs just 0.55.5? If you want the 24h packet.log from 0.55.5 Iâm afraid I canât help you. Itâs a bit of a catch 22, because I use Home Assistant and Ramses to be able to use 2 different non Honeywell temperature sensors for the main living quarters. The misses will have my head on a platter if the room isnât heated for 24hđ
Is there something else I can do to help?
Can you attach your 0.55.5 system log with debugging turned on for Ramses RF, just for the first 10 mins. or so until your sensors freeze (wait till the sun is shining!).
There must be some errors or warnings that will tell us more.