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

Share your Projects!
1870

Does anyone else have a Ideal combi boiler and opentherm running on it?

1871

Well, thatā€™s annoying. The only change made, was to tweak logging and restart:

2021-11-20 07:30:30 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.07_014869_temperature, old_state=<state sensor.07_014869_temperature=unavailable; restored=True, state_class=measurement, supported_features=0, device_class=temperature, unit_of_measurement=Ā°C, friendly_name=Stored Hot Water @ 2021-11-20T07:25:37.272702+00:00>, new_state=<state sensor.07_014869_temperature=67.9; state_class=measurement, controller_id=01:050858, device_id=07:014869, domain_id=FA, domain_name=Stored HW, unit_of_measurement=Ā°C, friendly_name=Stored Hot Water, device_class=temperature @ 2021-11-20T07:30:30.376748+00:00>>

Prior to that, over the course of about 7-10days since I upgraded from 0.14.x ā†’ 0.16.x, HA was probably restarted 4-5 times in total (trying with restore_state: false) and it was missing every time. Typical! :slight_smile:

I note some others further up this thread/topic mentioned that it comes and goes, this is the first time it has appeared for me on 0.16.x, so I guess we shall see - will leave the logging enabled for now.

1872

There was an issue with an earlier buildā€¦ was that it?

1873

Went unavailable again, even though I can see the broadcast packets from the 07 device:

[core-ssh config]$ grep 014869 home-assistant.log|grep temp
2021-11-20 07:25:30 INFO (MainThread) [ramses_rf.message] || DHW:014869 |            |  I | dhw_temp         |      || {'temperature': 67.9}
2021-11-20 07:25:37 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.07_014869_temperature, old_state=None, new_state=<state sensor.07_014869_temperature=unavailable; restored=True, state_class=measurement, supported_features=0, device_class=temperature, unit_of_measurement=Ā°C, friendly_name=Stored Hot Water @ 2021-11-20T07:25:37.272702+00:00>>
2021-11-20 07:30:30 INFO (MainThread) [custom_components.evohome_cc.sensor] Found a Sensor (temperature), id=07:014869
2021-11-20 07:30:30 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.07_014869_temperature, old_state=<state sensor.07_014869_temperature=unavailable; restored=True, state_class=measurement, supported_features=0, device_class=temperature, unit_of_measurement=Ā°C, friendly_name=Stored Hot Water @ 2021-11-20T07:25:37.272702+00:00>, new_state=<state sensor.07_014869_temperature=67.9; state_class=measurement, controller_id=01:050858, device_id=07:014869, domain_id=FA, domain_name=Stored HW, unit_of_measurement=Ā°C, friendly_name=Stored Hot Water, device_class=temperature @ 2021-11-20T07:30:30.376748+00:00>>
2021-11-20 08:30:31 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.07_014869_temperature, old_state=<state sensor.07_014869_temperature=67.9; state_class=measurement, controller_id=01:050858, device_id=07:014869, domain_id=FA, domain_name=Stored HW, unit_of_measurement=Ā°C, friendly_name=Stored Hot Water, device_class=temperature @ 2021-11-20T07:30:30.376748+00:00>, new_state=<state sensor.07_014869_temperature=unavailable; state_class=measurement, unit_of_measurement=Ā°C, friendly_name=Stored Hot Water, device_class=temperature @ 2021-11-20T08:30:31.318806+00:00>>
2021-11-20 09:05:48 INFO (MainThread) [ramses_rf.message] || DHW:014869 |            |  I | dhw_temp         |      || {'temperature': 66.86}
2021-11-20 09:10:03 INFO (MainThread) [ramses_rf.message] || DHW:014869 |            |  I | dhw_temp         |      || {'temperature': 65.82}
2021-11-20 09:10:48 INFO (MainThread) [ramses_rf.message] || DHW:014869 |            |  I | dhw_temp         |      || {'temperature': 64.59}
2021-11-20 09:11:18 INFO (MainThread) [ramses_rf.message] || DHW:014869 |            |  I | dhw_temp         |      || {'temperature': 61.94}
2021-11-20 09:12:18 INFO (MainThread) [ramses_rf.message] || DHW:014869 |            |  I | dhw_temp         |      || {'temperature': 51.87}
2021-11-20 09:13:48 INFO (MainThread) [ramses_rf.message] || DHW:014869 |            |  I | dhw_temp         |      || {'temperature': 40.59}

I have some things to do this morning, will package up the logs and get them over later on/tomorrow.

1874

Iā€™m seeing the same with the latest build

1875

For those with unavailable sensors, please us this logging your configuration.yaml:

logger:
  default: warn
  logs:
    homeassistant.core: debug

    # custom_components.evohome_cc: info
    custom_components.evohome_cc.sensor: info

    ramses_rf.message: info
    ramses_rf.protocol.message: info

