Action sets the wrong value

Configuration
, ,
1

Hi, I created this action to turn my heater to 10˚C at 11:30PM. Yet when I trigger this action all it does is setting my Local temperature calibration to -429496720.6.

alias: "Heater off at night"
description: ""
triggers:
  - trigger: time
    at: "23:30:00"
    weekday:
      - sun
      - mon
      - tue
      - wed
      - thu
conditions: []
actions:
  - device_id: 2358ae4771f8ac73a71741233648484b
    domain: number
    entity_id: 41728e1a0b5813d0683656c5d877e81d
    type: set_value
    value: 10
mode: single

I’m completely new to home automation and I’m getting currently overwhelmed by all the different protocols and applications. I’m using Zigbee2MQTT to connect my Zigbee devices via MQTT to my Home Assitant container with the MQTT integration.

I have no idea where the issue could be coming from. Could it be the hardware, Zigbee2mqtt, Mosquitto or Home Automation itself?

How could I debug this issue? entity_id seems to be the culprit here, but I’m not sure where I could find the appropriate ID of the variable that contains the temperature value.

2

My advice is to not use device ids, See: Why and how to avoid device_ids in automations and scripts

3

Most likely you are not supposed to use set number.
You probably should use the climate.set_temperature

4

Thanks very much for the answers. The solution for me would be not to use the UI anymore to create the automations since it creates these awful yaml files. I solved this very issue by not using the set_value and the hashes anymore.

But I noticed that once I have a proper yaml file the UI seems to be able to display the variables and properties and even let’s me edit them in the UI. Is there a way to make the UI actually use proper IDs and make proper suggesstions when creating an automation?

5

You can still use the UI. Just don’t select triggers, conditions or actions that use devices. Select the ones that use entities. As per the link I posted.