I believe I have a workaround for this in v0.15.5.
Please, can someone with an R8810A/R8820A (an OTB, OpenTherm bridge) please send me a packet log, using this version.
I have just updated to v0.15.5 and tested. I still have the error unfortunatelly:
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:87
First occurred: 11:23:10 AM (4 occurrences)
Last logged: 11:23:12 AM
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/ramses_rf/helpers.py", line 17, in execute_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/devices.py", line 289, in _discover
self._make_cmd(_10E0, retries=3)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/devices.py", line 189, in _make_cmd
super()._make_cmd(code, self.id, payload, **kwargs)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/entities.py", line 89, in _make_cmd
self._send_cmd(self._gwy.create_cmd(verb, dest_id, code, payload, **kwargs))
File "/usr/local/lib/python3.9/site-packages/ramses_rf/entities.py", line 93, in _send_cmd
raise RuntimeError("Sending is disabled")
RuntimeError: Sending is disabled
I send you in parrallel via PM the corresponding log file
Same for me. Iāll send you my packet log
@bishop I am not surprised yours is still failingā¦ Because of teh excessive re-transmits, thing are timing out all over the placeā¦
@guyank Letās have a look at your log.
Iām having problems getting my log. VS keeps crashing HASS
After a few restarts of my Pi4 owing to the problems with VS, the climate entities have returned.
Does that mean, so that others reading this thread arenāt mislead into thinking the library is unreliable, you want to do this:
Yes. All working now
To be absolutely clear, the error still exists, but doesnāt seem to be preventing anything working:
2021-11-05 11:41:35 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/ramses_rf/helpers.py", line 17, in execute_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/devices.py", line 289, in _discover
self._make_cmd(_10E0, retries=3)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/devices.py", line 189, in _make_cmd
super()._make_cmd(code, self.id, payload, **kwargs)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/entities.py", line 89, in _make_cmd
self._send_cmd(self._gwy.create_cmd(verb, dest_id, code, payload, **kwargs))
File "/usr/local/lib/python3.9/site-packages/ramses_rf/entities.py", line 93, in _send_cmd
raise RuntimeError("Sending is disabled")
RuntimeError: Sending is disabled
OK, I am chagrined!
This is what I see:
2021-11-05T10:41:01.521415 ... I --- 04:026369 --:------ 04:026369 10E0 038 000002FF0412FFFFFFFF100907DF0D0307DE48523932205261646961746F72204374726C2E00 # 10E0| I|04:026369
2021-11-05T11:01:46.108662 ... I --- 04:026371 --:------ 01:065252 1060 003 00C801 # 1060| I|04:026371|00 (00)
...
2021-11-05T11:01:51.265266 ... RP --- 01:065252 18:131597 --:------ 0100 005 00656EFFFF # 0100|RP|01:065252
2021-11-05T11:01:51.274141 000 I --- 18:131597 63:262142 --:------ 7FFF 015 0010017CEFC3124376302E31352E32
This tells me it is taking >5 seconds to get from when it starts to restore state, until it starts to monitor for RF trafficā¦
My dodgy work-around had budgeted 1 second for this! Thatās why itās an issue (the same thing is happening to @bishop, but for a separate reason).
What hardware are you using?
Anyway, I canāt put a 5 second pause inā¦
After the upgrade I am missing the evohome_cc.put_zone_temp service call. Has this been renamed (cannot find something similar in the services tab under developer tools)?
Its an SSM-D
Iāve upgraded and have these errors and warnings.
Logger: homeassistant
Source: /usr/src/homeassistant/homeassistant/runner.py:98
First occurred: 12:53:05 (824 occurrences)
Last logged: 16:45:12
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/ramses_rf/helpers.py", line 17, in execute_func
return func(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/devices.py", line 289, in _discover
self._make_cmd(_10E0, retries=3)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/devices.py", line 189, in _make_cmd
super()._make_cmd(code, self.id, payload, **kwargs)
File "/usr/local/lib/python3.9/site-packages/ramses_rf/entities.py", line 89, in _make_cmd
self._send_cmd(self._gwy.create_cmd(verb, dest_id, code, payload, **kwargs))
File "/usr/local/lib/python3.9/site-packages/ramses_rf/entities.py", line 93, in _send_cmd
raise RuntimeError("Sending is disabled")
RuntimeError: Sending is disabled
Logger: ramses_rf.protocol.message
Source: /usr/local/lib/python3.9/site-packages/ramses_rf/protocol/message.py:310
First occurred: 12:53:11 (66 occurrences)
Last logged: 16:38:06
RP --- 10:051349 01:169176 --:------ 3220 005 00707A0000 # has expired (285%)
RP --- 10:051349 01:169176 --:------ 3220 005 00F07B0000 # has expired (285%)
RP --- 10:051349 01:169176 --:------ 3220 005 00407F0202 # has expired (285%)
I --- 30:079129 --:------ 30:079129 1F09 003 0007FD # has expired (167%)
I --- 04:198487 --:------ 01:169176 2309 003 040802 # has expired (121%)
Logger: ramses_rf.protocol.message
Source: /usr/local/lib/python3.9/site-packages/ramses_rf/protocol/message.py:371
First occurred: 15:21:01 (3 occurrences)
Last logged: 15:21:01
RQ --- 32:168240 30:079129 --:------ 31DA 001 6C << Corrupt payload: Payload doesn't match '^(00|01|21)$': 6C (will be ignored)
Hello,
I am running the latest version (v0.15.5) and I have the service call evohome_cc.put_zone_temp in my list of services in the developer tools page and I confirm it works because I am using it in an automation to fake 3 zone sensors. So I guess the problem is not linked to the update to the latest version (but no clue what it could be due to, sorry).
Just new hereā¦ have been observing for a long time (Impressed in the mean time coming from Domoticz but also overwhelmed). Just installed your update, will log for a while and try to het you a packetlog. Have got a Evo system here, the OT bridge R8810A ā¦
In the mean time, in general, impressed with the whole system!
Hi,
Welcome here 
Iāve migrated a while back from Domoticz too so if you have questions I might be able to help. In general I am very happy to have migrated and my setup is much more stable now (I used to have to reboot Domoticz regularly).
@zxdavb Hmmā¦ Just updated to the latest release. Saw that my system was using the full CPU (I run it here on a Xeon Synology as VM) ā¦ Also it reported problems with my HGI80 (I ve got one)ā¦ Just inspected and now reporting that the USB cannot be found. Strange thing is that my Syno seems to be seeing it, rebooting the VM (I wait a little before restarting the VM) did not seem to fix the USB. I learnt that the only way to fix this is a stop and go of my syno. The HGI will only report back duty when I do this. So hoped to provide a packetlog but this will have to waitā¦
I would suggest people who are having trouble go back to 0.14.x for now.
I have opened a can of worms.
HGI80s have a duty cycle - if it is exceeded (likely with multiple back-to-back stars of HA) - it will lock up.
Hmmā¦ I think my HGI has diedā¦ Multiple power downs. Long time disconnectingā¦ Somehow my Syno seems to see which device it is, can pass trough it to my VM, but Domoticz does not define the USB prort to it nor does HA pass trough it. And before just running perfect. Think I need another (Nanocul) solutionā¦
I think I am losing my mindā¦ and it is back! Since I plan only to read/record statusses I can now (phew) see again what the Evo is doingā¦ 
Anyone on version 0.15.x please upgrade to 0.16.1.
Anyone who got the above error on 0.15.x, please let me know how you get on with 0.16.1.