Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm

[holymountain92 (Jeroen)]

Been able to solve it by completely deleting the integration, installing 0.30.4 and cleaning the antenna. Everything works again.

[phdelodder (Philippe Delodder)]

Hi, upgraded to 0.30.4 and running it for a few days

My feedback:

• name attribute becomes null on the climate-entity
• friendly_name attribute can’t find it on the climate-entity
• Battery sensor, eg binary_sensor.04_231770_battery_low, is nearly always unavailable. This is for all battery sensors.

After restarting HA the friendly_name attribute is back.

Currently running HA 2023.12.1

Hope this helps.

[zxdavb (David Bonnes)]

@Mike_H

Can anyone help me understand what it’s telling me?

This is a known issue, it can be ignored for now.

[zxdavb (David Bonnes)]

@Rinco

I also would add the Filter remaining time; sensor.xx_xxxxxx_filter_remaining
(To do so, you’ll need to ad some code manually to the sensor.ply and add an autoimation for keeping the value as it is not integrated yet)

This sensor should be working.

[zxdavb (David Bonnes)]

@phdelodder

• name attribute becomes null on the climate-entity
• friendly_name attribute can’t find it on the climate-entity
• Battery sensor, eg binary_sensor.04_231770_battery_low, is nearly always unavailable. This is for all battery sensors.

After restarting HA the friendly_name attribute is back.

Please - is anyone suffering for this issue.

[Mike_H (Mike Henderson)]

@zxdavb

This is a known issue, it can be ignored for now.

Cheers for that.

Mike

[Rinco (Rinco van der Beek)]

That’s correct, that works like a charme.
I mend implementing this to your WTW image.

[behold81]

Anyone? Would like to work out i there is anything I can do to solve this or help solve this.

Either I am blind (highly possible) or there is still not a confirmed process to bind a 4 way remote to my Nuaire? I have tried reading extensivly the 3700+ comments to try and find the answer.
I can see the RF code for my using and my remote will send commands. but I assume binding process still is not working?

[zxdavb (David Bonnes)]

@behold81

Anyone? Would like to work out i there is anything I can do to solve this or help solve this.

It is doable, even with the current code, but the process is quite intricate (specifically, the 10E0).

I have spent a lot of time making this happen, and am on the home run, but we are not there yet, and I will have very little time to look at it until mid -Jan.

Remaining challenges include:

• the existing bind command does not send a follow-up 10E0 packet after the bind completes
• there are 3 distinct ‘schemes’ (Nuaire, Orcon, Itho) for binding remotes.
• the new QoS is still buggy

[behold81]

Thanks, Appreciate that and that your time is likely filled with home life like many of us.

let me know if you need any testing to checks. I have the Nuaire HC-Heat system.

Although right now I have a near empty Packet Log. not sure whats going on. can’t get any RF info in the log. (was working) So trying to sort that right now.

UPDATE- Seemingly wiping most of the config and starting it again seems to have fixed it. oddly. I have an evohome so there is alot of noise in the log.

[behold81]

So I seem to get this after I restart my HA. It seems to do an initial discovery then dies. What am I doing wrong here?

