No - you can have both integrations at the same time - they are compatible. They do different things, too, so are complimentary (i.e. you may still want to run both even if you get ramses_cc working).
I do not test/dev with Windows - but WSL works OK (I do my test/dev of WSL2/Ubuntu). Others may suggest a Windows solution.
Note: the above will only test Rx. It is quite common for these units - for various reasons - to Rx, but not Tx (e.g. using the wrong bootloader in the Arduino IDE).
Is a possible use case to turn the pump of the underfloor heating on and off with a shelly (or similar) instead of using a zone valve?
I noticed during a underfloor heating pump failure that hardly any water goes into the floor.
I am curious whether using a shelly instead of using a bdr91 is already implemented.
You should be able to do this just using regular HA automation, i.e. when a particular zone changes state, e.g. idle to heat and vice/versa, then trigger a relay on, e.g your shelly.
I run multiple pump circuits this way, the BDR91 is only connected to the heat source to trigger global heat demand.
Maybe this makes it clearer: I have 5 pumps which each serve 1 or more radiator zones - so each zone is a sensor and multiple TRV’s. Evohome takes cares of the TRV’s and global heat demand through a single BDR91. When a zone is triggered (from my perspective an HA thermostat state), automation will trigger the relevant pump for that zone. This saves me energy - the original setup had the BDR91 triggering both heat demand and all the pumps together.
I’m not 100% on your automation (maybe you might post the YAML here?), but it wouldn’t be uncommon for the zone sensor to have measured_temp < setpoint, but all the TRVs have their valves closed (i.e. water circulates around the zone, but does not enter the radiators).
You may want to consider turning on the pumps (are they pumps or valves?) if:
system heat_demand > 0 (so the heat source is providing heat), and
max(heat_demand of all TRVs) > 0 (so at leave one TRV has it’s valve open)
Its indeed a little more complicated: each zone automation has a condition to check that relay_demand on the BDR91 > 0 and that the demand relay is actually on. Also automations on the controller state itself, e.g. if the whole system was off, away mode etc will trigger zone automations to trigger pumps where necessary, if the controller switches off, then turn off all pumps…its actually quite a bit of YAML.
I dont seem to log anything though. There is no packet log created.
I assumed the radio dongle was not working.
How do I know what to put in the ‘Known_List’ if I dont see anything in the log?
Is there a new version of ramses_RF I was unaware! How do I update!
Without a known_list (and assuming you don’t enforce_known_list: true - it will accept packets from all devices. It is OK do do this until you know the device ID off all your devices.
Sorry, I misled you before:
Is actually saying you should really specify one - and only one - HGI in your known_list. But if you don’t things will probably be OK - you will certainly get packets in your packet log.
If your packet log remains empty, and your configuration is only:
Other solutions will be much cheaper, but the quality can be very variable - many people have bought one of these, after spending (wasting?) money on alternatives.
Yep, thats what I bought from indalo-tech!
I have had it a while as I have a busy work/home life and not had the time to play until now with this kit.
I presume working out which Evohome components are which is a case of trial and error.
How long should I leave it before creating the known_list?
