Invalid config for 'sensor' at configuration.yaml after last 2025.12 udate

[newslettersns2000]

Hello, I’m going crazy with this damn 2025.12 update. Since then, I keep getting “Invalid config for ‘sensor’ at configuration.yaml” when checking in the developer tools.
What’s going wrong?
Invalid config for ‘sensor’ at configuration.yaml, line 127: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 128: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 131: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 132: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 135: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 136: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 139: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 140: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 143: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 144: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 147: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 148: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 151: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 152: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 155: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 156: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 159: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 160: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 163: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 164: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 167: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 168: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 172: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 173: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 178: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 179: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 182: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 183: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 186: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 187: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 190: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 191: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 194: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 195: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 198: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 199: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 202: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 203: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 206: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 207: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 210: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 211: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 214: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 215: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 218: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 219: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 222: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 223: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 227: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 228: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 233: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 234: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 237: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 238: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 240: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 241: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 244: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 245: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 248: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 249: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 251: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 252: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 255: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 256: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 259: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 260: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 263: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 264: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 267: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 268: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 271: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 272: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 275: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 276: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 280: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 281: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 286: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 287: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 290: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 291: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 294: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 295: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 298: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 299: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 302: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 303: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 306: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 307: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 310: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 311: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 314: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 315: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 318: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 319: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 322: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 323: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 326: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 327: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 330: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 331: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 335: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 336: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 341: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 342: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 345: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 346: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 349: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 350: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 353: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 354: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 357: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 358: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 361: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 362: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 365: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 366: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 369: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 370: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 373: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 374: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 377: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 378: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 381: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 382: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 385: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 386: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 390: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 391: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 408: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 409: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 412: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 413: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 416: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 417: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 420: required key ‘platform’ not provided
Invalid config for ‘sensor’ at configuration.yaml, line 421: required key ‘platform’ not provided

Here’s my config.

default_config:

Load frontend themes from the themes folder

frontend:
themes: !include_dir_merge_named themes

extra_module_url:

- /local/card-mod.js

################################################################################

T E M P L A T E

################################################################################
template:

• sensor:
  ################################

Shelly EM3 Berechnung

################################
###########

Zusammengerechneter Strom aller 3 Phasen (Echtzeitverbrauch)

###########
- name: ‘Gesamt Strom’
unique_id: power_total
state: >-
{{
[ states(‘sensor.shellyem3_485519d9b0fa_channel_a_power’),
states(‘sensor.shellyem3_485519d9b0fa_channel_b_power’),
states(‘sensor.shellyem3_485519d9b0fa_channel_c_power’),
] | map(‘float’) | sum | round(3)
}}
unit_of_measurement: W
device_class: power
state_class: measurement
availability: >-
{{
[ states(‘sensor.shellyem3_485519d9b0fa_channel_a_power’),
states(‘sensor.shellyem3_485519d9b0fa_channel_b_power’),
states(‘sensor.shellyem3_485519d9b0fa_channel_b_power’),
] | map(‘is_number’) | min | round(3)
}}

###########

Zusammengerechnete Stromstärke aller 3 Phasen (Echtzeit)

###########

- name: 'Gesamt Stromstärke'
  unique_id: current_total
  state: >-
      {{ 
        [ states('sensor.shellyem3_485519d9b0fa_channel_a_current'), 
          states('sensor.shellyem3_485519d9b0fa_channel_b_current'),
          states('sensor.shellyem3_485519d9b0fa_channel_c_current'),
        ] | map('float') | sum
      }}
  unit_of_measurement: A
  device_class: current
  state_class: measurement
  availability: >-
      {{ 
        [ states('sensor.shellyem3_485519d9b0fa_channel_a_current'), 
          states('sensor.shellyem3_485519d9b0fa_channel_b_current'),
          states('sensor.shellyem3_485519d9b0fa_channel_c_current'),
        ] | map('is_number') | min
      }}