2023-12-11 10:25:48.700 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_05 (RAD): Failed to send discovery cmd: 12B0|RP|01:198631|05: 
2023-12-11 10:25:49.095 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_06 (ELE): Failed to send discovery cmd: 12B0|RP|01:198631|06: 
2023-12-11 10:25:49.773 WARNING (MainThread) [ramses_rf.entity_base] 13:100513 (BDR): True: Failed to send discovery cmd: 3EF1|RP|13:100513: 
2023-12-11 10:25:59.600 WARNING (MainThread) [ramses_rf.entity_base] 30:081993 (FAN): Failed to send discovery cmd: 22F8|RP|30:081993: 
2023-12-11 10:26:48.656 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_HW (DHW): Failed to send discovery cmd: 1260|RP|01:198631|00: 
2023-12-11 10:26:51.657 WARNING (MainThread) [ramses_rf.entity_base] 13:244215 (BDR): False: Failed to send discovery cmd: 0008|RP|13:244215: 
2023-12-11 10:26:51.702 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_00 (RAD): Failed to send discovery cmd: 2349|RP|01:198631|00: 
2023-12-11 10:26:51.703 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_01 (RAD): Failed to send discovery cmd: 2349|RP|01:198631|01: 
2023-12-11 10:26:51.703 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_02 (RAD): Failed to send discovery cmd: 2349|RP|01:198631|02: 
2023-12-11 10:26:51.703 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_03 (RAD): Failed to send discovery cmd: 2349|RP|01:198631|03: 
2023-12-11 10:26:51.703 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_04 (RAD): Failed to send discovery cmd: 2349|RP|01:198631|04: 
2023-12-11 10:26:51.703 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_05 (RAD): Failed to send discovery cmd: 2349|RP|01:198631|05: 
2023-12-11 10:26:52.098 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_06 (ELE): Failed to send discovery cmd: 2349|RP|01:198631|06: 
2023-12-11 10:26:52.776 WARNING (MainThread) [ramses_rf.entity_base] 13:100513 (BDR): True: Failed to send discovery cmd: 0008|RP|13:100513: 
2023-12-11 10:26:59.601 WARNING (MainThread) [ramses_rf.entity_base] 30:081993 (FAN): Failed to send discovery cmd: 313E|RP|30:081993: 
2023-12-11 10:27:51.658 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_HW (DHW): Failed to send discovery cmd: 1F41|RP|01:198631|00: 
2023-12-11 10:27:51.659 WARNING (MainThread) [ramses_rf.entity_base] 13:244215 (BDR): False: Failed to send discovery cmd: 3EF1|RP|13:244215: 
2023-12-11 10:27:51.704 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_00 (RAD): Failed to send discovery cmd: 30C9|RP|01:198631|00: 
2023-12-11 10:27:51.704 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_01 (RAD): Failed to send discovery cmd: 30C9|RP|01:198631|01: 
2023-12-11 10:27:51.705 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_02 (RAD): Failed to send discovery cmd: 30C9|RP|01:198631|02: 
2023-12-11 10:27:51.705 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_03 (RAD): Failed to send discovery cmd: 30C9|RP|01:198631|03: 
2023-12-11 10:27:51.705 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_04 (RAD): Failed to send discovery cmd: 30C9|RP|01:198631|04: 
2023-12-11 10:27:51.705 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_05 (RAD): Failed to send discovery cmd: 30C9|RP|01:198631|05: 
2023-12-11 10:27:52.100 WARNING (MainThread) [ramses_rf.entity_base] 01:198631_06 (ELE): Failed to send discovery cmd: 30C9|RP|01:198631|06: 
2023-12-11 10:27:52.778 WARNING (MainThread) [ramses_rf.entity_base] 13:100513 (BDR): True: Failed to send discovery cmd: 3EF1|RP|13:100513: 
2023-12-11 10:27:59.603 WARNING (MainThread) [ramses_rf.entity_base] 30:081993 (FAN): Failed to send discovery cmd: 3222|RP|30:081993:

