VSCode Error on Entity Filter Card

Configuration Frontend
1

Having an issue with the following bit of code and the VSCode Hass.io addon:

## BATTERIES ##
      - type: entity-filter
        card:
          type: entities
          title: Low Battery Levels
          show_header_toggle: false
        entities:
          - sensor.amy_bedroom_switch_battery_level
          - sensor.andy_bedroom_switch_battery_level
          - sensor.back_door_sensor_battery_level
          - sensor.bathroom_thermometer_battery_level
          - sensor.bathroom_window_sensor_battery_level
          - sensor.bedroom_motion_sensor_battery_level
          - sensor.bedroom_thermometer_battery_level
          - sensor.dining_room_switch_battery_level
          - sensor.front_door_sensor_battery_level
          - sensor.hall_motion_sensor_battery_level
          - sensor.jessica_door_sensor_battery_level
          - sensor.jessica_thermometer_battery_level
          - sensor.kitchen_door_sensor_battery_level
          - sensor.kitchen_motion_sensor_battery_level
          - sensor.landing_motion_sensor_battery_level
          - sensor.living_room_button_battery_level_2
          - sensor.living_room_motion_sensor_battery_level
          - sensor.porch_motion_sensor_battery_level
        state_filter:
          - operator: "<"
            value: 60

It is working fine in Lovelace however in the VSCode Hass.io addon i’m getting this error.

image
image798×542 15.6 KB

Does anyone know how to fix, or alternativly make VSCode ignore those particular lines.

Thanks, Andy

2

I know it’s not what is in the docs but this works for me:

    state_filter:
      - operator: <
        value: -70
3

Still shows up as an error in VSCode. It works in Lovelace but the error message is annoying in VSCode.

4

I meant it gives no error in VSCode (as well as working in Lovelace). Strange that you are getting an error.

Raise an issue here:

5

I also have some yaml errors in the VCode editor. I did raise an issue there a few weeks ago and the dev said it’s upstream in yamlint and to raise the issue there… but there is no way to make an issue in that repo. So I just ignore the error now.

image