Yes looks good, updated set restore state to false and rebooted, evohome_cc is now good als always.
set restore state to true and rebooted and evohome_cc file is still good. i shall look in an hour if it’s still so.
( I have only HR92’s)
@TheMystery I have never seen this behavior with HR92’s, only HR80s… Could you please PM me a copy of a packet log from a restart with restore_state: false
send you a pm
OK, I think for you - was just lost packets - the relevant packet is relatively long (and thus, fragile) - so you may see this behaviour again in the future… Just reboot.
OK, but it was 100% reproducible the last 3 days. But everythin is now good so we shall see,
Thanks for the support.
I am absolutely sure that one of us is right. 
1 Like
@zxdavb Just to let you know I am still waiting for it to become unavailable. Typical, I enabled the requested logging then left it alone, and it’s still working fine on 0.10.2 over 3 days later! I’ll DM you with the logs if/when it fails.
I noticed this morgning dat the zone names are away in home assistant, i don’t know for how long this is.
Yeah - I think I know what this is - just waiting for someone to send me log files, so I can implement a solution.
It’s caused by discarding stale packets, but not requesting up-to-date packets.
I am reluctant to jump in with a solution - such may be non-optimal & break more stuff elsewhere.
@hsluis and anyone else with an OpenTherm Bridge (R8810A):
Are you interested in contributing to development of OTB (OpenTherm Bridge) support? The goal will be to expose a large number of OTB message ID values as HA sensors, say:
msg_ids = {0x00, 0x01, 0x11, 0x19} # mandatory for OT
# 00 - Master/Slave status flags
# 01 - CH water temperature setpoint
# 11 - Relative modulation level (%)
# 19 - Boiler water temperature
msg_ids |= {0x05, 0x12, 0x13, 0x1A} # evohome-specific?
# 05 - Fault flags & OEM fault code
# 12 - Central heating water pressure (bar)
# 13 - DHW flow rate (L/min)
# 1A - DHW temperature
msg_ids |= {0x1B, 0x1C, 0x73} # other
# 1B - Outside temperature
# 1C - Return water temperature
# 73 - OEM diagnostic code (is supported?)
If so, I’m ideally looking for those who can (when required):
- run a bespoke release of evohome_cc (you will likely need to pull it by commit-id)
- PM me homeassistant.log / packet.log files and the .storage/evohome_cc file
- install bespoke releases of ramses_rf (
pip install git+https://github.com/zxdavb/ramses_rf.git@branch)
Sorry, I won’t have time to teach you how to do the above. Also, you can expect things to break (in HA, not with your system - all this is read-only).
I have a test env that could be used for that.
I have a R8810A and would certainly want to try to help. I guess I can get those things going, but not so much experience to do that on HA Os, but certainly willing to try.
re: OTB, I will need a packet.log & an evohome_cc file from a reboot.
No need to change any configuration just yet - simply reboot HA, wait 15 mins & PM me those two files - a sanity check before we progress.
When you PM- let me know the make/model of your OT appliance.
1 Like
I just noticed, I also have this issue where there are no states at all. Usually it tells me when something is heating, on auto or whatever.
I was testing this out…
- Set to restore_state: false
- Restart HA
- So far, around 3-4 days later, I haven’t lost any state on any of the heating zones.
Before, when it was restoring state between HA restarts, it did seem to lose state after 12-24 hours… might have been a fluke, mind you.
I figured I’d let it run for a week, without restarting HA since the original ‘restore_state: false’…
…then hash it out and restart HA…
I can confirm this works.
Alright so since I set restore_state: false my fake sensors have stopped working. 
Logger: homeassistant.components.automation.h_slaapkamer_temp
Source: custom_components/evohome_cc/climate.py:283
Integration: Automation (documentation, issues)
First occurred: 9:55:00 AM (200 occurrences)
Last logged: 6:10:00 PM
Update evohome temp: Error executing script. Unexpected error for call_service at pos 1: Can't set attribute (Faking is not enabled)
While executing automation automation.h_slaapkamer_temp
Traceback (most recent call last):
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_platform.py", line 666, in handle_service
await 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/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 283, in svc_set_zone_temp
self._device.sensor.temperature = temperature
File "/usr/local/lib/python3.8/site-packages/ramses_rf/devices.py", line 446, in temperature
raise AttributeError("Can't set attribute (Faking is not enabled)")
AttributeError: Can't set attribute (Faking is not enabled)
Show me a copy of the evohome_cc: section of your configuration.yaml file.