2023-12-11T10:19:42.452860 # ramses_tx 0.30.4
2023-12-11T10:19:42.609572 ...  I --- 22:015026 --:------ 22:015026 0008 002 0000 # 0008| I|22:015026
2023-12-11T10:19:42.613351 ... RP --- 01:198631 18:071184 --:------ 000C 006 000E0037B9F7 # 000C|RP|01:198631|000E (000E)
2023-12-11T10:19:42.616244 ... RP --- 01:198631 18:071184 --:------ 000C 006 010E7FFFFFFF # 000C|RP|01:198631|010E (010E)
2023-12-11T10:19:42.637135 ... RP --- 01:198631 18:071184 --:------ 000C 006 000D001C96AD # 000C|RP|01:198631|000D (000D)
2023-12-11T10:19:42.641903 ... RP --- 13:244215 18:071184 --:------ 0008 002 0000 # 0008|RP|13:244215
2023-12-11T10:19:42.645048 ... RP --- 01:198631 18:071184 --:------ 313F 009 00FC032B090B0C07E7 # 313F|RP|01:198631
2023-12-11T10:19:42.648779 ... RP --- 01:198631 18:071184 --:------ 10A0 006 0019640003E8 # 10A0|RP|01:198631|00 (00)
2023-12-11T10:19:42.657025 ... RP --- 13:244215 18:071184 --:------ 1100 008 000C1000007FFF01 # 1100|RP|13:244215
2023-12-11T10:19:42.658866 ... RP --- 01:198631 18:071184 --:------ 0005 004 00083F00 # 0005|RP|01:198631|0008 (0008)
2023-12-11T10:19:42.668136 ... RP --- 01:198631 18:071184 --:------ 1F41 006 000000FFFFFF # 1F41|RP|01:198631|00 (00)
2023-12-11T10:19:42.675504 ... RP --- 13:244215 18:071184 --:------ 3EF1 007 0000EF00EF00FF # 3EF1|RP|13:244215
2023-12-11T10:19:42.679872 ... RP --- 01:198631 18:071184 --:------ 0005 004 00090000 # 0005|RP|01:198631|0009 (0009)
2023-12-11T10:19:42.687192 ... RP --- 01:198631 18:071184 --:------ 30C9 003 0006FF # 30C9|RP|01:198631|00 (00)
2023-12-11T10:19:42.693311 ... RP --- 01:198631 18:071184 --:------ 30C9 003 01057F # 30C9|RP|01:198631|01 (01)
2023-12-11T10:19:42.695886 ... RP --- 01:198631 18:071184 --:------ 30C9 003 020643 # 30C9|RP|01:198631|02 (02)
2023-12-11T10:19:42.697464 ... RP --- 01:198631 18:071184 --:------ 30C9 003 0305C7 # 30C9|RP|01:198631|03 (03)
2023-12-11T10:19:42.710569 ... RP --- 01:198631 18:071184 --:------ 30C9 003 040629 # 30C9|RP|01:198631|04 (04)
2023-12-11T10:19:42.924991 ... RP --- 01:198631 18:071184 --:------ 30C9 003 05067E # 30C9|RP|01:198631|05 (05)
2023-12-11T10:19:42.929929 ... RP --- 01:198631 18:071184 --:------ 1260 003 000904 # 1260|RP|01:198631|00 (00)
2023-12-11T10:19:42.999068 ... RP --- 01:198631 18:071184 --:------ 0005 004 000A0000 # 0005|RP|01:198631|000A (000A)
2023-12-11T10:19:43.006175 ... RP --- 01:198631 18:071184 --:------ 0005 004 000B0000 # 0005|RP|01:198631|000B (000B)
2023-12-11T10:19:43.011274 ... RP --- 01:198631 18:071184 --:------ 0005 004 00114000 # 0005|RP|01:198631|0011 (0011)
2023-12-11T10:19:43.013165 ... RP --- 01:198631 18:071184 --:------ 0005 004 00047F00 # 0005|RP|01:198631|0004 (0004)
2023-12-11T10:19:43.016616 ... RP --- 01:198631 18:071184 --:------ 30C9 003 060718 # 30C9|RP|01:198631|06 (06)
2023-12-11T10:19:43.081447 ... RP --- 01:198631 18:071184 --:------ 000C 006 000800104B8A # 000C|RP|01:198631|0008 (0008)
2023-12-11T10:19:43.083465 ... RP --- 01:198631 18:071184 --:------ 000C 006 00047FFFFFFF # 000C|RP|01:198631|0004 (0004)
2023-12-11T10:19:43.106273 ... RP --- 01:198631 18:071184 --:------ 000C 006 010800104B80 # 000C|RP|01:198631|0108 (0108)
2023-12-11T10:19:43.111386 ... RP --- 01:198631 18:071184 --:------ 000C 006 010400104B80 # 000C|RP|01:198631|0104 (0104)
2023-12-11T10:19:43.117202 ... RP --- 01:198631 18:071184 --:------ 000C 006 020800104F12 # 000C|RP|01:198631|0208 (0208)
2023-12-11T10:19:43.207235 ... RP --- 01:198631 18:071184 --:------ 000C 006 030800104F14 # 000C|RP|01:198631|0308 (0308)
2023-12-11T10:19:43.212240 ... RP --- 01:198631 18:071184 --:------ 000C 006 020400104F12 # 000C|RP|01:198631|0204 (0204)
2023-12-11T10:19:43.219314 ... RP --- 01:198631 18:071184 --:------ 000C 006 040800104F16 # 000C|RP|01:198631|0408 (0408)
2023-12-11T10:19:43.222512 ... RP --- 01:198631 18:071184 --:------ 000C 006 030400104F14 # 000C|RP|01:198631|0304 (0304)
2023-12-11T10:19:43.650957 ... RP --- 01:198631 18:071184 --:------ 000C 006 050800104F10 # 000C|RP|01:198631|0508 (0508)
2023-12-11T10:19:43.658478 ... RP --- 01:198631 18:071184 --:------ 000C 006 040400104F16 # 000C|RP|01:198631|0404 (0404)
2023-12-11T10:19:43.703799 ... RP --- 01:198631 18:071184 --:------ 000C 006 050400104F10 # 000C|RP|01:198631|0504 (0504)
2023-12-11T10:19:43.713128 ... RP --- 01:198631 18:071184 --:------ 000C 006 000F003588A1 # 000C|RP|01:198631|000F (000F)
2023-12-11T10:19:43.720744 ... RP --- 01:198631 18:071184 --:------ 000C 006 06117FFFFFFF # 000C|RP|01:198631|0611 (0611)
2023-12-11T10:19:43.724191 ... RP --- 01:198631 18:071184 --:------ 1100 008 FC0C1000007FFF01 # 1100|RP|01:198631|FC (FC)
2023-12-11T10:19:43.753827 ... RP --- 13:100513 18:071184 --:------ 0008 002 00C8 # 0008|RP|13:100513
2023-12-11T10:19:43.761735 ... RP --- 01:198631 18:071184 --:------ 000C 006 060400583AB2 # 000C|RP|01:198631|0604 (0604)
2023-12-11T10:19:43.767326 ... RP --- 01:198631 18:071184 --:------ 0418 022 004000B0061C04000000B61785B5FFFFFF70003588A1 # 0418|RP|01:198631|00 (00)
2023-12-11T10:19:43.961164 ... RP --- 13:100513 18:071184 --:------ 1100 008 000C1000007FFF01 # 1100|RP|13:100513
2023-12-11T10:19:43.972187 ... RP --- 01:198631 18:071184 --:------ 2E04 008 00FFFFFFFFFFFF00 # 2E04|RP|01:198631
2023-12-11T10:19:43.987504 ... RP --- 01:198631 18:071184 --:------ 0006 004 00050019 # 0006|RP|01:198631
2023-12-11T10:19:44.000504 ... RP --- 13:100513 18:071184 --:------ 3EF1 007 0000E400E4C8FF # 3EF1|RP|13:100513
2023-12-11T10:19:44.012784 ... RP --- 01:198631 18:071184 --:------ 000A 006 031001F40DAC # 000A|RP|01:198631|03 (03)
2023-12-11T10:19:44.015608 ... RP --- 01:198631 18:071184 --:------ 2349 007 0103E800FFFFFF # 2349|RP|01:198631|01 (01)
2023-12-11T10:19:44.018715 ... RP --- 01:198631 18:071184 --:------ 2349 007 04057800FFFFFF # 2349|RP|01:198631|04 (04)
2023-12-11T10:19:44.026115 ... RP --- 01:198631 18:071184 --:------ 000A 006 021001F40DAC # 000A|RP|01:198631|02 (02)
2023-12-11T10:19:44.028050 ... RP --- 01:198631 18:071184 --:------ 0004 022 00004C6976696E6720726F6F6D000000000000000000 # 0004|RP|01:198631|00 (00)
2023-12-11T10:19:44.030837 ... RP --- 01:198631 18:071184 --:------ 000A 006 051001F40DAC # 000A|RP|01:198631|05 (05)
2023-12-11T10:19:44.033762 ... RP --- 01:198631 18:071184 --:------ 0004 022 020042617468726F6F6D000000000000000000000000 # 0004|RP|01:198631|02 (02)
2023-12-11T10:19:44.071913 ... RP --- 01:198631 18:071184 --:------ 2349 007 0005DC00FFFFFF # 2349|RP|01:198631|00 (00)
2023-12-11T10:19:44.075696 ... RP --- 01:198631 18:071184 --:------ 0004 022 05005370617265726F6F6D0000000000000000000000 # 0004|RP|01:198631|05 (05)
2023-12-11T10:19:44.079138 ... RP --- 01:198631 18:071184 --:------ 2349 007 0207D000FFFFFF # 2349|RP|01:198631|02 (02)
2023-12-11T10:19:44.081577 ... RP --- 01:198631 18:071184 --:------ 2349 007 05051400FFFFFF # 2349|RP|01:198631|05 (05)
2023-12-11T10:19:44.085339 ... RP --- 01:198631 18:071184 --:------ 0004 022 0600457874656E73696F6E0000000000000000000000 # 0004|RP|01:198631|06 (06)
2023-12-11T10:19:44.101066 ... RP --- 01:198631 18:071184 --:------ 0004 022 03005574696C69747920526F6F6D0000000000000000 # 0004|RP|01:198631|03 (03)
2023-12-11T10:19:44.104184 ... RP --- 01:198631 18:071184 --:------ 2349 007 03032000FFFFFF # 2349|RP|01:198631|03 (03)
2023-12-11T10:19:44.309289 ... RP --- 01:198631 18:071184 --:------ 000A 006 011001F40DAC # 000A|RP|01:198631|01 (01)
2023-12-11T10:19:44.316766 ... RP --- 01:198631 18:071184 --:------ 000A 006 041001F40DAC # 000A|RP|01:198631|04 (04)
2023-12-11T10:19:44.330583 ... RP --- 01:198631 18:071184 --:------ 0004 022 0100456E7472616E6365000000000000000000000000 # 0004|RP|01:198631|01 (01)
2023-12-11T10:19:44.354373 ... RP --- 01:198631 18:071184 --:------ 0004 022 0400426564726F6F6D00000000000000000000000000 # 0004|RP|01:198631|04 (04)
2023-12-11T10:19:44.362445 ... RP --- 01:198631 18:071184 --:------ 000A 006 001001F40DAC # 000A|RP|01:198631|00 (00)
2023-12-11T10:19:44.370218 ... RP --- 01:198631 18:071184 --:------ 000A 006 061001F40DAC # 000A|RP|01:198631|06 (06)
2023-12-11T10:19:44.377727 ... RP --- 01:198631 18:071184 --:------ 2349 007 06032000FFFFFF # 2349|RP|01:198631|06 (06)

