RFLink Sensors went from Clear to Unknown after updating HA to Version 2022.2.0

1

I had an issue with HA to Version 2022.2.0
After updating my Yale Alarm 433.92 RFLink sensors all went to unknown.
I went around the house and noticed they went back to clear after detecting a single motion, just wondering if anyone else had that issue?

2

Yes I have the same with my MQTT motion sensors they all start as unknown. Once triggered they then change to clear untill I restart the revert to unknown again.

3

One thought I had was that this would impact anyone where the automation goes from Off (Clear) to On (Detected)
I can’t see anything configurable under the Binary Sensor Group - Home Assistant (home-assistant.io)
Integration.

binary_sensor:
yw_sensor_117562_03:
name: Kitchen PIR
device_class: motion
off_delay: 5

I have raised an issue with HA under this bug ref
(2) RFLink Sensors status went to “Unknown” after updating HA to Version 2022.2.0 from previous version was working fine just before · Issue #65559 · home-assistant/core (github.com)

4

I tried this as a workaround, however all that happens is that the state of the sensors doesn’t change even when a motion is detected. Not sure where to go with this now I don’t really want sensors showing as “unknown” its kind of disconcerting…

  1. Added this line to configuration.yaml

python_script:

  1. Use Rod Paynes Python Script dated Dec 18 @rodpayne
  1. This is my automation which runs when HA starts up.
    Sensors come up as “unknown” for about 30 seconds then the script fires and all are OFF (Clear) ready for a motion detection action ON (Detect) but now the state just doesn’t chance from OFF!!

This calls the python script.
It isn’t “code efficient” but I’m not a programmer. Maybe someone can enhance the code?

alias: Fix unknown status on sensors connected to RFLink v2
description: ''
trigger:
  - platform: homeassistant
    event: start
condition: []
action:
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.back_door
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.entrance_door
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.office_pir
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.office_window
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.lounge_window
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.kitchen_pir
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.kitchen_window
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.front_bedroom_pir
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.back_bedroom_pir
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.panic_button_downstairs
      state: 'off'
      allow_create: true
  - service: python_script.set_state
    data_template:
      entity_id: binary_sensor.panic_button_upstairs
      state: 'off'
      allow_create: true

Kind of lost as to where to go now… Thought this might work but just makes the state get stuck