Using External Temp Sensor to Manage Room Temp Accuracy V2

[iredsell-png]

Firstly I recognise that I am new to YAML and HA, however I have been trying to setup and test this automation. I am attempting to link my wiser system to an ESP32 Thermostat creatively named bathtemp its integration is ESPHome and its sensor is temperature

Using the first automation script as a trigger I have followed the instructions which appeared to be straightforward resulting in the script as appended.

The ESPDevice works locally I can view it and see the output updating. I can also use it to drive a switch

What I wish to do though is link to Wiser. I found this excellent GitHub ad I want to thank you for your work.

I have used the run to test the automation but suspect that as there is no entity triggered the trace results in an entity not found within the following script -

  {% if temp_sensor in integration_entities(temp_sensor_integration)
          and temp_sensor.startswith(temp_sensor_prefix) 
          and temp_sensor.endswith(temp_sensor_suffix)
  %}

I have checked the entity name, integration and sensor name and I realise that all I had to do was change 2 lines of variables, but I cannot get the automation to trigger and I am running out of ideas to diagnose further.

Can anyone advise this enthusiastic amateur?

Thank you

`alias: Fire Event When Room Monitoring Temp Sensors Change Reading
description: ""
triggers:
  - event_type: state_changed
    variables:
      temp_sensor: "{{trigger.event.data.entity_id}}"
    trigger: event
conditions:
  - condition: template
    value_template: |-
      {% if temp_sensor in integration_entities(temp_sensor_integration)
              and temp_sensor.startswith(temp_sensor_prefix) 
              and temp_sensor.endswith(temp_sensor_suffix)
      %}
        True
      {% endif %}
actions:
  - event: external_temp_sensor_changed
    event_data:
      entity_id: "{{temp_sensor}}"
      old_temp: "{{trigger.event.data.old_state.state}}"
      new_temp: "{{trigger.event.data.new_state.state}}"
trigger_variables:
  temp_sensor_integration: ESPHome
  temp_sensor_prefix: sensor.bathtemp
  temp_sensor_suffix: temperature
mode: queued
max: 25
`

[msp1974]

Hi @iredsell-png!

So, firstly, if you have 'how do I' or 'help me!' type questions, post them on the forum as you will likely get much better response. No issue posting here, but then you have to wait for me or Angelo to respond in the main.

Secondly, this is an old automation and there is an issue open that it caused lockups in some peoples environments. So, with that caveat, it should still work though.

I think the issue is your temp_sensor_integration line. All HA integration names (really internal 'domain' keys) are lowercase. So ESPHome shoudl be 'esphome'.

Assuming then that your sensor is called sensor.bathtemp_temperature or sensor.bathtemp_[whatever]_temperature this should work.

[iredsell-png]

Mark Thank you for taking the time to respond. I apologise if I screw up the protocol, this is all new to me, however I am working as hard as I can to diligently work through the issue. The Old automation comment implies that the Wiser integration is now uninteresting, reprioritised or that there may be something more vital. If so I can not find it. I have been working extensively on troubleshooting this one. I tried to reduce the fault in my implementation by isolating each element of the integration {% if temp_sensor in integration_entities(temp_sensor_integration) and temp_sensor.startswith(temp_sensor_prefix) and temp_sensor.endswith(temp_sensor_suffix) %} Ref temp_sensor_integration: esphome temp_sensor_prefix: sensor.bathtemp temp_sensor_suffix: temperature I do not know how to find out what is retrieved from the entity list, however when I reduce the selection to just esphome the trigger happens more frequently. Every 1 second I have tried using the .in statement as well and I cannot find out which element is at fault. If I could check the variables in line I would be able to go further. Thanks again for your intervention and I would be happy to continue this on the Community site. Regards Ian By cutting out each of the select statements and I still get a False in the trace which leads me to believe that the alert is not being trapped to the ESPHome device

…

On 5 Nov 2025, at 17:40, Mark Parker ***@***.*** ***@***.***>> wrote: msp1974 left a comment (asantaga/wiserHomeAssistantPlatform#619) <#619 (comment)> Hi @iredsell-png <https://github.com/iredsell-png>! So, firstly, if you have 'how do I' or 'help me!' type questions, post them on the forum as you will likely get much better response. No issue posting here, but then you have to wait for me or Angelo to respond in the main. Secondly, this is an old automation and there is an issue open that it caused lockups in some peoples environments. So, with that caveat, it shoud still work though. I think the issue is your temp_sensor_integration line. All HA integration names (really internal 'domain; keys) are lowercase. So ESPHome shoudl be 'esphome'. Assuming then that your sensor is called sensor.bathtemp_temperature or sensor.bathtemp_[whatever]_temperature thsi shoudl work. — Reply to this email directly, view it on GitHub <#619 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BY6HAW7UVSEL6IOQLTWEFRT33IR7PAVCNFSM6AAAAACLG4NY5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOJSGIZTSMRWHE>. You are receiving this because you were mentioned.