# RF Configuration
ramses_cc:
  serial_port: /dev/serial/by-id/usb-SparkFun_evofw3_atmega32u4-if00 #SSM-D2 Rev B
  packet_log:
    file_name: ramsespacket.log
    rotate_backups: 7
  #restore_cache:
  #  restore_schema: true
  #  restore_state: false
  orphans_hvac: [30:081993, 32:222222, 63:262142]
  known_list:
    18:071184: { class: HGI } # SSM-D2
    30:081993: { class: FAN } # Nuaire PIV}
    32:222222:
      class: REM
      faked: true
      commands:
        normal: " I --- 32:222222 30:081993 --:------ 22F1 003 00020A"
        boost: " I --- 32:222222 30:081993 --:------ 22F1 003 00030A"
        heater_auto: " I --- 32:222222 30:081993 --:------ 22F1 003 000A0A"
        heater_off: " I --- 32:222222 30:081993 --:------ 22F1 003 00090A"
      # bind: " I --- 32:222222 30:081993 --:------ 1FC9 001 00"
      # Virtual DRI-ECO-4S
  ramses_rf:
    enforce_known_list: false # if not true, still enforces the block_list
    # disable_discovery: false
    # disable_sending: false # do not transmit any packets, ever
    # enable_eavesdrop: false # can be used to create an initial system schema

