Closed darsys closed 3 years ago
I modified my thermostat config as show below and the log does not report in the heat action event. I have setup a development environment to see if I can contribute a fix.
heat_action:
- logger.log:
format: "Shop east thermostat turning ON Current Temp: value %.1f and Setpoint %.1f"
args: [ 'id(shop_east_thermostat).target_temperature', 'id(shop_east_temperature).state' ]
- switch.turn_on: shop_east_heat_low
idle_action:
- logger.log:
format: "Shop east thermostat turning OFF Current Temp: value %.1f and Setpoint %.1f"
args: [ 'id(shop_east_thermostat).target_temperature', 'id(shop_east_temperature).state' ]
- switch.turn_off: shop_east_heat_low
`
This issue was because I had a generic climate device defined in my home assistant configuration (using the esphome temp and switched) and there was not a name defined in my esphome thermostat configuration. HA/esphome did not configure the esphome thermostat and obviously all the commands were going to the generic climate device defined in ha. I am closing the issue and hope I haven't wasted anyone else's time.
Operating environment/Installation (Hass.io/Docker/pip/etc.):
Host is Hass.io running in a debian xen vm
ESP (ESP32/ESP8266, Board/Sonoff):
Esp8266 WemosD1 mini clone mounted on a breadboard (yes i know...) powered with a wall usb brick
ESPHome version (latest production, beta, dev branch)
ESPHome version 1.17.0-dev
Affected component:
https://esphome.io/components/climate/thermostat.html?highlight=thermostat
Description of problem: The component functionality works as expected. In the log I changed the setpoint to above current temperature via home assistant ui and the esphome thermostat component turns on the heat. I then change the setpoint back to below the current temperature and the esphome thermostat component turns off the heat, Watching the component via the home assistant developer tools shows visible component properties properly changing including the temps and heat status. The debug log for the climate component does not, however, output the correct values to match the status of the component.
I would also mention that a log event for when the setpoint is updated seems appropriate? This could probably be considered a separate issue.
Problem-relevant YAML-configuration entries:
Logs (if applicable):
Additional information and things you've tried: I have tried simplifying the config by removing devices and using different output devices for the heat action.