RFLink states for switch and covers are not restored after restart

[Skuair]

The problem

The issue seems the same as #76482: my covers and switch from rflink are not restored after HA restart. I cannot say from which version it happened, but i would say more that one or 2 monthes (i update HA as soon as a new version is online). But i'm sure that before some time, the states were restored.

There are no logs after the restart that could explain this.

Here is the yaml for my covers and switch:

covers:

  - platform: rflink
    devices:
      newkaku_021c841a_1:
        name: Volet terrasse
        type: inverted
        aliases:
          - newkaku_021c841a_0
      newkaku_021c841a_2:
        name: Volet cuisine
        type: inverted
        aliases:
          - newkaku_021c841a_0

switches:

  - platform: rflink
    devices:
      newkaku_01872402_1:
        name: Caméras PoE
        aliases:
          - newkaku_01872402_0
      newkaku_cac142_2:
        name: Ventilateur baie réseau
      newkaku_cac142_4:
        name: Répéteur wifi

Example for one of the covers in the debug part, the last update of the state is when HA restarted (the cover was open before):

Tell me if you want more info.

What version of Home Assistant Core has the issue?

2023.5.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

RFLink

Link to integration documentation on our website

https://www.home-assistant.io/integrations/rflink/

Diagnostics information

Log of core after restart:

2023-06-01 17:24:17.574 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-06-01 17:24:17.577 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration pyscript which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-06-01 17:24:17.581 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration rte_ecowatt which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-06-01 17:24:17.585 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration myEnedis which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @javicalle, mind taking a look at this issue as it has been labeled with an integration (rflink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `rflink` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign rflink` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

rflink documentation rflink source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Skuair]

Still open for me.

[elik745i]

I have checked my old switches and they stopped working, not sure since when, used to work fine in the past maybe a year ago, any thoughts?

[Quato38]

Hi

I have the same problem

[daru23]

I have the same issue. Anything that the developers can suggest to try to help solve this problem.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Skuair]

Still an issue for me.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Skuair]

Still an issue.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Skuair]

Still happening.