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

Share your Projects!
1580

I have enabled the following:

logger:
  default: warning                  # don't use debug

  logs:
    # homeassistant.core: debug
    custom_components.evohome_cc: warn
    ramses_rf.message: info

evohome_cc:
  serial_port: /dev/ttyUSB0
  scan_interval: 60
  packet_log: /config/evohome_cc_packet.log
  config:
    enforce_known_list: true
  schema:
    controller: 01:223036
  restore_state: false
  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

Restarting the systeem gets back the controller, Iā€™m going to monitor it how long it takes.

When it reoccurs Iā€™ll send you the logs.

1581

@zxdavb Seeing temperature sensors not becoming available. This is from just this morning:

Logger: ramses_rf.protocol.message
Source: /usr/local/lib/python3.9/site-packages/ramses_rf/protocol/message.py:307 
First occurred: 8:54:13 (210 occurrences) 
Last logged: 12:39:03

I --- 04:030580 --:------ 01:210309 2309 003 080834 # has expired (201%)
I --- 04:030582 --:------ 01:210309 3150 002 0300 # has expired (121%)
I --- 01:210309 --:------ 01:210309 0009 006 FC00FFF900FF # has expired (197%)
I --- 04:033006 --:------ 01:210309 2309 003 0A0834 # has expired (217%)
I --- 04:030580 --:------ 01:210309 2309 003 080834 # has expired (218%)

Values however are being received (example below):

2021-09-06 13:11:34 INFO (MainThread) [ramses_rf.message] || TRV:030798 | | I | temperature | || {'temperature': 22.58}
2021-09-06 13:11:39 INFO (MainThread) [ramses_rf.message] || TRV:032930 | | I | temperature | || {'temperature': 22.26}
1582

Did anyone tried to control the radiator manually? When i change the temp at the radiator he reboots himself.

1583

I had it again at 2:26:39, attached the log: Logs

To make the controller available again, I changed the mode in home assistant. Rooms like climate.woonkamer where also unavailable at 22:09:39.

1584

Thanks for the logs.

OK, I think Iā€™ve worked it out (unavailable) - there was a feature Iā€™d implemented, but that that wasnā€™t properly turned on. I have turned it on now - am testing, and will probably push it tonight.

2 Likes
1585

0.14.4 released - fill ya boots!

1586

Thx a lot for your hard work.

1587

Hi David

Just upgraded to 0.14.4, in my case, all of the HR91 temperature sensors are remaining permanently unavailable, other associated properties such as their heat demands are working.

To confirm. The values are being received:

2021-09-07 20:41:38 INFO (MainThread) [ramses_rf.message] || TRV:032930 | | I | temperature | || {'temperature': 22.83}
2021-09-07 20:41:59 INFO (MainThread) [ramses_rf.message] || TRV:033030 | | I | temperature | || {'temperature': 21.87}

Dan

1588

@DanRP - can you ping me a copy of your schema? Use the new schema entity - have a look at the developer, state tab in lovelace.

1589

I can reproduce this bug. Fix shortly.

1590

Hi @zxdavb , version 0.14.4 hasnā€™t fixed the controller unavailable bug for me sorry! After a few hours (about 6), every device becomes unavailable regardless of its state (i.e. Off, Eco, etc). In my logs linked below, this happened at 01:26:23. Iā€™ve included the whole hour just in case there are any clues around the event. If I change the mode to Off/Heat, etc, everything becomes available again for about another 6 hours.

http://gofile.me/4aXPm/uzupX2nw0

1591

Thanks David. Also noticed with 0.14.4, that the hot water entity is now not becoming available. This worked in the prior release.

1592

I have identified this issue - it is a simple typo. Fix coming.

1593

I have identified a bug that would cause this ā€¦ testing.

1594

Getting the new version to work with the (existing) fake sensor was a bit of hassle (but I had been warned more then enough upfront).

The most important point was to set ā€˜restore_stateā€™ to false, otherwise you might get Python errors on dict objects (probably new format now), took a while before I figured out that it wasnā€™t an error in my config file. Then you have to create the sensor again (which was clear and easy). Then the calls to put_zone_temp failed, that was due to some issue with devices that werenā€™t part of my Evohome system, so added them all to the block_list (it is clear that the known_list advice has a reason ;)). Then everything was up and running again. Nice that there is a sensor with the schema in it, an easy way to check the sanity of the setup :slight_smile: .

Thanks again for all your effort!

1595

@zxdavb David, 0.14.5 looks good to me for all temperature sensors (inc HW). The HW entity however is still remaining unavailable.

1596

Well, progress is being madeā€¦

I will look at the DHW sensor over the weekend - keep the bug reports coming in!

1597
1598

Yup, I agree - 0.14.5 seems to be very stable over the last 24 hours, thank you for your hard work on this @zxdavb. water_heater.stored_hw is also unavailable for me too.

1599

I am still using v0.11.0 with a faked sensor, i have now this in my config:

  schema:
    controller: 01:155341
    zones:
      "04": {"sensor": {"device_id": "03:256005", "is_faked": true}}

Can i remove the zones configuration under schema and change allow list to known_list and change the faked sensor to:

- 03:256005
- 03:256005: {faked: true}

Or do i need to remove the sensor from the zone on the evohome touch controller and add a new faked one?