Configuration - sensors.yaml errors

Hi friendly people

This is a snippet of my configuration.yaml.

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
sensor: !include sensors.yaml
input_boolean: !include input_booleans.yaml

Below is a screen shot of my sensors.yaml opened in Studio Code Server that shows errors which I do not recall having ever seen before. Can someone point me to what I need to change on my sensors.yaml file? I have copied some of the code below.

- platform: systemmonitor
  resources:
    - type: disk_use_percent
    - type: memory_use_percent
    - type: load_1m
    - type: load_5m
    - type: load_15m
    - type: processor_use
    - type: processor_temperature

- platform: rest
  name: pws_forecast
  json_attributes:
    - calendarDayTemperatureMax
    - calendarDayTemperatureMin
    - dayOfWeek
    - expirationTimeUtc
    - moonPhase
    - moonPhaseCode
    - moonPhaseDay
    - moonriseTimeLocal
    - moonriseTimeUtc
    - moonsetTimeLocal
    - moonsetTimeUtc
    - narrative
    - qpf
    - qpfSnow
    - sunriseTimeLocal
    - sunriseTimeUtc
    - sunsetTimeLocal
    - sunsetTimeUtc
    - temperatureMax
    - temperatureMin
    - validTimeLocal
    - validTimeUtc
    - daypart
  value_template: '{{ value_json["validTimeLocal"][0] }}'
  resource: !secret wu_forecast_url
  scan_interval: 03:00:00

- platform: rest
  name: pws_report
  json_attributes:
    - observations
  value_template: '{{ value_json["observations"][0]["obsTimeLocal"].title() }}'
  resource: !secret wu_report_url
  scan_interval: 00:05:00

- platform: rest
  name: pws_history
  json_attributes:
    - summaries
  value_template: '{{ value_json["summaries"][0]["obsTimeLocal"].title() }}'
  resource: !secret wu_history_url
  scan_interval: 24:00:00

Which version of Studio Code Server are you using?
With version 4.1.0 I also got these type of error messages.
It seems a known issue (https://github.com/keesschollaart81/vscode-home-assistant/issues/1866)
I reverted back to version 4.0.0 and it works again without syntax error messages.

1 Like

Thanks @bertreb , you were spot on.