I added it as a condition:
condition: state
entity_id: climate.huis
state: heat
for:
hours: 0
minutes: 1
seconds: 0
For information, the same error happens with the remote control faking of the ventilation. I noticed it yesterday. If the service “remote.send_command” is called too soon after a restart, it will create the same type of error message. Waiting for the corresponding remote entity generated by rameses_cc to become available is necessary before calling the service. In my case it takes a few minutes after restart (like 5 to 10 minutes). After that no problem anymore.
- id: 'Living Room Evohome Faked Sensor'
alias: Living Room Evohome Faked Sensor
mode: single
trigger:
- platform: state
entity_id: sensor.ble_temperature_living_room_evohome
condition:
condition: not
conditions:
- condition: state
entity_id: climate.living_room
state: "unavailable"
action:
- service: ramses_cc.put_zone_temp
data:
entity_id: climate.living_room
temperature: '{{ states("sensor.ble_temperature_living_room_evohome") | float }}'
- delay: 00:00:01
- service: homeassistant.update_entity
data: {}
target:
entity_id: sensor.03_055594_temperature
- service: homeassistant.update_entity
data: {}
target:
entity_id: climate.living_room
This seems to work for me - automation does not run/call the service, if the climate entity is unavailable.
I didn’t wait that long aproximity 12 hours
I see it this entity binary_sensor.18_xxxxxx_status whit nanocul
This isn’t right - I will add it to my to-do list.
Please PM me a packet log - preferably the full day when you upgraded from 18.x. I’ll have a look.
BTW, do you have a R8810A or an R8820A?
Can everyone running 0.20.22e please confirm they see, or no longer see, these errors:
22/08/00_1: (maybe fixed by 0.20.22a) I am not sure why this is happening - the code was written to handle this issue:
File "/config/custom_components/ramses_cc/climate_heat.py", line 138, in hvac_mode
if self._device.tcs.system_mode[CONF_SYSTEM_MODE] == SystemMode.AWAY:
TypeError: 'NoneType' object is not subscriptable
22/08/00_2: This is under investigation - appears only on startup? The system appears to behave normally otherwise.
File "/usr/local/lib/python3.10/site-packages/ramses_rf/gateway.py", line 545, in check_filter_lists
and dev_id != self.pkt_protocol._hgi80[SZ_DEVICE_ID]
AttributeError: 'NoneType' object has no attribute '_hgi80'
Some sensors can take >12 hours (battery state is only reported once per 24h), but not the OpenTherm Bridge - all its important sensors are 5 minutes (and every 5 minutes after that):
_STATUS_MSG_IDS: tuple = (
"00", # ..0: "Master/Slave status flags",
"01", # ..1: "CH water temperature Setpoint (°C)",
"11", # .17: "Relative Modulation Level (%)",
"12", # .18: "Water pressure in CH circuit (bar)",
"13", # .19: "Water flow rate in DHW circuit. (L/min)",
"19", # .25: "Boiler flow water temperature (°C)",
"1A", # .26: "DHW temperature (°C)",
"1B", # .27: "Outside temperature (°C)",
"1C", # .28: "Return water temperature (°C)",
# These are error/state codes...
"05", # ..5: "Fault flags & OEM codes",
"73", # 115: "OEM diagnostic code",
)
You didn’t answer my question: R8810A, or R8820A?
Please PM me a packet log as described above and I’ll have a look for you - the answer will be in there.
I am not at home yet Ian back on Friday
I have a r8810a module for as far as I know I don’t no what the r8820a is
Here is a part of my logbook
2022-09-12T00:00:04.056657 074 I — --:------ --:------ 10:130890 1FD4 003 000992
2022-09-12T00:00:04.836857 000 RQ — 18:207134 01:168864 --:------ 2349 002 0100
2022-09-12T00:00:04.857784 061 RP — 01:168864 18:207134 --:------ 2349 007 01047E02FFFFFF
2022-09-12T00:00:05.665435 000 RQ — 18:207134 01:168864 --:------ 2349 002 0300
2022-09-12T00:00:05.681646 061 RP — 01:168864 18:207134 --:------ 2349 007 0304B000FFFFFF
2022-09-12T00:00:34.269461 075 I — --:------ --:------ 10:130890 1FD4 003 000993
2022-09-12T00:00:44.206381 061 RQ — 01:168864 10:130890 --:------ 3EF0 001 00
2022-09-12T00:00:44.238462 076 RP — 10:130890 01:168864 --:------ 3EF0 006 000010000000
2022-09-12T00:01:04.477715 076 I — --:------ --:------ 10:130890 1FD4 003 000994
2022-09-12T00:01:14.457709 000 RQ — 18:207134 01:168864 --:------ 0006 001 00
2022-09-12T00:01:14.472341 062 RP — 01:168864 18:207134 --:------ 0006 004 00050000
2022-09-12T00:01:17.522960 000 RQ — 18:207134 01:168864 --:------ 313F 001 00
2022-09-12T00:01:17.542266 061 RP — 01:168864 18:207134 --:------ 313F 009 00FC9E03000C0907E6
2022-09-12T00:01:17.585573 000 RQ — 18:207134 01:168864 --:------ 2349 002 0200
2022-09-12T00:01:17.601367 062 RP — 01:168864 18:207134 --:------ 2349 007 0204B000FFFFFF
2022-09-12T00:01:17.786518 000 RQ — 18:207134 01:168864 --:------ 2349 002 0600
2022-09-12T00:01:17.803242 061 RP — 01:168864 18:207134 --:------ 2349 007 0603E800FFFFFF
2022-09-12T00:01:34.688244 075 I — --:------ --:------ 10:130890 1FD4 003 000995
2022-09-12T00:01:42.523057 062 I — 01:168864 --:------ 01:168864 1F09 003 FF096A
2022-09-12T00:01:42.549706 061 I — 01:168864 --:------ 01:168864 2309 021 0005DC01047E0204B00304B004047E0504B00603E8
2022-09-12T00:01:42.568522 061 I — 01:168864 --:------ 01:168864 30C9 021 0009820108790208A60308CD04087C05087C0608EC
2022-09-12T00:01:44.415184 061 RQ — 01:168864 10:130890 --:------ 3EF0 001 00
2022-09-12T00:01:44.442917 075 RP — 10:130890 01:168864 --:------ 3EF0 006 000010000000
2022-09-12T00:01:55.763375 000 RQ — 18:207134 01:168864 --:------ 2349 002 0000
2022-09-12T00:01:55.780035 062 RP — 01:168864 18:207134 --:------ 2349 007 0005DC02FFFFFF
2022-09-12T00:02:04.895811 075 I — --:------ --:------ 10:130890 1FD4 003 000996
2022-09-12T00:02:17.921355 000 RQ — 18:207134 01:168864 --:------ 2349 002 0400
2022-09-12T00:02:17.938021 062 RP — 01:168864 18:207134 --:------ 2349 007 04047E02FFFFFF
2022-09-12T00:02:35.107765 076 I — --:------ --:------ 10:130890 1FD4 003 000997
2022-09-12T00:02:44.624882 062 RQ — 01:168864 10:130890 --:------ 3EF0 001 00
2022-09-12T00:02:44.655587 075 RP — 10:130890 01:168864 --:------ 3EF0 006 000010000000
2022-09-12T00:02:56.667759 062 I — 01:168864 --:------ 01:168864 0008 002 FC00
2022-09-12T00:02:56.701037 074 I — 10:130890 --:------ 01:168864 3150 002 FC00
2022-09-12T00:03:05.316957 074 I — --:------ --:------ 10:130890 1FD4 003 000998
2022-09-12T00:03:20.591012 000 RQ — 18:207134 01:168864 --:------ 0418 003 000000
2022-09-12T00:03:20.618845 061 RP — 01:168864 18:207134 --:------ 0418 022 004000B0040004000000929605507FFFFF700010C29A
2022-09-12T00:03:35.528225 075 I — --:------ --:------ 10:130890 1FD4 003 000999
2022-09-12T00:03:41.583839 000 RQ — 18:207134 01:168864 --:------ 2349 002 0500
2022-09-12T00:03:41.599552 062 RP — 01:168864 18:207134 --:------ 2349 007 0504B000FFFFFF
2022-09-12T00:03:44.835033 061 RQ — 01:168864 10:130890 --:------ 3EF0 001 00
2022-09-12T00:03:44.862765 075 RP — 10:130890 01:168864 --:------ 3EF0 006 000010000000
2022-09-12T00:03:45.717704 000 RQ — 18:207134 01:168864 --:------ 2E04 001 FF
2022-09-12T00:03:45.735439 061 RP — 01:168864 18:207134 --:------ 2E04 008 02FFFFFFFFFFFF00
2022-09-12T00:03:48.318573 043 I — 04:049884 --:------ 01:168864 12B0 003 040000
2022-09-12T00:03:51.445220 042 I — 04:049884 --:------ 01:168864 12B0 003 040000
2022-09-12T00:03:52.537839 043 I — 04:049884 --:------ 04:049884 30C9 003 000877
2022-09-12T00:04:23.641149 061 RQ — 01:168864 10:130890 --:------ 22D9 001 00
2022-09-12T00:04:23.667731 076 RP — 10:130890 01:168864 --:------ 22D9 003 0003E8
2022-09-12T00:04:23.844056 061 RQ — 01:168864 10:130890 --:------ 3220 005 0000050000
2022-09-12T00:04:24.043906 076 RP — 10:130890 01:168864 --:------ 3220 005 00F0050000
2022-09-12T00:04:24.244542 061 RQ — 01:168864 10:130890 --:------ 3220 005 0000110000
2022-09-12T00:04:24.584860 075 RP — 10:130890 01:168864 --:------ 3220 005 00C0110000
2022-09-12T00:04:24.644442 062 RQ — 01:168864 10:130890 --:------ 3220 005 0000120000
2022-09-12T00:04:25.123607 074 RP — 10:130890 01:168864 --:------ 3220 005 0040120100
2022-09-12T00:04:25.244132 061 RQ — 01:168864 10:130890 --:------ 3220 005 0080130000
2022-09-12T00:04:25.661821 076 RP — 10:130890 01:168864 --:------ 3220 005 0070130000
2022-09-12T00:04:25.844880 062 RQ — 01:168864 10:130890 --:------ 3220 005 0080190000
2022-09-12T00:04:26.201268 075 RP — 10:130890 01:168864 --:------ 3220 005 00C0193499
2022-09-12T00:04:26.244798 062 RQ — 01:168864 10:130890 --:------ 3220 005 00801A0000
2022-09-12T00:04:26.844523 061 RQ — 01:168864 10:130890 --:------ 3220 005 00801C0000
2022-09-12T00:04:27.444680 062 RQ — 01:168864 10:130890 --:------ 3220 005 0080730000
2022-09-12T00:04:27.819665 076 RP — 10:130890 01:168864 --:------ 3220 005 00C07300CB
2022-09-12T00:04:35.951090 074 I — --:------ --:------ 10:130890 1FD4 003 00099B
2022-09-12T00:04:45.045080 061 RQ — 01:168864 10:130890 --:------ 3EF0 001 00
2022-09-12T00:04:45.071354 074 RP — 10:130890 01:168864 --:------ 3EF0 006 000010000000
2022-09-12T00:04:59.286946 061 I — 01:168864 --:------ 01:168864 3B00 002 FCC8
2022-09-12T00:05:04.906099 000 RQ — 18:207134 01:168864 --:------ 2349 002 0100
2022-09-12T00:05:04.923454 061 RP — 01:168864 18:207134 --:------ 2349 007 01047E02FFFFFF
2022-09-12T00:05:05.732556 000 RQ — 18:207134 01:168864 --:------ 2349 002 0300
2022-09-12T00:05:05.747858 061 RP — 01:168864 18:207134 --:------ 2349 007 0304B000FFFFFF
2022-09-12T00:05:10.219341 076 I — 04:049746 --:------ 01:168864 2309 003 067EFF
2022-09-12T00:05:10.240646 061 I — 01:168864 --:------ 01:168864 2349 013 0601F404FFFFFF00160C0907E6
2022-09-12T00:05:10.253100 062 I — 01:168864 --:------ 01:168864 2309 003 0601F4
2022-09-12T00:05:36.377620 075 I — --:------ --:------ 10:130890 1FD4 003 00099D
2022-09-12T00:05:43.518928 061 I — 01:168864 --:------ 01:168864 1F09 003 FF096A
2022-09-12T00:05:43.545113 062 I — 01:168864 --:------ 01:168864 2309 021 0005DC01047E0204B00304B004047E0504B00601F4
2022-09-12T00:05:43.564889 061 I — 01:168864 --:------ 01:168864 30C9 021 0009820108790208A60308CD04087705087C0608EC
2022-09-12T00:05:45.255208 061 RQ — 01:168864 10:130890 --:------ 3EF0 001 00
2022-09-12T00:05:45.282450 076 RP — 10:130890 01:168864 --:------ 3EF0 006 000010000000
2022-09-12T00:06:06.578675 076 I — --:------ --:------ 10:130890 1FD4 003 00099E
2022-09-12T00:06:09.479298 076 I — 04:049814 --:------ 04:049814 30C9 003 000892
2022-09-12T00:06:14.553351 000 RQ — 18:207134 01:168864 --:------ 0006 001 00
2022-09-12T00:06:14.567771 062 RP — 01:168864 18:207134 --:------ 0006 004 00050000
2022-09-12T00:06:17.663354 000 RQ — 18:207134 01:168864 --:------ 2349 002 0200
2022-09-12T00:06:17.678333 062 RP — 01:168864 18:207134 --:------ 2349 007 0204B000FFFFFF
2022-09-12T00:06:36.790233 075 I — --:------ --:------ 10:130890 1FD4 003 00099F
2022-09-12T00:06:45.464468 061 RQ — 01:168864 10:130890 --:------ 3EF0 001 00
2022-09-12T00:06:45.494170 075 RP — 10:130890 01:168864 --:------ 3EF0 006 000010000000
2022-09-12T00:06:55.857574 000 RQ — 18:207134 01:168864 --:------ 2349 002 0000
2022-09-12T00:06:55.873852 061 RP — 01:168864 18:207134 --:------ 2349 007 0005DC02FFFFFF
2022-09-12T00:07:07.000447 074 I — --:------ --:------ 10:130890 1FD4 003 0009A0
Is anyone else seeing Stored Hot Water Relay Demand (sensor.13_215029_relay_demand) and Temperature Sensors (i.e sensor.07_014869_temperature) going Unavailable?
These were rock solid with 0.18.x - I skipped 0.19.x - perhaps a regression? I remember we had this pre 0.18.x at some point as well.
Might try rolling back.
No-one else has reported this issue - which isn’t to say it’s not a real issue - the code changes from 0.18 to the latest 0.20 are rather extensive…
This is one of the reasons why I am encouraging people to move to 0.20.22 before Winter.
I have only just now put DHW back into my test bed, so I will keep an eye on it.
In the meantime, it would be helpful for you to track this over (say) 72h on a 3-day history graph (from the “History” tile, select “Show more”…
I am looking for patterns (say it goes unavailable for 15min every 6hr) - it is just a matter of tweaking timeout values, I suspect.
I shall resist the ‘Winters Coming’ retort…Damn it!
Will do, thanks.
The Water Heat entity shows a constant temperature graph, but the sensor.xxxx is a bit hit and miss - graph has broken lines for a few hours - it’s been a while since I looked at this, but I seem to recall perhaps one was intercepted from the box attached to the tank and the other was pulled from the main Controller?
The reason for this is that the controller is only telling you (telling ramses_rf) what it last heard from the DHW sensor. If the DHW sensor stops talking, eventually the controller will do what ramses_rf will do - have the value as None rather than the last reported value.
ramses_rf will forgive 2.1x lost packets (i.e. it will tolerate 1 lost update, but not 2) before it resorts to None (ramses_cc will say Unavailable) rather than the last reported value.
The only difference between teh controller and ramses_rf is how long they wait for the DHW sensor giving up.
I think it has settled down, apologies for the ‘noise’ - I reset the cache and restarted HA and it (flakey Stored hot water sensors) hasn’t reoccurred so far.
Any idea why I might not see the binary_sensor.18_xxxxxx_status entity being generated at all? Or what I could do to perhaps try and regenerate it? Hashing out ramses_cc, restarting, unhashing, restarting again?
It doesn’t appear in the core.entity_registry file, I checked that the correct 18:xxxxxx ID is in the conf from a packet.log. Will add some logging this afternoon and restart HA and see if it throws anything up.
hi, can someone help me with the basics of installation? I am following 1. Installation · zxdavb/ramses_cc Wiki · GitHub and I must be missing a step.
I have home assistant OS 2022.8.7 running on x86. all working fine. Have a number of HACS custom repo components already installed and working for some time, so I know how to do that part.
I added HACS custom repo GitHub - zxdavb/ramses_cc: HA custom component for ramses_rf. that works, now it’s listed in HACS custom repos. second step of install wiki doesn’t work for me - there is no repository matching “ramses” or “honeywell” available to install, so I don’t think I’ve actually installed it, only added the repo. I’ve restarted several times. so if I go into HA->Settings->Integrations, there is no new tile as I would expect to see if I’d installed it as well.
the other issue is how to find the serial device:
I bought one of these: https://indalo-tech.onlineweb.shop/ as per recommendations here. Its plugged into my box.
the command
ls /dev/serial/by-id
doesn’t exist in HA OS?
looking for inspiration for dashboard for the evohome, this is mine:
I would like to see what you have configured!
1 Like
My design takes inspiration from the Evohome controller. The colour temperature changes based on the set point temperature. The icons change depending on the climate mode and whether there is a fault condition. Mouse tooltips provide additional information. The mode panel dynamically changes to expose climate modes and hot water boost. I created this design a couple of years ago for the cloud integration and yet to migrate it to ramses_cc. I could add boiler/heat demand which would be nice.
5 Likes