Delay in Applying Target Temperature Setting - requires calling twice #21
Comments
|
Thanks for this nice feedback. |
|
Thank you for the |
|
I'll try and do some more structured testing later today and see what I can find. |
|
Thanks for all that. |
I haven't been able to codify a complete set and forget model for what I want the heat pumps to do, so little buttons are nice to have:
Don't be! It's awesome to have someone actively developing for this. I was excited to tap into the compressor data, but my units don't seem to send anything. Indoor <> Outdoor |
|
Yes it's a nice interface.
It seems to have a lot of units not supporting the compressor data. climate:
- platform: cn105
name: ${friendly_name}
id: "esp32_clim"
compressor_frequency_sensor:
name: Compressor frequency (clim Sejour)
vertical_vane_select:
name: Orientation de la Vane Verticale
horizontal_vane_select:
name: Orientation de la Vane Horizontale
isee_sensor:
name: ISEE Sensor
remote_temperature_timeout: 30min
update_interval: 10s # shouldn't be lessif you want to be sure to compile the last head sources each time you build the firmware, you also have to add the |
|
I've just committed a correction to address this issue. Configuration example: uart:
id: HP_UART
baud_rate: 2400
tx_pin: GPIO17
rx_pin: GPIO16
climate:
- platform: cn105
name: ${friendly_name}
id: "esp32_clim"
compressor_frequency_sensor:
name: Compressor frequency (clim Sejour)
vertical_vane_select:
name: Orientation de la Vane Verticale
horizontal_vane_select:
name: Orientation de la Vane Horizontale
isee_sensor:
name: ISEE Sensor
remote_temperature_timeout: 5min
update_interval: 1s # shouldn't be less than 1 second
debounce_delay : 500ms # delay to prevent bouncing |
|
Brilliant - I recompiled without modifying my config and the default debounce delay seems to have done the trick. Regarding the compressor reporting - whether or not I define the sensor in the configuration, I still get 0hz reported, so I'm assuming my models aren't compatible. [17:21:26][I][STATUS:106]: [received ]-> [room C°: 25.5, operating: NO , compressor freq: 0 Hz] |
|
Yes SwiCago lib gets the data from the packet whether the feature is supported or not. |
With https://github.com/geoffdavis/esphome-mitsubishiheatpump I was able to use a badge button on a dashboard to turn on and set temperature:
However, I'm finding with this component I need to hit the button twice - the first time turns it on, but doesn't set the temperature, I need to hit the button a second time to have that happen.
Logs:
Click here to expand logs
Expected Behavior:
The heat pump should set the target temperature to 23°C immediately upon setting the mode to cool without requiring a second command.
Actual Behavior:
The target temperature initially remains at an incorrect setting (27°C) until the command is sent again, after which it correctly updates to 23°C.
Steps to Reproduce:
Set the heat pump to cool mode with a target temperature of 23°C through the Home Assistant interface.
Observe that the target temperature does not apply until the command is issued a second time.
The text was updated successfully, but these errors were encountered: