It should be reporting the current water temperature:
(my figures do not look right, because I have a DHW kit, but no actual DHW cylinder)
Has it only just gone wrong?
There should be an 07:xxxxxx device that is a temperature sensor - what does it show?
Thanks, I’ll give a test on my test env.
It’s never shown an actual temperature. I’d also only got the controller ID in the allow-list so I’ve also added the 07 device to that and restarted. Every non-controller sensor entity I’d actually disabled in Home Assistant just to keep things cleaner as I wasn’t using them, but I’ve enabled it and will keep my eye on it to see if it starts to report any data over the next hour or so. At the moment it looks like this:
“Evohome DHW Temperature” is the 07:xxxxxx entity I’ve just re-enabled.
This sounds like the cause of your issue - if the 07: device is being filtered out, then you wont have DHW temps.
NOTE: Device filtering is now very strictly enforced in evohome_cc (in addition to the above) - all your devices must be in the allow_list.
Ha! There we go… needed either the sensor to be enabled or the 07 device adding to the allow-list. Not sure which, but it’s pulling in a temperature for the first time. Thanks for the help.
I can send you the packet.log, only how can I send it to you?
I reinstalled the master branch but still get the error message when I change the temperature.
just updated and now i could remove the bad devices in home assistant.
and with this verion i got a new entity for the BDR91 modulation level.
Sorry - I wasn’t clear…
There should be more entities than you’ve listed above - perhaps you could send me a log file, so I can bugfix?
(the above sentence is in response to the paucity of OTB entities, from your above quote)
Just post the packet log somewhere & PM me the link?
I have fixed/pushed to the master branch - it is not 100% clear to me if you’ll see it, let me know - you have to “Reinstall” via the HACS UI.
(the above sentence is indicating that the latest commit to the master branch fixes this bug)
Enabling the 07: sensor entity in HA was not the fix to your problem.
Not having the 07: in your allow_list was the issue.
All: If you have an
allow_list, it must now include ALL your devices.Since allow_list is applied in evohome_cc as well as ramses_rf, you should have all your devices in the
allow_list, and then disable any unwanted entities in HA.
@hsluis The latest commit to master definitely works fro me - did you restart the HA server after Reinstall-ing evohome_cc?
Yes I did, I just tried again but still the same issue.
I am sorry - it works for me 
That is weird 
maybe the logging below helps to understand what is wrong at my site?
[547499830576] ‘EvoBroker’ object has no attribute ‘hass_config’
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 167, in handle_call_service
await hass.services.async_call(
File “/usr/src/homeassistant/homeassistant/core.py”, line 1481, in async_call
task.result()
File “/usr/src/homeassistant/homeassistant/core.py”, line 1516, 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 726, 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 250, in set_temperature
if self._broker.hass_config[DOMAIN][CONF_ADVANCED_OVERRIDE]:
AttributeError: ‘EvoBroker’ object has no attribute ‘hass_config’
In the latest commit, this is:
if self._broker.config[DOMAIN][CONF_ADVANCED_OVERRIDE]:
Super weird, this time I replaced the files manual and I can adjust the temperature again. 
But when I change preset mode I get the error below:
[547542845856] Invalid args: For temporary_override, setpoint cant be None
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 167, in handle_call_service
await hass.services.async_call(
File “/usr/src/homeassistant/homeassistant/core.py”, line 1481, in async_call
task.result()
File “/usr/src/homeassistant/homeassistant/core.py”, line 1516, 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 726, 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 450, in async_set_preset_mode
await self.hass.async_add_executor_job(self.set_preset_mode, preset_mode)
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 246, in set_preset_mode
self.svc_set_zone_mode(mode=ZoneMode.TEMPORARY)
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 797, 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 559, in set_zone_mode
raise ValueError(f"Invalid args: For {mode}, setpoint cant be None")
ValueError: Invalid args: For temporary_override, setpoint cant be None
I have noticed that my controller (heat_demand) remains unavaible after a restart 16hours ago.
Also sensor.10_040239_rel_modulation_level remains unavailable
i have the same with the heat demand of the controller.
After running for a few hours (from a clean build), I have the following:
2021-05-19 16:15:01 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=climate.controller, old_state=<state climate.controller=heat; hvac_modes=['heat', 'off', 'auto'], min_temp=None, max_temp=None, preset_modes=['none', 'away', 'custom', 'home', 'eco'], current_temperature=21.0, temperature=5.0, hvac_action=idle, preset_mode=eco, heat_demand=0.0, heat_demands=FC=0.0, relay_demands=FA=0.0, F9=0.0, FC=0.0, system_mode=system_mode=eco_boost, until=None, tpi_params=cycle_rate=6, min_on_time=5.0, min_off_time=0.0, proportional_band_width=None, friendly_name=Controller, supported_features=17 @ 2021-05-19T13:51:16.678787+01:00>, new_state=<state climate.controller=heat; hvac_modes=['heat', 'off', 'auto'], min_temp=None, max_temp=None, preset_modes=['none', 'away', 'custom', 'home', 'eco'], current_temperature=21.1, temperature=5.0, hvac_action=idle, preset_mode=eco, heat_demand=0.0, heat_demands=FC=0.0, relay_demands=FA=0.0, F9=0.0, FC=0.0, system_mode=system_mode=eco_boost, until=None, tpi_params=cycle_rate=6, min_on_time=5.0, min_off_time=0.0, proportional_band_width=None, friendly_name=Controller, supported_features=17 @ 2021-05-19T13:51:16.678787+01:00>>
It includes:
... new_state=... heat_demand=0.0 ...
[EDIT] Oh! Hang on…