[phdelodder (Philippe Delodder)]

If you want I can supply log files! I went back to 0.22.40.

[dspalu32]

This sounds similar to what I saw: Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm - #3787 by dspalu32

Since reporting that, I noticed that it’s actually cyclical: the names re-appear and disappear repeatedly over the course of hours.

I’ve dropped back to 0.22.40 for now.

[RemcoMe (Remcomeeder)]

I am a bit lost on how to get ramses_rf and ramses_cc running on my system.
I have a SSM-D2 dongle which seems to recognized by my HA installation.
In the HA Log I get the following:

2023-12-11 17:33:41.301 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 000F0035B0DC < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:43.895 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 024 00080010ED2700080010ED2B00080010ED3900080012512F < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:44.185 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 01080010ED3F < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.171 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 0104010D4CAC < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.326 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 02080010ED3D < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.384 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 02040088B314 < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.403 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 03080010ED2D < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.447 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 03040010ED2D < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.464 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 040800125131 < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.475 ERROR (MainThread) [ramses_rf.processor] RP — 01:248420 18:005908 --:------ 000C 006 0404010D4D45 < AttributeError(‘NoneType’ object has no attribute ‘_hgi80’)
2023-12-11 17:33:45.710 WARNING (MainThread) [ramses_rf.protocol.transport] I — 18:005908 63:262142 --:------ 7FFF 016 0010018C59BA38C676302E32312E3430 < Active gateway set to: 18:005908

