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

Share your Projects!
2531

yes the same message. All climate entities are unavailable.

2532

try:

ramses_cc:
  scan_interval: 5
  serial_port: /dev/ttyUSB-EVOHOME
  restore_cache:
    restore_schema: false
    restore_state: true
  ramses_rf:
    disable_discovery: false
2533

doesnā€™t solve the problem.

2534

OK. Please re-describe your problem (so Iā€™m clear).

Please provide a home-assistant.log.

2535

After upgrading to 0.20.13 I get all climate entities in ā€œunknownā€ state even their name isnā€™t loaded in the entity. The first few minutes of restarting HA I have to wait for the entities to load, currently itā€™s > 10 min and still most is undefined or unknown. You can find some logs here: https://cloud.delodder.be/s/95iAWxXBP4DxXMz

My config:

ramses_cc:
  serial_port: /dev/ttyUSB0
  restore_cache: true
  packet_log:
    file_name: /config/ramses_cc_packet.log
    rotate_bytes: null
    rotate_backups: 7
  ramses_rf:
    enable_eavesdrop: false
    enforce_known_list: false

  schema:
    controller: 01:223036
  known_list:
    - 01:223036
    - 10:040239
    - 04:231770
    - 04:231772
    - 04:231774
    - 04:231776
    - 04:050559
    - 04:155445
    - 04:155403
    - 04:081849
    - 04:155443
    - 04:155407
    - 04:155551
    - 04:155533
    - 04:155537
2536

Can you try:

ramses_cc:
  serial_port: /dev/ttyUSB0
  restore_cache:
    restore_schema: false
    restore_state: true

I also recommend:

  ramses_rf:
    enforce_known_list: true
2537

Still the same after doing the changes

2538

I am about to push 0.20.14ā€¦

2539

@cinnamon @phdelodder

Please try 0.20.14 and report back.

2540

Please try 0.20.15 and report back.

2541

Working with 0.20.15!

Do I need to keep this or can I revert to my previous config?

2542

My expectation is that you can use any configuration you like. However, I strongly recommend:

ramses_cc:
  ramses_rf:
    enforce_known_list: true
2543

@cinnamon Please remind me - is your ventilation kit Orcon, or Itho, or something else?

It would be helpful if you could give me make/models.

2544

Hi,

Just want to say that Iā€™ve switched over to the new version and so far everything is working very nicely for me.

Thanks

2545

If anyone uses HVAC (Orcon, Itho) and wants to test sensor faking for CO2 and/or humidity (i.e. you have a third-party humidity/CO2 sensor in your house):

  • You will need to download release 0.20.16 or later
  • You will need a USB dongle that is is running evofw3
  • You will need to set up a faked sensor, e.g., I have this setup:
ramses_cc:
  schema:
    orphans_hvac:
      - 32:123456  # instantiate the device on startup
  known_list:
    - 32:123456: {class: HUM, faked: true}  # set the attributes of the device when it is instantiated
    - 32:111111: {class: CO2, faked: true}
  • You will also have to bind them to your fan. Here is how you start a device binding (put the fan in listen mode first)ā€¦
service: ramses_cc.fake_device
data:
  device_id: '32:123456'
  start_binding: true
  • Here is the service call for humidity:
service: ramses_cc.put_indoor_humidity
data:
  entity_id: sensor.32_123456_indoor_humidity
  indoor_humidity: 59.3
2546

image

1 Like
2547

Obviously, the next step is to fake a remoteā€¦ this will require a change to the schema that I am currently sorting out.

2548

Iā€™ve just upgraded to 0.20.15, and I think I have it working with my setup below. Iā€™ve got lots of new things from my Nuaire PIV too.


  ramses_cc:
    serial_port: /dev/ttyACM2
    packet_log: /config/packet_logs
    restore_schema: true
    known_list:    
      - 10:051349 # Appliance Control
      - 01:169176 # main_controller
      - 18:135447 # Config Sensor
      - 04:190691 # Harry's Room
      - 04:198483 # Bedroom
      - 04:198487 # Spare Room
      - 04:112546 # Living Room 1
      - 04:198485 # Living Room 2
      - 04:038015 # Utility Room
      - 04:090189 # Kitchen
      - 32:166025: {class: CO2}
      - 32:123456: {class: CO2, faked: true}
      - 30:079129: {class: FAN}
      - 32:168240: {class: HUM}
      - 32:172534: {class: REM}
#      - 32:172522: {class: SWI}
      - 03:000001 # kitchen
      - 03:000002 # Living Room 1
      - 03:000004 # Harry's Room
      - 03:000005 # Master Bedroom
      - 03:000006 # Utility Room 
      - 03:000007 # Spare Room
#    block_list: 
#      - 10:051349    
    ramses_rf:
      enforce_known_list: true
      enable_eavesdrop: false
    schema:
      orphans_hvac:
        - 32:172534
        - 32:168240
        - 32:172534
        - 32:123456
        - 30:079129
      controller: 01:169176
      system:
        appliance_control: 10:051349

I have his error with the binary_sensor.18

Logger: homeassistant.components.binary_sensor
Source: custom_components/ramses_cc/helpers.py:30
Integration: Binary Sensor (documentation, issues)
First occurred: 15:02:12 (1 occurrences)
Last logged: 15:02:12

Error while setting up ramses_cc platform for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 250, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/ramses_cc/binary_sensor.py", line 58, in async_setup_platform
    new_sensors += [
  File "/config/custom_components/ramses_cc/binary_sensor.py", line 59, in <listcomp>
    entity_factory(broker, dev, k, **v)
  File "/config/custom_components/ramses_cc/binary_sensor.py", line 45, in entity_factory
    migrate_to_ramses_rf(hass, "binary_sensor", f"{device.id}-{attr}")
  File "/config/custom_components/ramses_cc/helpers.py", line 30, in migrate_to_ramses_rf
    if hass.states.get(entity_id).state == STATE_UNAVAILABLE:  # HACK
AttributeError: 'NoneType' object has no attribute 'state'
2549

@stevieb12345 is the error persistent? Does it happen every time you start HA?

2550

Yes itā€™s there every time I restart.