Numeric state problems, not actioned

Configuration
21

Then trigger from a state change to the sensor as I suggested above.

22

Not out of the wood yest and no central heating this morning, it was 14C in the house.
Iā€™ve now discovered the log info and trace info given on the lovelace front end viewed on a Falkon web browser , misses a lot of info, whereas the companion app , android, shows much

The trace on the companion app showed this:-

Executed 25March 2024 at 08:00:00
Error in ā€˜numeric_stateā€™. In ā€˜numeric_stateā€™ condition: entity sensor.tv_control_temp_sensors_temperature stateā€™ can not be process as a number

The same message then repeated as entity_id/0

alias: Central Heating Morning
description: ""
trigger:
  - platform: time
    at: "08:00:00"
condition:
  - condition: state
    entity_id: input_boolean.notify_away
    state: "off"
  - condition: numeric_state
    entity_id: sensor.tv_control_temp_sensors_temperature
    value_template: ""
    below: 16
action:
  - type: turn_on
    device_id: 0b6e278afd061db57c5ac8961518b0a9
    entity_id: b694f2bce0f086bce79b6505f2540bfd
    domain: switch
mode: single

Iā€™ve used the Shelly temperature sensor withe the Shelly 1+ PM throughout and the temperature is displayed on the lovelace gauges and graphs.
Checking the config in developer tools shows no error

What doesnā€™t it like with the condition using a numeric state ???, as I used numeric state conditions to cover the numeric threshold misses

23

Your value_template: "" line says ā€œignore the actual value and replace it with an empty stringā€. Thatā€™s why youā€™re getting that error. Why did you add that line?