@So871 “value” and “percentage” seem related to modulation level but not the same. I’m not getting good data for either at the moment but if you are interested I’ve attached screenshots from when I was getting data. rel_modulation_level seems to give a good indication of how hard the system is working anyway.
@so871 - no, on that particular day the house was empty and HW off so not terribly representative but the most recent day I have good data for. Those occasional spikes would have been the system kicking in to maintain a minimum temp
If anyone is interested in creating a faked sensor which reports from 2 separate physical sensors I can write it up.
In short: I created 2 set point sensors for the room, 1 with the actual set point and one with an offset from that setpoint. I expanded the automation to now report when the temperature of one of the two physical sensors changes and created an andif , then, else routine.
IF the temperature of physical sensor 1 (room sensor @ 1.5m) drops below the setpoint AND the temperature of physical sensor 2 (on the floor) is below (setpoint -0.5) the value for physical sensor 2 is send to ramses. Else: it sends the reading of physical sensor 1 to ramses.
All looking good here too on 0.31.5. I don’t have opentherm but the other sensors that were previously going unavailable a lot all seem to be much more stable now.
OK, I’m now on the latest version. The send command is fixed and yields a checkmark instead of an error now, but responsiveness is still very iffy. I was finally was able to catch a “unresponsive” send command the ventilation unit, where the unit doesn’t respond as normal:
Since I was experiencing this issue, I’ve “upgraded” the automation and it’s now using a repeat of three button presses, each 1 second apart. This “block” of three presses is repeated until the fan speed is adjusted. So that’s why you’ll see multiples of 3. Below is the example of this “loop” for the high setting and similar is present for the auto setting after humidity is restored:
action:
- repeat:
sequence:
- service: ramses_cc.send_command
data:
entity_id: remote.29_123456
command: high
num_repeats: 3
delay_secs: 1
until:
- condition: state
entity_id: sensor.37_182456_fan_info
state: speed 3, high
Logs:
High setting succeeding in 1 try (repeats are there since I’ve set up now to repeat the button press 3 times)
2024-01-30T20:05:30.108721 000 I --- --:------ --:------ 29:057880 22F1 003 630404
2024-01-30T20:05:30.144845 041 I --- --:------ --:------ 37:182456 31DA 030 00C840033A33EF7FFF7FFF7FFF7FFFF800EF0357000000EFEF7FFF7FFF00
2024-01-30T20:05:31.106289 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BC320B332324631204932393A303537383830
2024-01-30T20:05:31.109290 000 I --- --:------ --:------ 29:057880 22F1 003 630404
2024-01-30T20:05:32.131516 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BC324B432324631204932393A303537383830
2024-01-30T20:05:32.134350 000 I --- --:------ --:------ 29:057880 22F1 003 630404
2024-01-30T20:05:37.320909 078 I --- 37:078891 --:------ 37:078891 31DA 029 00EF007FFF30EF7FFF7FFF7FFF7FFFF800EF183C000000EFEF7FFF7FFF
2024-01-30T20:05:38.281861 041 I 175 37:182456 --:------ 37:182456 31D9 017 0006C40020202020202020202020202000
Auto “failing” multiple times and finally responding in the 3rd block of 3 presses:
2024-01-30T20:48:31.015212 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA7E7732324631204932393A303537383830
2024-01-30T20:48:31.018239 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:32.015342 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA826032324631204932393A303537383830
2024-01-30T20:48:32.019461 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:33.044398 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA866032324631204932393A303537383830
2024-01-30T20:48:33.051449 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:33.077204 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA866232324631204932393A303537383830
2024-01-30T20:48:33.081285 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:34.042335 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA8A4B32324631204932393A303537383830
2024-01-30T20:48:34.046174 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:35.067398 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA8E4C32324631204932393A303537383830
2024-01-30T20:48:35.073360 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:35.113199 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA8E4D32324631204932393A303537383830
2024-01-30T20:48:35.117180 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:36.070278 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA923632324631204932393A303537383830
2024-01-30T20:48:36.073247 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:36.108305 042 I --- --:------ --:------ 37:182456 31DA 030 00C84002F933EF7FFF7FFF7FFF7FFFF800EF18C8000000EFEF7FFF7FFF00
2024-01-30T20:48:37.094391 000 I --- 18:203291 63:262142 --:------ 7FFF 023 0011018D5BEA963732324631204932393A303537383830
2024-01-30T20:48:37.098211 000 I --- --:------ --:------ 29:057880 22F1 003 630304
2024-01-30T20:48:41.482210 042 I 180 37:182456 --:------ 37:182456 31D9 017 0006A50020202020202020202020202000
2024-01-30T20:48:45.555418 042 I 181 37:182456 --:------ 37:182456 31D9 017 00064B0020202020202020202020202000
And here’s one for a barrage of manual sending the command for high, not responding, but after it’s on high it responds to auto instantly:
I’ve got an issue (probably not new) where the enforce_known_list: true parameter doesn’t filter out my next door neighbours Evohome (it’s partly my fault since I installed it for them as a favour! )
Despite enforcing the enforce_known_list the following entities are automatically added;
climate
heat_demand
window_open
active_fault
hw
hw_heat_demand
hw_relay_demand
I thought the entities were created from a enable_eavesdrop and when I didn’t enforce_known_list so I removed the ramses integration completely, deleted the entities and started again with the enforce_known_list from the beginning. After all of that, the entities were created again
My theory is the integration is not filtering the “controller” 01:xxxxxx correctly and assumes that I have a “multi” Evohome system but in fact it’s my neighbour. The log file complains that I don’t have a controller in my known list, but clearly I do.
Don’t know if it’s HAOS or Ramses related, but I got both updates at the same time and I haven’t been having a very fun time. Boot up took ages, when finally loading Ramses was shot, as was every other HACS component. Tried restoring the back up, which of course failed, tried reupdating HAOS core, went OK, but again took ages. After that Ramses failed to load, still said there was an update, but trying to update didn’t do anything. Tried removing ramses altogether and now I can’t even reinstall or re-download as the page doesn’t load… Weird stuff…
OK, Don’t know what happend, but all my troubles went away after using a laptop to manage my install. Was finally able to get ramses reinstalled and it appears to be working again. Was shitting bricks there for an hour and a half