You need to restart, and run for an hour - then provide me the HA log, and the corresponding packet.log.

I am still trying to work out whatā€™s going onā€¦

1876

Have sent you an email.

1877

I donā€™t get it, for months it works ok but at the moment there is nothing happening anymore. I dont see any climate or sensors entities anymore.
Logging gave this back:

2021-11-21 11:12:19 INFO (MainThread) [custom_components.evohome_cc] Params = {'system': {'tpi_params': None, 'system_mode': None, 'language': None}, 'stored_hotwater': {}, 'underfloor_heating': {}, 'zones': {}}
2021-11-21 11:12:19 INFO (MainThread) [custom_components.evohome_cc] Status = {'system': {'heat_demand': None, 'heat_demands': None, 'relay_demands': None, 'relay_failsafes': None}, 'faultlog': None, 'stored_hotwater': {}, 'underfloor_heating': {}, 'zones': {}, 'schedule_outdated': True}

It looks like he dont get any info anymore.

1878

Are you using a HGI80?

1879

Yes i use a HGI80 (I have a opentherm system)

1880

It looks like your duty cycle is blown - the HGI80 will no longer transmit until it resets itself, or it is reset (disconnected from / reconnected to USB).

ramses_rf is pretty pushy - that is why the cache is so important - without it, it sends lots of packets in a short time, and multiple back-to-back restarts of HA can exceed the limit imposed by the HGI80.

If youā€™re using a Honeywell HGI80, donā€™t do multiple-back-to-back restart of HA with restore_state: false

1881

All, I am only interested if a sensor is permanently unavailable not temporarily / infrequently unavailable.

1882

Your system is misconfigured (below is slightly edited for readability):

(venv) dbonnes@vm-builder ~/c/ramses_rf (master)> cat .secrets/lloyda/2021-11-21.log | grep 'RP.* 000C ... 0[03]' | tail -2 | python client.py -ns parse
 ...
08:54:42.127 || CTL:185426 | HGI:136212 | RP | zone_devices     | 0008 || {'zone_idx': '00', '_device_class': '08', 'device_class': 'rad_actuators', 'devices': ['04:003278', '04:003222', '04:003192']}
08:54:43.957 || CTL:185426 | HGI:136212 | RP | zone_devices     | 0308 || {'zone_idx': '03', '_device_class': '08', 'device_class': 'rad_actuators', 'devices': ['04:003286',              '04:003192']}

TRV 04:003192 is an actuator in two different zones.

You will have to destroy & re-create the zone that shouldnā€™t have that TRV in it.

1883

The nature of evohome is that it is very easy to have a misconfigured system.

If I notice an error in your system configuration, that does not necessarily mean the rest of it is fine. It is up to you to check

A big hint would be something like this in your log files:

Inconsistent state: 04:003192 (TRV) changed parent: 01:185426_00 (radiator_valve) to 01:185426_03 (radiator_valve), (try restarting the client library)
1884

When my system is back in service i will send you a log. I misread your message. I use a arduino nano for evofw.

1885

Can all those with issues upgrade to 0.16.12 and weā€™ll try to sort these issues out using that versionā€¦

For unavailable sensors, I am only interested if sensors are permanently unavailable, and Iā€™m not concerned if theyā€™re unavailable at times (the RF protocol has no QoS).

I am interested in all zone issues.

You need to use this logging:

logger:
  default: warn
  logs:
    homeassistant.core: debug

    # custom_components.evohome_cc: info
    custom_components.evohome_cc.sensor: info

    ramses_rf.message: info
    ramses_rf.protocol.message: info

I need a fresh restart of HA that runs for at least an hour. I need the HA log, the packet log(s), and your configuration of evohome_cc in configuration.yaml.

To be clear, the HA log, and the corresponding packet log must include the restart of HA.

You must have restore_state: false if you have changed your evohomeā€™s configuration (added/removed a zone, added/removed/moved a device).

Please PM with the above, and a clear description of what is going wrong. Please donā€™t say: ā€œIā€™m having the same problems as everyone elseā€, or ā€œIā€™ve got unavailable sensorsā€ - your message will be ignored, sorry.

The better job you do of the above, the more likely it will be that it is your system Iā€™ll look at first.

1886

Thanks. Yes spotted that this morning and deleted both zones. Not setting restore_state to false caught me out at first, but now sorted.

1887

This version has fixed all my errors and warnings.

Thanks for the hard work.

1888

Someone has kindly sent me a packet log that does not satisfy the above criteria.

To be clear, the HA log, and the corresponding packet log must include the restart of HA.

1889

Please now use 0.16.12 - it has increased logging that will highlight those with poor reception.

In your logs you may see:

WARNING ... [ramses_rf.protocol.transport] ... QoS: IS_EXPIRED (giving up) ...
WARNING ... [ramses_rf.entities] ... Sending now deprecated for 01:000730 ...