RFlink entities unavailable after restart, until turned on manually in real life

I was scrolling through the forum and saw a different post with the same issue

I’ve tried the same steps but can’t find my issue. Everytime I restart all the devices become unavailable e.g.

configuration.yaml:


# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
# Example configuration.yaml entry
rflink:
  port: /dev/serial/by-id/usb-Arduino__www.arduino.cc__Arduino_Mega_2560_11652601009321232660-if00
  wait_for_ack: false
  ignore_devices:
    - light.afzuiging
    - kaku_00004b_5
# this port is shown in the image above. your detail might be different
logger:
  default: error
  logs:
    rflink: debug
    homeassistant.components.rflink: debug

light:
# add the following to the existing light section
  - platform: rflink
    automatic_add: true
    devices:
     light.afzuiging:
      name: afzuiging washok
     light.kaku_00004b_5:
      name: test_device

sensor:
# add the following to the existing sensor section
  - platform: rflink
    automatic_add: true

Logfile:

2023-10-01 12:25:22.408 INFO (MainThread) [homeassistant.components.rflink] Initiating Rflink connection
2023-10-01 12:25:22.411 DEBUG (MainThread) [rflink.protocol] ignoring: ['afzuiging', 'kaku_00004b_5']
2023-10-01 12:25:22.414 INFO (MainThread) [homeassistant.components.rflink] Connected to Rflink
2023-10-01 12:25:22.421 DEBUG (MainThread) [rflink.protocol] connected
2023-10-01 12:25:25.543 DEBUG (MainThread) [rflink.protocol] received data: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R48;
2023-10-01 12:25:25.543 DEBUG (MainThread) [rflink.protocol] got packet: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R48;
2023-10-01 12:25:25.544 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'unknown', 'hardware': 'Nodo RadioFrequencyLink', 'firmware': 'RFLink Gateway', 'version': '1.1', 'revision': '48'}
2023-10-01 12:25:25.545 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'rflink', 'hardware': 'Nodo RadioFrequencyLink', 'firmware': 'RFLink Gateway', 'version': '1.1', 'revision': '48'}
2023-10-01 12:25:25.545 DEBUG (MainThread) [homeassistant.components.rflink] event of type unknown: {'id': 'rflink', 'hardware': 'Nodo RadioFrequencyLink', 'firmware': 'RFLink Gateway', 'version': '1.1', 'revision': '48'}
2023-10-01 12:25:25.545 DEBUG (MainThread) [homeassistant.components.rflink] unhandled event of type: unknown
2023-10-01 12:25:26.902 ERROR (Thread-5) [pychromecast.socket_client] [Tv in woonkamer(e582d6aa-f9ec-c237-3d74-30ac23d60f80.local.):8009] Failed to connect to service ServiceInfo(type='mdns', data='Chromecast-HD-e582d6aaf9ecc2373d7430ac23d60f80._googlecast._tcp.local.'), retrying in 5.0s
2023-10-01 12:29:46.710 DEBUG (MainThread) [rflink.protocol] received data: 20;
2023-10-01 12:29:46.712 DEBUG (MainThread) [rflink.protocol] received data: 01;NewKaku;ID=0
2023-10-01 12:29:46.714 DEBUG (MainThread) [rflink.protocol] received data: 106090c;S
2023-10-01 12:29:46.716 DEBUG (MainThread) [rflink.protocol] received data: WITCH=1;C
2023-10-01 12:29:46.717 DEBUG (MainThread) [rflink.protocol] received data: MD=OFF
2023-10-01 12:29:46.718 DEBUG (MainThread) [rflink.protocol] received data: ;
2023-10-01 12:29:46.719 DEBUG (MainThread) [rflink.protocol] got packet: 20;01;NewKaku;ID=0106090c;SWITCH=1;CMD=OFF;
2023-10-01 12:29:46.719 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'newkaku', 'id': '0106090c', 'switch': '1', 'command': 'off'}
2023-10-01 12:29:46.719 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'newkaku_0106090c_1', 'command': 'off'}
2023-10-01 12:29:46.720 DEBUG (MainThread) [homeassistant.components.rflink] event of type command: {'id': 'newkaku_0106090c_1', 'command': 'off'}
2023-10-01 12:29:46.720 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: []
2023-10-01 12:29:46.720 DEBUG (MainThread) [homeassistant.components.rflink] device_id not known, adding new device

Your kaku_00004b_5 is in ignore_devices

This was an example, this problem is for all RFLink devices.

Rflink will never create an entity afzuiging, so this can be removed already. I added my list of ignored devices. In light:, don’t add light., just the raw entity.

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
# Example configuration.yaml entry
rflink:
  port: /dev/serial/by-id/usb-Arduino__www.arduino.cc__Arduino_Mega_2560_11652601009321232660-if00
  wait_for_ack: false
  ignore_devices:
    - ev1527_012af3_02 
    - ev1527_01285a_02
    - blyss_th_*
    - doorbell_fe2a_1
    - legrandcad*
    - renkforcee*
    - fineoffset*
    - chuango_de8380_02
    - selectplus_07ffff_02
    - selectplus_00c677_02
    - ev1527_022f69*
    - eurodomest_2dd096*
    - eurodomest_0dd096*
    - eurodomest_2ed50c*
    - ev1527_00bd30_*
# this port is shown in the image above. your detail might be different
logger:
  default: error
  logs:
    rflink: debug
    homeassistant.components.rflink: debug

light:
# add the following to the existing light section
  - platform: rflink
    automatic_add: true
    devices:
      kaku_00004b_5:
        name: test_device

sensor:
# add the following to the existing sensor section
  - platform: rflink
    automatic_add: true

To persist devices between restarts, they must be declared in the RFLink configuration. Entities added by the automatic_add mechanism will not be available until detected by RFLink.

It seems to me that your RFLink configuration is incorrect.
Devices definitions should not have the platform prefix:

Be carefull with the configuration indentation. It matters.