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

zxdavb · June 1, 2021, 8:44pm

So, the difficulty is that I do not have any UFH to test against. Volunteers welcome.

Version 0.9.15 just pushed - will fix the above issues, and prepare the way for (periodically) polling the system state.

Captain · June 2, 2021, 5:55am

Thank you very much for the quick fix! Will test it today.

What would you need from a “volunteer” to test the UFH? I could send you my package logs if that helps?

TheMystery · June 2, 2021, 7:13am

Updated 1,5 hour ago, most problems are solved only the names of the card are not back yet.

Edit:
a few hours later the hvac status is again away

iMiMx · June 2, 2021, 1:37pm

I still seem to be getting state Unknown unfortunately, even after clearing the saved state and restarting - this is with 0.9.15.

EDIT: I think it’s about 2 hours when it loses the state, if that helps.

The last restart, for hotwater:

When it lost state, 2 hours later:

zxdavb · June 2, 2021, 8:08pm

The good news is - this is all expected behaviour - a fix is coming.

maesenator · June 2, 2021, 9:50pm

Today I decided to upgrade from 0.9.4 to 0.9.15.
Before the update, everything was working fine including 3 fake sensors.
Now, when I start home assistant all of my climate entities have been set to unavailable and I get the following errors in my log. I’ve tried to revert back to a previous version using a snapshot but unfortunately the errors will not go away even though the version reports as 0.9.4 again.

This error originated from a custom integration.

Logger: homeassistant.setup
Source: custom_components/evohome_cc/__init__.py:192
Integration: evohome_cc (documentation, issues)
First occurred: 11:46:00 PM (1 occurrences)
Last logged: 11:46:00 PM

Error during setup of component evohome_cc
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 248, in _async_setup_component
    result = await task
  File "/config/custom_components/evohome_cc/__init__.py", line 93, in async_setup
    await broker.async_restore_client_state()
  File "/config/custom_components/evohome_cc/__init__.py", line 192, in async_restore_client_state
    await self.client._set_state(**app_storage["client_state"])
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/__init__.py", line 310, in _set_state
    self.known_devices = load_system_schema(self, **schema)  # keep old known_devs?
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/schema.py", line 368, in load_system_schema
    [
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/schema.py", line 369, in <listcomp>
    _load_system_schema(gwy, schema)
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/schema.py", line 393, in _load_system_schema
    ctl._evo._set_htg_control(_get_device(gwy, addr(htg_ctl_id), ctl_addr=ctl))
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/systems.py", line 768, in _set_htg_control
    raise TypeError(f"{ATTR_HTG_CONTROL} can't be: {device}")
TypeError: heating_control can't be: None

Logger: homeassistant.components.automation.h_slaapkamer_temp
Source: helpers/script.py:1341
Integration: Automation (documentation, issues)
First occurred: 11:50:00 PM (1 occurrences)
Last logged: 11:50:00 PM

Update evohome temp: Error executing script. Service not found for call_service at pos 1: Unable to find service evohome_cc.set_zone_temp

zxdavb · June 2, 2021, 10:31pm

For now, revert, and then:

a) delete .storage/evohome_cc before starting HA

b) If you can’t delete the file, the alternative is

set revert_state: false
restart HA
set revert_state: true
restart HA

maesenator · June 2, 2021, 10:43pm

Thank you David, I will give that a try!

Spaco · June 2, 2021, 11:15pm

To get state, actions etc working again, I re-installed 0.9.10 using HACS but noticed that ramses_rf did not revert back - so the unexpected behaviour stayed. Running HA Core, so maybe that has an impact. Used pip in the venv to reinstall and align the ramses_rf version

zxdavb · June 3, 2021, 5:14am

Ah yes - that would be right.

Hang on - a permanent solution is being tested now.

maesenator · June 3, 2021, 6:26am

I also noticed that ramses_rf stayed on 0.9.15. I’ll wait for the permanent solution, It’s a million degrees now here anyway so I don’t need the heating

phdelodder · June 4, 2021, 8:18am

I’ve noticed this in my logs:

2021-06-04 10:17:26 ERROR (MainThread) [homeassistant.components.automation.climate_set_keuken_temperature] While executing automation automation.climate_set_keuken_temperature
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 513, in async_trigger
    await self.action_script.async_run(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1216, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 350, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 368, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 750, in _async_choose_step
    await self._async_run_script(script)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 824, in _async_run_script
    await self._async_run_long_action(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 532, in _async_run_long_action
    long_task.result()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1216, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 350, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 368, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 568, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1491, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1526, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
    await self.hass.helpers.service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 760, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 548, in async_service_temperature_set
    await entity.async_set_temperature(**kwargs)
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 408, in async_set_temperature
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/evohome_cc/climate.py", line 251, in set_temperature
    self.svc_set_zone_mode(
  File "/config/custom_components/evohome_cc/climate.py", line 278, in svc_set_zone_mode
    self._device.set_mode(mode=mode, setpoint=setpoint, until=until)
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/zones.py", line 817, in set_mode
    cmd = Command.set_zone_mode(self._ctl.id, self.idx, mode, setpoint, until)
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/command.py", line 167, in wrapper
    return fcn(cls, ctl_id, zone_idx, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/ramses_rf/command.py", line 640, in set_zone_mode
    payload = "".join(
TypeError: join() takes exactly one argument (5 given)

The service I use to trigger this is:

- service: climate.set_preset_mode
      data:
        preset_mode: None
        entity_id: climate.keuken

zxdavb · June 4, 2021, 9:50am

Well, that’s embarrassing. I will push a fix in a few hours.

zxdavb · June 5, 2021, 7:38pm

Guys, there’s a can of worms at present - please bear with me.

Spaco · June 6, 2021, 11:20am

Cheers David! Hopefully not too many worms in that can…

maesenator · June 16, 2021, 11:24am

Hey David, how’s it going? The few hours turned into 12 days

zxdavb · June 17, 2021, 8:35pm

I have been updating ramses_rf, trying to sort out some deeper issues…

I wIll stop development on the library, and re-integrate it with evohome_cc, then push what I have, and take feedback on that.

maesenator · June 21, 2021, 7:54am

Alright good to hear.
Any idea if the issues I had since the upgrade to 0.9.15 are solved in this release? I’ve not been able to use the solution anymore since. I do realize it’s still a beta so no harm done but I should find a temporary work-around then because I’m currently unable to use the heating and the temperatures are going back down.

zxdavb · June 21, 2021, 8:33am

Version 0.10.0 has just been pushed - it is a huge drop. Way to many changes to be listed, see: Comparing 0.9.15…0.10.0 · zxdavb/ramses_rf (github.com)

It will fix many bugs, but will still have some issues, but will serve as a found base for those changes.

YMMV with faked devices - please don’t add any new such. Anyone having problems with faked devices, let me know.

zxdavb · June 21, 2021, 8:37am

I am sorry, I have little in the way of a test suite, and I have no capacity to implement one at present.

Moving forward, please mention bugs here, but I’ll ask you to report them to either

If you’re not sure which one to use, mention the bug here & I’ll signpost you.

This will help me keep track of these bugs.