###########

Berechnung Netzbezug in W

###########

- name: "power_import"
  unit_of_measurement: 'W'
  device_class: power
  state_class: measurement
  state: >-
      {% if (states('sensor.gesamt_strom'))|float(0) > 0 %}
        {{ states('sensor.gesamt_strom')|float(0) }}
      {% else %}
        {{ 0 }}
      {% endif %}
  availability: "{{
        [ states('sensor.gesamt_strom')
        ] | map('is_number') | min
      }}"

###########

Berechnung Einspeißung in W

###########

- name: "power_export"
  unit_of_measurement: 'W'
  device_class: power
  state_class: measurement
  state: >-
      {% if (states('sensor.gesamt_strom'))|float(0) < 0 %}
        {{ (states('sensor.gesamt_strom'))|float(0)  }}
      {% else %}
        {{ 0 }}
      {% endif %}
  availability: "{{
        [ states('sensor.gesamt_strom')
        ] | map('is_number') | min
      }}"

zha:
zigpy_config:
ota:
extra_providers:
- type: sonoff # Auto update Sonoff devices

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
###########

Open Hardware Monitor Home Assistant

###########
sensor:

Open Hardware Monitor AD

• platform: openhardwaremonitor
  host: 192.168.253.200

Open Hardware Monitor EX

• platform: openhardwaremonitor
  host: 192.168.253.201

Open Hardware Monitor mg

• platform: openhardwaremonitor
  host: 192.168.253.205

scan_interval: 15

#AD SENSORS

