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

Share your Projects!
4510

I cannot honestly recall but I certainly started with the configurational.yaml and converted. But since then have cleared cache and the config.yaml has been hashed out - I had thought it autopopulated after I cleared cache.
I have edited now and it is this as per your reference:

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

I have probably made a bit of a mess of the whole install over time and the change to the later config flow, though it seems to work ok.
If I query the gateway status through developer tools/Template I get the following:

id: 18:203270
schema: 
'01:081083':
  system:
    appliance_control: null

config: 
enforce_known_list: true

known_list: 
- '01:081083':
    class: controller
- '07:025191':
    class: dhw_sensor
- '13:173107':
    class: electrical_relay
- '04:027656':
    class: radiator_valve
- '34:150655':
    class: thermostat
- '13:001489':
    class: electrical_relay
- '34:027677':
    class: thermostat
- '13:055679':
    class: electrical_relay
- '34:150571':
    class: thermostat
- '13:001522':
    class: electrical_relay
- '04:023780':
    class: radiator_valve
- '04:027356':
    class: radiator_valve
- '04:027722':
    class: radiator_valve
- '04:023774':
    class: radiator_valve
- '04:027650':
    class: radiator_valve
- '04:027714':
    class: radiator_valve
- '04:027720':
    class: radiator_valve
- '04:027648':
    class: radiator_valve
- '04:027358':
    class: radiator_valve
- '04:027646':
    class: radiator_valve
- '04:027718':
    class: radiator_valve
- '04:027716':
    class: radiator_valve
- '04:027360':
    class: radiator_valve
- '34:063533':
    class: thermostat
- '13:224329':
    class: electrical_relay
- '13:003271':
    class: electrical_relay
- '34:150657':
    class: thermostat
- '18:203270':
    class: gateway_interface

block_list: 
is_evofw3: true
device_class: problem
friendly_name: HGI 18:203270 Gateway status

All my three Schema’s (through the DEveloper tools/States) say unavailable. Indeed I have a lot of unavailable throughout.
But as I say all seems to work satisfactory.

4511

Just taken the plunge and upgraded to the config flow version (0.42.0) from the latest non-config flow version. I let the installation create the config flow entry from configuration.yaml.

A lot of things appear to be working, but one thing that is not is send_cmd. Looking into this, if I try and view the Advanced Features under Configuration, I get a pop up that simply says ‘Error’. I also noticed that the schema is not populated - not sure if that is an issue or not.

So I’ve tried to look at what has been stored in .storage/core.config_entries, and there is nothing in there from ramses.

Can anyone shed any light on what might be happening here?

4512

How are people displaying the information from this integration? I see some examples in the thread, and also on the Wiki, but they are all quite old. Is it just the default Climate card, or are people doing something more advanced?

4513

The templates are somewhat hidden in the Wiki

HA Custom Cards by @Galaxy Explorer

HA Custom Card (PIV) By @Behold81

HA Custom Card by @janvkem

HA Custom Card by @lloyda

HA Custom Card by @vrobenmat

The cards that I designed serve my purposes just fine, for example

image
image507×628 69.8 KB

image
image747×587 19.5 KB

4514

Having looked a bit closer, I think send_cmd may be working. However, the schema is still not populated in the configuration, and I can’t get into the Advanced Features - get a error popup.

4515

Hi All,
It there anyway to fake a TRV, I’ve got a room with valveless radiator that I’ve like to be able to heat when all the remaining zones have TRVs with 0% demand.

4516

Dear user,
For your information, I successfully forwarded USB evofw3 connected on a Rpi to a HyperV HAOS using USBIP.
I make a little Howto if someone is interested.
Now, I need to make the configuration.
My goal will be to forward the % heat output of the EVOHOME to a Vaillant EcoTECPLus VCW296/5-5 (BE) using the ebus interface (not yet investigated into it).
so, my boiler will be able to modulate in place to Start/Stop at 100% (not the goal of a condensation Boiler)
I know about the interface OpenTherm, but I need a unofficial module VR33 a bit more costly and maybe more complex.
So, I’ll try first with ebus