Input_boolean cannot be turned off by scene

Hi folks, I’m struggling with something that I think is probably a bug, but maybe could be something I’m doing wrong.

So I have two scenes that I create dynamically with automations. One is to correspond to the “on” state of my driveway light switch, one to correspond to the “off” state.

Because sometimes the “off” state will actually be a dimly lit state, I need some way for the triggering automation to know which state to toggle to, other than looking at the state of any bulb in the scene. So I have created an input boolean to track that.

Problem is, my scene turns on the input boolean as expected, but won’t turn it off. Is this a bug?

Below are the service snippets that create the scenes in my automation.

      - service: scene.create
        data:
          scene_id: disable_driveway_lights_input
          entities:
            input_boolean.driveway_proxy: "off"
            light.driveway_spot_1: "off"
            light.driveway_spot_2: "off"
            light.driveway_spot_3: "off"
            light.front_gate: "off"
            light.entrance_light: "off"
            light.front_door_spot: "off"

And …

    - service: scene.create
      data:
        scene_id: driveway_lights_input
        entities:
          input_boolean.driveway_proxy: "on"
          light.driveway_spot_1:
            state: "on"
            brightness: 255
            color_temp: '{{ states.input_number.calculated_warmth.state | int }}'
          light.driveway_spot_2:
            state: "on"
            brightness: 255
            color_temp: '{{ states.input_number.calculated_warmth.state | int }}'
          light.driveway_spot_3:
            state: "on"
            brightness: 255
            color_temp: '{{ states.input_number.calculated_warmth.state | int }}'
          light.front_gate:
            state: "on"
            brightness: 255
            color_temp: '{{ states.input_number.calculated_warmth.state | int }}'

I ran into this issue as well. If you use false instead of “off”, it works. Seems like a bug.

Seems the bug is fixed at least as of version 2022.9.7 - but thanks for the tip.