The integration is not tolerant of temporary issues with the packet source.

[brucemiranda]

The integration is not tolerant of temporary issues with the packet source.

[zxdavb]

User reports:

A simple Reload of the integration seems to kick things back into life.

I note Reload is only available with the config_flow version of the integration, version 0.41.x and later.

In summary: if there is an error in the transport layer of the integration, the integration will freeze, and the only solution is to restart HA, or Reload the integration (if that option exists).

[zxdavb]

This is an automation to reload the integration if a problem is detected (thanks @brucemiranda).

NOTE: this work-around only apples for the config flow (>0.41.x) release of RAMSES RF.

alias: Reload Ramses CC
description: Reload Ramses CC when HGI80 shows a Problem
trigger:
  - platform: state
    entity_id:
      - binary_sensor.18_002563_status
    to: "on"
condition: []
action:
  - service: homeassistant.reload_config_entry
    data:
      entry_id: 14f6287491ba233d7310fd7a82b32fec
mode: single

[brucemiranda]

You can find the entity_id for ramses_cc by looking in the file config/.storage/core.config_entries and looking with the

domain:
  ramses_cc:

section.

[Swiftnesses]

This is helpful, I also started to see this a few months back (was faultless before that).

[Swiftnesses]

I don't have an entry in config/.storage/core.config_entries, any ideas @zxdavb or @brucemiranda?

[Swiftnesses]

Uploaded to the latest beta version and run the config flow, which provided me with the core config and allowed me to restart.

Thanks, both.

[zxdavb]

I don't have an entry in config/.storage/core.config_entries, any ideas @zxdavb or @brucemiranda?

The advice only applies for the config flow release of RAMSES RF.

[zxdavb]

related to #182