I am not really sure what to do next. I have the following in my configuration.yaml

ramses_cc:
serial_port: /dev/ttyACM0
restore_cache:
restore_state: true
restore_schema: false

packet_log:
file_name: /config/ramses_cc.log
rotate_backups: 28

ramses_rf:
enforce_known_list: true

known_list:
01:248420: # Evohome controller
18:005908: # SSM-D2

How do I find out the ID’s for the HR92’s and the BDR91T which controls the main valve to supply heat to the house?

[RemcoMe (Remcomeeder)]

Ah after yet another reboot of HA suddenly there were multiple entities showing up.
Now it’s the question on identifying all the different devices and how they show up.

In our living room the Evohome is the main temperature sensor and there are four HR92’s which control the radiators.
On the second floor there are 2 rooms (bathroom and bedroom) which have a HR92 which controls the radiator but the temperature is measured by a HCF82 temperature sensor.
There is also one room which has a HR92 and as the temperature sensor I have used a Round Wireless thermostat (T87RF2025). I wanted to get a HCF82 for that room as well but the Round Wireless is cheaper for some reason.

I have the following device types in the entities:

01: this is the main Evohome thermostat.
04: these are the HR92’s.
18: this is the evofw3 dongle if I am correct
13: this is the BDR91T relay box
then there are types 03 and 34 of which I don’t exactly know what they are.

Can someone tell me what the device types 03 and 34 are?
And what is the easiest way to determine which ID belongs to which device? For a couple of HR92’s I found the corresponding ID by checking which one had a specific heat demand but sometimes more than one has the same demand.

[zxdavb (David Bonnes)]

There was an issue where the state cache may not have been restored correctly in 0.30.x. For example:

@phdelodder

My feedback:

• name attribute becomes null on the climate-entity

… and:

@dspalu32

One other comment, not specific to 0.30.x: would it be possible to cache/restore min_temp and max_temp for zones?

… and also fixes:

@Mike_H

AttributeError: 'NoneType' object has no attribute 'send_frame'

If you’ve had problems, please try 0.30.5, and report back.

[Spaco]

Getting this after a few hours while on 0.30.4:

Logger: ramses_tx.message
Source: /usr/local/lib/python3.11/site-packages/ramses_tx/message.py:274
First occurred: 20:00:25 (6 occurrences)
Last logged: 20:02:01

RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFE1FEB500FF < AssertionError(byte 1: FFE1)
RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFDEFEB200FF < AssertionError(byte 1: FFDE)
RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFC0FE9400FF < AssertionError(byte 1: FFC0)
RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFA2FE7600FF < AssertionError(byte 1: FFA2)
RP --- 13:259021 18:071950 --:------ 3EF1 007 00FF84FE5800FF < AssertionError(byte 1: FF84)
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/ramses_tx/message.py", line 259, in _validate
    result = parse_payload(self)
             ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ramses_tx/parsers.py", line 2854, in parse_payload
    result = _PAYLOAD_PARSERS.get(msg.code, parser_unknown)(msg._pkt.payload, msg)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/ramses_tx/parsers.py", line 2528, in parser_3ef1
    assert int(payload[2:6], 16) <= 7200, f"byte 1: {payload[2:6]}"
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: byte 1: FFE4

This is right after:

2023-12-11T03:14:48.745490 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00

which it send every minute or so. most of the RP’s parse fine, except the above. it doesn’t seem like a corrupted packet, here’s a series of ‘correct’ one with a group of ‘bad’ ones in the middle:

