Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Best practice is exactly one gateway #174

Closed
sciorty opened this issue Mar 8, 2024 · 7 comments
Closed

Best practice is exactly one gateway #174

sciorty opened this issue Mar 8, 2024 · 7 comments
Assignees
@zxdavb
Labels
ramses_rf The issue is likely due to an underlying bug in the ramses_rf library.

Comments

@sciorty
Copy link

sciorty commented Mar 8, 2024 •
edited by zxdavb
Loading

Hello,

I just updated the version of the integration from 0.21.40 -> 0.31.7.
This was my previous configuration that worked fine for moths with an SSM-D2. Now it simply stopped, logs are no longer present on the packets.log, there simply isn't anything since the update. Already tried to reboot the host, reset the dongle etc. Waited for an entire night but no entuty has been updated/available.

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:
    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'

Works again after going back to previous version
@sciorty
Copy link
Author

sciorty commented Mar 8, 2024

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
Copy link
Owner

zxdavb commented Mar 14, 2024

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
Copy link
Owner

zxdavb commented Mar 14, 2024 •
edited
Loading

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 zxdavb self-assigned this Mar 14, 2024
@zxdavb
Copy link
Owner

zxdavb commented Mar 17, 2024

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

@zxdavb zxdavb changed the title SSM-D2 stopped working with 0.31.7 ? Best practice is exactly one gateway Mar 17, 2024
@zxdavb zxdavb added the ramses_rf The issue is likely due to an underlying bug in the ramses_rf library. label Mar 17, 2024
@zxdavb zxdavb closed this as completed Mar 17, 2024
@sciorty
Copy link
Author

sciorty commented Mar 19, 2024

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:
image
image

@mazzy89
Copy link

mazzy89 commented Mar 22, 2024 

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
Copy link
Author

sciorty commented Apr 8, 2024

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: image image

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zxdavb zxdavb

Labels
ramses_rf The issue is likely due to an underlying bug in the ramses_rf library.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mazzy89 @sciorty @zxdavb