Motion Automation, Illuminance timing issue, wrong value

So I have a motion trigger according to below, my issue is that sometimes after the trigger that turns off all the lights has run, it takes some time before the entity for the Illuminance (Philips Hue Motion Sensor) to change that the Automation is rejected when motion occurs because the Illuminance value has not been refreshed since the lights turned off.

I haven’t looked too deep into how often the entity takes to update, but it happens few times a week where I go to the kitchen after it apparently just turned the lights off (10 seconds?) because it won’t turn the lights on, on those occurrences.

Surely someone brighter then myself has had this happen and come up with a solution or someone has an idea to take care of this from happening?

id: '1668679075687'
alias: Motion - Kitchen
description: ''
trigger:
  - type: motion
    platform: device
    device_id: 09b5b6c6edabf56bb038b9f63990688f
    entity_id: binary_sensor.kitchen_motion_sensor_motion
    domain: binary_sensor
condition:
  - condition: state
    entity_id: input_boolean.isdark
    state: 'on'
    enabled: false
  - condition: state
    entity_id: light.kitchen_cupboard_lights
    state: 'off'
  - type: is_illuminance
    condition: device
    device_id: 09b5b6c6edabf56bb038b9f63990688f
    entity_id: sensor.kitchen_motion_sensor_illuminance
    domain: sensor
    below: 25
action:
  - service: light.turn_on
    data: {}
    target:
      entity_id:
        - light.group_kitchen_island_pendants
        - light.kitchen_cupboard_lights
  - wait_for_trigger:
      - platform: state
        entity_id:
          - binary_sensor.group_downstairs_motion
        to: 'off'
        for:
          hours: 0
          minutes: 20
          seconds: 0
  - service: light.turn_off
    data: {}
    target:
      area_id:
        - hallway
        - kitchen
mode: restart

image

@FakeThinkpad did you find a solution for this? I’m dealing with this as well.