Utility_Meter --- invalid config in YAML but not with Helper

Configuration
1

I am puzzled on this one.
I have 12 sensors I defined in config.yaml - everything is working fine.

The I tried to define a new sensor for the energy I am selling to the network.
It is coming also from Tasmota (same device providing the energy consumed and energy sold through 2 different mqtt values)

The “Check YAML” keeps warning that this is an invalid option…
→ I then tried to define the sensor using an helper… and its ok!

How can this be?

Accepted code in Config


mt1681_weekly_energy:
  unique_id: "mt1681-weeky"
  source: sensor.bitshake_smartmeterreader_mt681_total_in
  name: From netz weekly
  cron: "0 0 * * 7"

INVALID Option


mt1681_OutWeekly_energy:
  source: sensor.bitshake_smartmeterreader_mt681_total_out
  name: To netz weekly
  cron: "0 0 * * 7"
  unique_id: "mt1681-OutWeekly"

The sensor.bitshake_smartmeterreader_mt681_total_out is ok and I can access it as an entity

Any idea please

3

my apologies. The code is formatted correctly (it’s in an include file… but I copied and pasted and the spaces don’t show… but it is formatted ok).

The error is

Screenshot 2023-12-19 at 18.02.02
Screenshot 2023-12-19 at 18.02.022452×608 64.6 KB

The sensor is in a customise file and is defined as (again the spaces are ok… - I have now edited the post to show the formatting)

sensor.bitshake_smartmeterreader_mt681_total_in:
  unit_of_measurement: "kWh"
  device_class: energy
  state_class: total_increasing

sensor.bitshake_smartmeterreader_mt681_total_out:
  unit_of_measurement: "kWh"
  device_class: energy
  state_class: total_increasing
4

The main difference I can see is that in your invalid code - you have uppercase letters, which you should not.

5

damn!!! you are the MAN!
I didnt know about the uppercase!

Many thanks!!!

1 Like