Best practice is exactly one gateway

[sciorty]

Best practice is exactly one gateway

[sciorty]

Oh wait, i see something into the logs after a reboot:

2024-03-08T09:26:04.487423 # ramses_tx 0.31.7
2024-03-08T09:26:10.357661 000  I --- 18:136974 63:262142 --:------ 7FFF 015 0010018E1D2B627576302E33312E37
2024-03-08T09:26:12.166995 000  I --- 18:136974 63:262142 --:------ 7FFF 015 0010018E1D2B627576302E33312E37
2024-03-08T09:30:51.642368 072  I --- 32:142858 --:------ 32:142858 31DA 030 00EF007FFFEFEF06C27FFF08130654F000004150500000EFEF7FFF7FFF00
2024-03-08T09:35:51.891627 071  I 227 32:142858 --:------ 32:142858 31D9 017 002A020020202020202020202020202008
2024-03-08T09:40:52.151424 071  I --- 32:142858 --:------ 32:142858 31DA 030 00EF007FFFEFEF06BE7FFF0813064FF000004150500000EFEF7FFF7FFF00

And found this into the HA logs:

2024-03-08 09:26:04.484 WARNING (MainThread) [ramses_tx.schemas] Best practice is exactly one gateway (HGI) in the known_list: []
2024-03-08 09:26:06.293 WARNING (MainThread) [homeassistant.setup] Setup of ramses_cc is taking over 10 seconds.

2024-03-08 09:26:10.353 ERROR (MainThread) [custom_components.ramses_cc] There is a problem with the serial port: Transport did not initialise successfully
2024-03-08 09:26:10.355 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration 'ramses_cc': Integration failed to initialize.

[zxdavb]

There is no doubt that ramses_cc / ramses_rf is complex to configure...

Here, we have a message:

Best practice is exactly one gateway (HGI) in the known_list: []

In this case, 'exactly one' does not mean 0!

That is, there corresponding known_list, which is enforced, has no HGIs in it.:

  known_list:
    32:142858 : {class: FAN} 
    32:126818:
      class: REM
...

Try adding a HGI like so, and see how you go!

  known_list: 
    18:136974: class: HGI
    32:142858: class: FAN
    32:126818:
      class: REM
...

[zxdavb]

Setup of ramses_cc is taking over 10 seconds.

Note to self: test that new Transport architecture will call Protocol.connection_made() when it received the first puzzle packet, even if the HGI is not known, and the known list is enforced.

(there is now test_create_stack.py that does this)

[zxdavb]

There is a better error message for this:

2024-03-17 07:03:48.736 WARNING (MainThread) [ramses_tx.schemas]
 Best practice is exactly one gateway (HGI) in the known_list: but, len(['18:006402', '18:017804']) = 2

[sciorty]

Uhm i tried this configuration after the update:

ramses_cc:
  scan_interval: 3
  serial_port: /dev/ttyACM0
  packet_log: packets.log
  advanced_features:
    send_packet: true
  ramses_rf:
    enforce_known_list: true
  orphans_hvac: [32:142858, 32:126818]
  known_list:
    18:136974:
        class: HGI
    32:142858:
        class: FAN
    32:126818:
      class: REM
      faked: true
      commands:
        away:         ' I --- 32:126818 32:142858 --:------ 22F1 003 000007'
        low:          ' I --- 32:126818 32:142858 --:------ 22F1 003 000207'
        medium:       ' I --- 32:126818 32:142858 --:------ 22F1 003 000307'
        high:         ' I --- 32:126818 32:142858 --:------ 22F1 003 000707'
        bypass_open:  ' W --- 32:126818 32:142858 --:------ 22F7 003 00C8EF'
        bypass_close: ' W --- 32:126818 32:142858 --:------ 22F7 003 0000EF'
        bypass_auto:  ' W --- 32:126818 32:142858 --:------ 22F7 003 00FFEF'
        reset_filter: ' W --- 32:126818 32:142858 --:------ 10D0 002 00FF'

But on restart i have this:

[mazzy89]

ramses_cc:
  serial_port: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A50285BI-if00-port0
  restore_cache: true
  ramses_rf:
    enforce_known_list: true
    max_zones: 8
  "01:214354": {}
  known_list:
    "01:214354": { "alias": "--controller--" }
    "18:066327": { "alias": "HGI:evofw3" }
    "07:053519": { "alias": "hotwater_sensor" }
    "13:101655": { "alias": "hotwater_valve" }
    "13:000281": { "alias": "heating_valve" }
    "13:054730": { "alias": "zone_valve zone 00" }
    "04:208553": { "alias": "radiator_valve zone 01" }
    "04:208539": { "alias": "radiator_valve zone 02" }
    "04:208531": { "alias": "radiator_valve zone 03" }
    "04:000673": { "alias": "radiator_valve zone 04" }
    "34:036056": { "alias": "sensor zone 05" }
    "13:004596": { "alias": "actuator zone 05" }
    "04:000667": { "alias": "radiator_valve zone 06" }
    "04:002409": { "alias": "radiator_valve zone 07" }
  packet_log:
    file_name: packet.log
    rotate_backups: 7

This is my config and now I get this error:

2024-03-22 09:48:19.167 INFO (MainThread) [homeassistant.setup] Setting up ramses_cc
2024-03-22 09:48:36.970 WARNING (MainThread) [homeassistant.setup] Setup of ramses_cc is taking over 10 seconds.
2024-03-22 09:48:40.839 WARNING (MainThread) [custom_components.ramses_cc.broker] The config schema is not minimal (consider minimising it)
2024-03-22 09:48:40.845 INFO (MainThread) [custom_components.ramses_cc.schemas] Using a merged schema
2024-03-22 09:48:44.671 ERROR (MainThread) [custom_components.ramses_cc] There is a problem with the serial port: Transport did not initialise successfully
2024-03-22 09:48:44.673 INFO (MainThread) [homeassistant.setup] Setup of domain ramses_cc took 25.5 seconds
2024-03-22 09:48:44.673 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration 'ramses_cc': Integration failed to initialize.

[sciorty]

Uhm i tried this configuration after the update:

ramses_cc:
  scan_interval: 3
  serial_port: /dev/ttyACM0
  packet_log: packets.log
  advanced_features:
    send_packet: true
  ramses_rf:
    enforce_known_list: true
  orphans_hvac: [32:142858, 32:126818]
  known_list:
    18:136974:
        class: HGI
    32:142858:
        class: FAN
    32:126818:
      class: REM
      faked: true
      commands:
        away:         ' I --- 32:126818 32:142858 --:------ 22F1 003 000007'
        low:          ' I --- 32:126818 32:142858 --:------ 22F1 003 000207'
        medium:       ' I --- 32:126818 32:142858 --:------ 22F1 003 000307'
        high:         ' I --- 32:126818 32:142858 --:------ 22F1 003 000707'
        bypass_open:  ' W --- 32:126818 32:142858 --:------ 22F7 003 00C8EF'
        bypass_close: ' W --- 32:126818 32:142858 --:------ 22F7 003 0000EF'
        bypass_auto:  ' W --- 32:126818 32:142858 --:------ 22F7 003 00FFEF'
        reset_filter: ' W --- 32:126818 32:142858 --:------ 10D0 002 00FF'

But on restart i have this:

Ok so apparently after latest 0.31.16 release the integration restarted to work. Problem was that apparently some informations changed their name!! Some sensors that were name_temperature are now unavailable and changed to name_temp, and many others like attribute values of speed