Internally set temp not matching external temperature sensor

[Quarks-1]

I'm using the sensor implementation to set the current temperature on my HVAC, but the temperature being displayed as 'current' is often a bit off or dated compared to the actual


Below is the YAML of the portion dealing with sensors and the climate component

sensor:
  # Uptime sensor.
  - platform: uptime
    name: ${name} Uptime

  # WiFi Signal sensor.
  - platform: wifi_signal
    name: ${name} WiFi Signal
    update_interval: 120s
  
  - platform: homeassistant
    id: current_temp
    entity_id: sensor.living_room_temperature_sensor_temperature
    internal: true
    on_value:
      then:
        - lambda: |-
            id(hp).set_remote_temperature((x - 32.0) * (5.0 / 9.0));

# Create a button to restart the unit from HomeAssistant. Rarely needed, but can be handy.
button:
  - platform: restart
    name: "Restart ${friendly_name}"

climate:
  - platform: cn105
    id: hp
    name: "${friendly_name}"
    icon: mdi:heat-pump
    visual:
      min_temperature: 16
      max_temperature: 31
      temperature_step:
        target_temperature: 1
        current_temperature: 0.1
    compressor_frequency_sensor:
      name: ${name} Compressor Frequency
    vertical_vane_select:
      name: ${name} Vertical Vane
    horizontal_vane_select:
      name: ${name} Horizontal Vane
    isee_sensor:
      name: ${name} ISEE Sensor
    remote_temperature_timeout: 30min
    debounce_delay : 500ms
    update_interval: 4s```

Any idea what could be done to fix this?

[Quarks-1]

I have also tried using the api with this automation

description: ""
trigger:
  - platform: state
    entity_id: sensor.basement_temp_sensor_temperature
condition: []
action:
  - service: esphome.basement_ac_set_remote_temperature
    data:
      temperature: "{{ states('sensor.basement_temp_sensor_temperature') | float }}"
mode: single

and this service in the esp32 yaml

# Enable Home Assistant API
api:
  services:
    - service: set_remote_temperature
      variables:
        temperature: float
      then:
# Select between the C version and the F version
# Uncomment just ONE of the below lines. The top receives the temperature value in C,
# the bottom receives the value in F, converting to C here.
        # - lambda: 'id(hp).set_remote_temperature(temperature);'
       - lambda: 'id(hp).set_remote_temperature((temperature - 32.0) * (5.0 / 9.0));'
    - service: use_internal_temperature
      then:
        - lambda: 'id(hp).set_remote_temperature(0);'

But it still doesn't update when the automation is fired. Any ideas?

[echavet]

Hello @Quarks-1
Thanks for your message,
I'm experiencing the same PB.
I'm gonna watch the code to identify where it could come from.
In my case, as soon as I set it ON, the temperature is updated.
I'm thinking about sending the power mode with the temperature packet to see what happens...
I will update the thread as soon as I've tested.

[Quarks-1]

I did some testing myself last night and noticed that when I call the service directly in the develop tab it works, with maybe 5-10s delay of updating on the climate card. I wonder what's causing the difference between the automation and the service.

[echavet]

Could you provide your yaml content please ?

[echavet]

Could you provide your yaml content please ?

Sorry, ignore my msg.

[echavet]

Well, as long as nobody identify an issue in the component, I would be tempted to think that the heatpump itself is lazy about updating it's room temperature unless power is ON.
I let here as a lead (and for memory if I come to dig again later), that maybe the packet has to contain the power mode (and the remote_temperature) for the heatpump to take it seriously.