Platform error 'climate' from integration 'template' Config Warning | Home Assistant | Page 1

north lynx Dec 20, 2024, 11:11 AM

#

I am using the config below, but see the following error when I check config prior to rebooting. I only dabble around the edges of HA so I have absolutely no clue what it means:

** Platform error 'climate' from integration 'template' - Platform template.climate not found **

I have a nagging feeling something like this was indicated in an update's breaking changes but so far have failed to find anything helpful by searching for the error message.

If anyone can help explain what's going on I'd really appreciate it!

https://pastebin.com/kQFiAqjm

climate:
  - platform: generic_thermostat
    name: HA Thermostat
    unique_id: JFYEM....
    heater: switch.boiler_relay #Boiler Switch
    target_sensor: sensor.lounge_temperature

    min_temp: 12
    max_temp: 30
    target_temp: 18
    away_temp: 13
    precision: 0.5
    
    ac_mode: false
    
    cold_tolerance: 0.3
    hot_tolerance: 0.2
    
    min_cycle_duration:
      seconds: 180

    initial_hvac_mode: "heat"


#define temperature sensors                
  - platform: template  
    sensors:
      ha_current_temperature:
        value_template: "{{ states.sensor.lounge_temperature }}" #read downstairs temp as a sensor
        friendly_name: Current Lounge Temperature
      # upstairs_temp:
      ha_office_temperature:
        value_template: "{{ states.sensor.roaming_temperature }}" 

        friendly_name: Current Office Temperature
      # hvac_temperature_knob:
      ha_thermostat_temperature:
        value_template: "{{ states.climate.ha_thermostat.attributes.temperature }}" 
        friendly_name: Current Thermostat Temperature

Pastebin

#--------------Create Boiler thermostat----------------------------...

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

latent sorrel Dec 20, 2024, 11:16 AM

#

There is no template climate in HA? Has that been made by ChatGPT?

north lynx Dec 20, 2024, 11:29 AM

#

Nope it's a 3-4 year old config - I just got around to updating and I'm cleaning up errors :/

#

Can confidently say that this setup pre-dates LLMs 😄

#

Ahh, have I perhaps put this in the wrong channel,,,

latent sorrel Dec 20, 2024, 11:30 AM

#

I guess, those might have been old template sensors.

north lynx Dec 20, 2024, 11:30 AM

#

Perhaps it should have been in integrations >?

#

https://www.home-assistant.io/integrations/generic_thermostat/

Home Assistant

Generic Thermostat

Turn Home Assistant into a thermostat

#

I believe that's the thing I'm attempting.

#

So is it the sensor definitions that are causing the errors ?

latent sorrel Dec 20, 2024, 11:32 AM

#

The sensor: before the -platform: template might be missing. It thinks, that is part of the climate integration.

latent sorrel Dec 20, 2024, 11:32 AM

#

north lynx So is it the sensor definitions that are causing the errors ?

Yes.

north lynx Dec 20, 2024, 11:32 AM

#

Ahhh!

#

You know... I'm not even certain that thing is required at all.

#

I'm looking for anywhere I might have used it , and I think it might have been a "Fiddling with this and giving up" moment 4 years ago coming back to haunt me.

latent sorrel Dec 20, 2024, 11:34 AM

#

dr_evil

north lynx Dec 20, 2024, 11:35 AM

#

I've commented them out, and will check on reboot. Thanks for rubber ducking, I think that might have been it. Years ago (before automations supported for: ) I was working on a 1hr boost switch for my heating and gave up - I think these things might be leftovers.

granite widget Dec 20, 2024, 11:37 AM

#

all your templates are wrong too

#

well, accept the attribute temperature one

latent sorrel Dec 20, 2024, 11:38 AM

#

To explain my GPT suspicion: it sometimes creates configs, that look plausible at first but contain nonsense. Unfortunately so well packed, that people still believe it.

granite widget Dec 20, 2024, 11:39 AM

#

Also, in-line comments will mess up your template

#

Put all comments before or after the yaml field

#

as for your templates being wrong, use the states method, or the states object method. Right now you're using the states object method but you're outputting the whole object, not the state from it.

#

and jorg is correct, you're missing sensor: before your template entities

north lynx Dec 20, 2024, 11:41 AM

#

I do believe those were fossils, I can't see anywhere in the system where they were even attempted to be used. I think I was trying to aggregate temperature values somehow (again, 4 years or so ago, so I don't remember)

#

I didn't realise inline comments were bad, either :/

granite widget Dec 20, 2024, 11:41 AM

#

well, that section of code you posted would have never worked or validated

#

HA wouldn't even let you read that section

#

so, I'm not sure how you've been using it at all

north lynx Dec 20, 2024, 11:42 AM

#

Exactly

granite widget Dec 20, 2024, 11:42 AM

#

Do you use packages?

north lynx Dec 20, 2024, 11:42 AM

#

What should that sensor definition look like ?

#

yeah this is in a heating package file.

#

to keep it separate

granite widget Dec 20, 2024, 11:42 AM

#

ok, so that whole package has been skipped then

#

meaning none of that in the file was even created

north lynx Dec 20, 2024, 11:43 AM

#

Nah because the thermostat is present and working,, though maybe only in the "last good" state before that extra guff got added?

granite widget Dec 20, 2024, 11:44 AM

#

I could see it only taking the generic thermostat portion and ignoring the template but producing an error. So that is possible.

#

because your spacing is correct

#

you should have an error in your logs saying something like platform template is not a valid climate blah blah blah

north lynx Dec 20, 2024, 11:44 AM

#

That's exatly it (Topic)

#

What should such a sensor definition look like though?

granite widget Dec 20, 2024, 11:45 AM

#

literally just put sensor: before your template entities

north lynx Dec 20, 2024, 11:45 AM

#

Just under a sensor: section

#

Ok, that's cool, I thought you were implying the definitions themselves were kaput

granite widget Dec 20, 2024, 11:45 AM

#

they are, you'll see when they are created

#

the main state will be wrong for 2 of the 3 of them

north lynx Dec 20, 2024, 11:54 AM

#

Aye, I just don' tknow why.

granite widget Dec 20, 2024, 11:56 AM

#

Because you're outputting the state object, not the state

#

and because you're using in-line comments

north lynx Dec 20, 2024, 11:57 AM

#

I've adjusted all the comments as per your earlier commnt.

#

But I don't know what "outputting the state object not the state" means in HA syntax.

#

That is, I know what outputting an object vs property is, I just don't know the HA syntax

granite widget Dec 20, 2024, 11:57 AM

#

#

read each bullet

#

from here

north lynx Dec 20, 2024, 12:23 PM

#

Thankyou!

This feels awfully relevant... : Avoid using states.sensor.temperature.state, instead use states('sensor.temperature')

#

🙂

#

"The following example results in the number 20.001:

{{ states.sensor.temperature.state }}"

#

They're using in the example the exact thing they say not to do, no wonder I'm confused :/

#

Got it!

#

#define temperature sensors                
sensor:
  - platform: template  
    sensors:
      ha_current_temperature:
        #read downstairs temp as a sensor
        value_template: "{{ states('sensor.lounge_temperature') }}"
        friendly_name: Current Lounge Temperature
      
      ha_office_temperature:
        #read upstairs temp as a sensor
        value_template: "{{ states('sensor.ble_temperature_office') }}"
        friendly_name: Current Office Temperature

      ha_thermostat_temperature:
        #read thermostat temp as a sensor
        value_template: "{{ state_attr('climate.ha_thermostat','temperature') }}"
        friendly_name: Current Thermostat Temperature

#Platform error 'climate' from integration 'template' Config Warning