2023-12-11T19:58:49.037160 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T19:58:49.052180 066 RP --- 13:259021 18:071950 --:------ 3EF1 007 00012C012CC8FF
2023-12-11T19:59:22.036991 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T19:59:22.051988 067 RP --- 13:259021 18:071950 --:------ 3EF1 007 00010B010B00FF
2023-12-11T19:59:23.105190 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T19:59:23.120092 067 RP --- 13:259021 18:071950 --:------ 3EF1 007 000022FEF600FF
2023-12-11T19:59:25.037029 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T19:59:25.052002 068 RP --- 13:259021 18:071950 --:------ 3EF1 007 000020FEF400FF
2023-12-11T20:00:25.082608 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:00:25.097451 068 RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFE4FEB800FF
2023-12-11T20:00:28.085584 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:00:28.100551 068 RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFE1FEB500FF
2023-12-11T20:00:31.086468 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:00:31.101474 068 RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFDEFEB200FF
2023-12-11T20:01:01.087245 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:01:01.102224 067 RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFC0FE9400FF
2023-12-11T20:01:31.089122 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:01:31.104146 067 RP --- 13:259021 18:071950 --:------ 3EF1 007 00FFA2FE7600FF
2023-12-11T20:02:01.089763 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:02:01.103768 068 RP --- 13:259021 18:071950 --:------ 3EF1 007 00FF84FE5800FF
2023-12-11T20:03:49.038986 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:03:49.053949 066 RP --- 13:259021 18:071950 --:------ 3EF1 007 00012C012CC8FF
2023-12-11T20:08:49.042776 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:08:49.057789 065 RP --- 13:259021 18:071950 --:------ 3EF1 007 00012C012CC8FF
2023-12-11T20:13:49.042715 000 RQ --- 18:071950 13:259021 --:------ 3EF1 001 00
2023-12-11T20:13:49.057656 065 RP --- 13:259021 18:071950 --:------ 3EF1 007 00012C012CC8FF

the 13: device is a BDR91

[zxdavb (David Bonnes)]

@Spaco

AssertionError: byte 1: FFE4

This is completely new - could I have a 24h packet log please.

Actually, nothing to do with 0.30.x - would still be an issue with 0.2x.x…

I know what it is, but I don’t know why… is count down timer to the number of seconds to next cycle (cycle_countdown), but these are negative numbers!

[Spaco]

its weird, this only actually happened this evening, nothing else in the packet log greps back to 5/12. maybe these are corrupt packets.

[zxdavb (David Bonnes)]

No, they are not corrupt - they are telling you something:

2023-12-11T19:58:49.052180 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 1.0, 'actuator_countdown': 300, 'cycle_countdown': 300, '_unknown_0': 'FF'}
2023-12-11T19:59:22.051988 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 267, 'cycle_countdown': 267, '_unknown_0': 'FF'}
2023-12-11T19:59:23.120092 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65270, 'cycle_countdown': 34, '_unknown_0': 'FF'}
2023-12-11T19:59:25.052002 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65268, 'cycle_countdown': 32, '_unknown_0': 'FF'}
2023-12-11T20:00:25.097451 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65208, 'cycle_countdown': -28, '_unknown_0': 'FF'}
2023-12-11T20:00:28.100551 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65205, 'cycle_countdown': -31, '_unknown_0': 'FF'}
2023-12-11T20:00:31.101474 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65202, 'cycle_countdown': -34, '_unknown_0': 'FF'}
2023-12-11T20:01:01.102224 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65172, 'cycle_countdown': -64, '_unknown_0': 'FF'}
2023-12-11T20:01:31.104146 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65142, 'cycle_countdown': -94, '_unknown_0': 'FF'}
2023-12-11T20:02:01.103768 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 0.0, 'actuator_countdown': 65112, 'cycle_countdown': -124, '_unknown_0': 'FF'}
2023-12-11T20:03:49.053949 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 1.0, 'actuator_countdown': 300, 'cycle_countdown': 300, '_unknown_0': 'FF'}
2023-12-11T20:08:49.057789 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 1.0, 'actuator_countdown': 300, 'cycle_countdown': 300, '_unknown_0': 'FF'}
2023-12-11T20:13:49.057656 ||  13:259021 |  18:071950 | RP | actuator_cycle   |      || {'modulation_level': 1.0, 'actuator_countdown': 300, 'cycle_countdown': 300, '_unknown_0': 'FF'}

… The cycle_countdown will match the elapsed seconds on the packet timestamps.