• sensor:
• default_entity_id: sensor.vm_ad_uptime_hours
  name: ad Uptime (Hours)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘uptime_hours’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_uptime_days
  name: ad Uptime (Days)
  state: ‘{{ states(’‘sensor.vm_ad_uptime_hours’‘)|int /24|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_ad_cpu_count
  name: ad CPU Count
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘cpu_count’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_cpu_use_pct
  name: ad CPU Used (%)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘cpu_use_pct’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_memory_allocated_mb
  name: ad Memory Allocated (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘memory_allocated_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_memory_used_mb
  name: ad Memory Used (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘memory_used_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_used_space_gb
  name: ad Used Space (GB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘used_space_gb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_tools_status
  name: ad Tools Status
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘tools_status’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_guest_ip
  name: ad Guest IP
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘guest_ip’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_snapshots
  name: ad Snapshots
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘snapshots’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ad_memory_used_pct
  name: ad Memory Used (%)
  state: ‘{{ states(’‘sensor.vm_ad_memory_allocated_mb’‘)|int / states(’‘sensor.vm_ad_memory_used_mb’‘)|int
  *100|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_ad_used_space_pct
  name: ad Storage Used (%)
  state: ‘{{102400 / states(’‘sensor.vm_ad_used_space_gb’‘)|int /10.24|round(1)
  }}’
  #ex SENSORS
• sensor:
• default_entity_id: sensor.vm_ex_state
  name: ex State
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘state’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_uptime_hours
  name: ex Uptime (Hours)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘uptime_hours’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_uptime_days
  name: ex Uptime (Days)
  state: ‘{{ states(’‘sensor.vm_ex_uptime_hours’‘)|int /24|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_ex_cpu_count
  name: ex CPU Count
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘cpu_count’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_cpu_use_pct
  name: ex CPU Used (%)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘cpu_use_pct’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_memory_allocated_mb
  name: ex Memory Allocated (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘memory_allocated_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_memory_used_mb
  name: ex Memory Used (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘memory_used_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_used_space_gb
  name: ex Used Space (GB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘used_space_gb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_tools_status
  name: ex Tools Status
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘tools_status’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_guest_ip
  name: ex Guest IP
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘guest_ip’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_snapshots
  name: ex Snapshots
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ex’‘,’‘snapshots’‘) }}’
• sensor:
• default_entity_id: sensor.vm_ex_memory_used_pct
  name: ex Memory Used (%)
  state: ‘{{ states(’‘sensor.vm_ex_memory_allocated_mb’‘)|int / states(’‘sensor.vm_ex_memory_used_mb’‘)|int
  *100|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_ex_used_space_pct
  name: ex Storage Used (%)
  state: ‘{{102400 / states(’‘sensor.vm_ex_used_space_gb’‘)|int /10.24|round(1)
  }}’
  #mg SENSORS
• sensor:
• default_entity_id: sensor.vm_mg_state
  name: mg State
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘state’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_uptime_hours
  name: mg Uptime (Hours)
• sensor:
• default_entity_id: sensor.vm_mg_uptime_days
  name: mg Uptime (Days)
  state: ‘{{ states(’‘sensor.vm_mg_uptime_hours’‘)|int /24|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_mg_cpu_count
  name: mg CPU Count
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘cpu_count’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_cpu_use_pct
  name: mg CPU Used (%)
• sensor:
• default_entity_id: sensor.vm_mg_memory_allocated_mb
  name: mg Memory Allocated (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘memory_allocated_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_memory_used_mb
  name: mg Memory Used (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘memory_used_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_used_space_gb
  name: mg Used Space (GB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘used_space_gb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_tools_status
  name: mg Tools Status
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘tools_status’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_guest_ip
  name: mg Guest IP
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘guest_ip’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_snapshots
  name: mg Snapshots
  state: ‘{{ state_attr(’‘sensor.esxi_vm_mg’‘,’‘snapshots’‘) }}’
• sensor:
• default_entity_id: sensor.vm_mg_used_space_pct
  name: mg Storage Used (%)
  state: ‘{{102400 / states(’‘sensor.vm_mg_used_space_gb’‘)|int /10.24|round(1)
  }}’
• sensor:
• default_entity_id: sensor.vm_mg_used_space_pct
  name: mg Storage Used (%)
  state: ‘{{102400 / states(’‘sensor.vm_mg_used_space_gb’‘)|int /10.24|round(1)
  }}’
  #Sophos SENSORS
• sensor:
• default_entity_id: sensor.vm_sophos9_state
  name: sophos State
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘state’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_uptime_hours
  name: sophos Uptime (Hours)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘uptime_hours’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_uptime_days
  name: sophos Uptime (Days)
  state: ‘{{ states(’‘sensor.vm_sophos9_uptime_hours’‘)|int /24|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_cpu_count
  name: sophos CPU Count
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘cpu_count’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_cpu_use_pct
  name: sophos CPU Used (%)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘cpu_use_pct’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_memory_allocated_mb
  name: sophos Memory Allocated (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘memory_allocated_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_memory_used_mb
  name: sophos Memory Used (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘memory_used_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_used_space_gb
  name: sophos Used Space (GB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘used_space_gb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_tools_status
  name: sophos Tools Status
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘tools_status’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_guest_ip
  name: sophos Guest IP
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘guest_ip’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_snapshots
  name: sophos Snapshots
  state: ‘{{ state_attr(’‘sensor.esxi_vm_sophos9’‘,’‘snapshots’‘) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_memory_used_pct
  name: sophos Memory Used (%)
  state: ‘{{ states(’‘sensor.vm_sophos9_memory_allocated_mb’‘)|int / states(’‘sensor.vm_sophos9_memory_used_mb’‘)|int
  *100|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_sophos9_used_space_pct
  name: sophos Storage Used (%)
  state: ‘{{102400 / states(’‘sensor.vm_sophos9_used_space_gb’‘)|int /10.24|round(1)
  }}’
  #UC SENSORS
• sensor:
• default_entity_id: sensor.vm_uc_state
  name: UC State
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘state’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_uptime_hours
  name: UC Uptime (Hours)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘uptime_hours’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_uptime_days
  name: UC Uptime (Days)
  state: ‘{{ states(’‘sensor.vm_uc_uptime_hours’‘)|int /24|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_uc_cpu_count
  name: UC CPU Count
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘cpu_count’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_cpu_use_pct
  name: UC CPU Used (%)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘cpu_use_pct’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_memory_allocated_mb
  name: UC Memory Allocated (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘memory_allocated_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_memory_used_mb
  name: UC Memory Used (MB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘memory_used_mb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_used_space_gb
  name: UC Used Space (GB)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘used_space_gb’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_tools_status
  name: UC Tools Status
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘tools_status’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_guest_ip
  name: UC Guest IP
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘guest_ip’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_snapshots
  name: UC Snapshots
  state: ‘{{ state_attr(’‘sensor.esxi_vm_uc’‘,’‘snapshots’‘) }}’
• sensor:
• default_entity_id: sensor.vm_uc_memory_used_pct
  name: UC Memory Used (%)
  state: ‘{{ states(’‘sensor.vm_uc_memory_allocated_mb’‘)|int / states(’‘sensor.vm_uc_memory_used_mb’‘)|int
  *100|round(1) }}’
• sensor:
• default_entity_id: sensor.vm_uc_used_space_pct
  name: UC Storage Used (%)
  state: ‘{{102400 / states(’‘sensor.vm_uc_used_space_gb’‘)|int /10.24|round(1)
  }}’
  ###########

RegenRadar

###########

• platform: rest
  name: regenradar
  scan_interval: 300
  json_attributes:
  • raintext
  • rainin30min
  • rainin60min
  • rainin120min
    resource: https://morgenwirdes.de/api/v3/rain.php?lat=48.669&long=11.904
    value_template: “{{ value_json.raintext }}”
• sensor:
• default_entity_id: sensor.rrraintext
  name: Regentext
  state: ‘{{ state_attr(’‘sensor.regenradar’‘, ‘‘raintext’’) }}’
• sensor:
• default_entity_id: sensor.rrrainin30min
  name: Regenin30min
  state: ‘{{ state_attr(’‘sensor.regenradar’‘, ‘‘rainin30min’’) }}’
• sensor:
• default_entity_id: sensor.rrrainin60min
  name: Regenin60min
  state: ‘{{ state_attr(’‘sensor.regenradar’‘, ‘‘rainin60min’’) }}’
• sensor:
• default_entity_id: sensor.rrrainin120min
  name: Regenin120min
  state: ‘{{ state_attr(’‘sensor.regenradar’‘, ‘‘rainin120min’’) }}’

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Read this thread. Petro has written tools to help you mentioned in this thread.
After you read that, if you still have questions ask there.

Deprecation of legacy template entities in 2025.12

TLDR: Legacy template entities (alarm_control_panel, binary_sensor, cover, fan, light, lock, sensor, switch, vacuum, weather) are being deprecated in 2025.12. Legacy template entities will no longer work after 2026.6. I wanted to avoid the deprecation, however it’s apparent that it’s not possible due to future plans. The Deprecation Please use this thread to ask questions and address concerns about the upcoming deprecation of legacy template entities. The Future You may have noticed an incre…

[tom_l]

@newslettersns2000

Open Hardware Monitor Home Assistant

###########
sensor:

Open Hardware Monitor AD

• platform: openhardwaremonitor
  host: 192.168.253.200

Open Hardware Monitor EX

• platform: openhardwaremonitor
  host: 192.168.253.201

Open Hardware Monitor mg

• platform: openhardwaremonitor
  host: 192.168.253.205

scan_interval: 15

#AD SENSORS

• sensor:
• default_entity_id: sensor.vm_ad_uptime_hours
  name: ad Uptime (Hours)
  state: ‘{{ state_attr(’‘sensor.esxi_vm_ad’‘,’‘uptime_hours’‘) }}’
• sensor:

Please edit your post and format it correctly.

[finity]

It’s because you put all of the template sensors under the “sensor:” key instead of the “template:” key.