This is really good, kinda the last step to be able to put the controller in a cupboard and do everything from HA.
Just made the jump from 0.18 to 0.20 with the config update, went flawlessly!
Question: HR91/92âs seem to be difficult to get hold of at the moment. There is mention of sensor faking, but would TRV faking (using e.g. a zigbee TRV) also be possible? or completely off the table?
@dpe I would be grateful if you could edit the wiki to address an deficiencies that made it difficult for you to set up ramses_cc without having to resort to asking for help here.
It is possible to set up two controllers - IIRC I advised someone else how to do it & asked them to write it up in the Wiki. Did you have a look there?
If you canât find it there, or in this thread, let me know by tagging me.
No, you donât need two radios.
Could you add this to the Wiki?
I am working towards this - IIRC, I asked a question about such TRVs, above, and didnât get an answer.
In short - what are the states & services typically available with these TRVs?
Thereâs a big list here. Typically there is temp, setpoint, batt, window det, lock.
The premium ones, e.g. Danfoss Ally have % opening, lock, external temperature sensor, local temperature battery, window det, setpoint.
But for zigbee they would all be abstracted through ZHA, so I guess the question is if ZHA exposes sufficient states/attributes/services for a climate device to fake a TRV.
I may get one to have a play.
Minimum needed is for the TRV to accept a setpoint (service call to that integration), and report a temperature (state or trigger).
It would be preferred to have them accept a % opening (service call) too.
The difficulty is that the algorithm for converting from setpoint|temperature to % opening is not known.
It is on my todo listâŚ
- Download/Upload zone/DHW schedules
- Multiple evohome controllers
- BDR (relay) faking
- TRV faking
Iâve even started controller faking, but that is proof of concept stuff only, at this stage.
If youâre interested, in multiple controllers, for now:
- use ser2net (see wiki)
- duplicate the CC with a different name
- enforce known_list filters, so you donât get duplicate entities
I have 2 controllers and ended up using 2 raspberry pi each running their own ha with ramses_cc and remote home-assitant which reports into my main ha instance.
I have found this to be the best way for me because it allows me to upgrade or make changes to one system without effecting the other.
I can control it all of my main ha as well which is a bonus.
All:
I would recommend a scan_interval of 60 seconds (or even less?).
There is no real benefit from having 300 seconds (as previously recommended), as all that is happening is youâre getting more changes every 5 mins rather than less changes every minute for 5 minutes.
That is, youâre getting the same number of changes every 5 minutes.
The advantage is you get better precision of time stamps with a shorter interval.
ramses_cc:
scan_interval: 60
2 Likes
IIRC, a round thermostat (34:) together with a BDR and gateway cannot be set as a controller in the config schema?
I have just pushed 0.20.22g, which includes a fix for this false error message.
You may also notice faster startup: when entities move from unavailable to available. As recommended before, set your scan_interval to 60 seconds (although this wasnât/isnât the cause of the issues with startup).
This release is strongly recommended for all.
Im looking into ser2net for multiple controllers and Im wondering if I have to compile ser2net myself? Im running HA on Odroid C2 ⌠
Depends on how you are running HA - OS, Supervised or Core?
OS, the easiest one.
This is the only âuseâ out of this Odroid C2, which is perfect for me. There arent any other âsupportedâ distros available for years already for this SBC, only this HA OS.
So compiling it is the only way?
Im searching for a binary and cant seem to find it. If I decide to compile, I would do a VM under HyperV and transfer the binary⌠The question is now if it would survive upgrades, etc. in this HA OS setup?
Then ser2net will probably be painful 
- you need to be able to get out to plain vanilla linux, which I understand is difficult with HA OS
I didnât know ser2net wasnât included with HassOS - perhaps see how you get on raising it as an issue at Issues ¡ home-assistant/operating-system (github.com)?
It was kinda wontfixed 3y ago, but things may have changed - would be worth asking again.
(I presume when you say gateway, you mean a RFG100, and not a HGI80).
Correct. Such a system would be doable, but I donât have time for that⌠They should appear as sensors, though, if you include them as orphans:
ramses_cc:
orphans_heat: [13:123456, 30:123456, 34:123456]
I canât recall if an RFG100 is a first-class citizen, or not.
Looks good this end, no new warnings/errors on start up.
Should this be updated in the wiki? Is there a new default?
Good point - it is in the wiki, here. I have just updated it with the new recommendation.
In releases 0.20.22x and below, the default is 300. IN 0.21.0 and above, it will be 60.