Core: Climate mill target temperature not reflected

Created on 12 Feb 2019  路  11Comments  路  Source: home-assistant/core

Home Assistant release with the issue:

0.87.1

Last working Home Assistant release (if known):
0.84.4

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

https://www.home-assistant.io/components/climate.mill/

Description of problem:
When setting the target temperature for Mill Heater the target temperature is not updated in the front-end. I can see it's setting the temperature on the heater itself, but it's not reflected back to HomeAssistant. (Last time it was working was in 0.84.x, might work in 0.85 as well, but I jumped from 0.84 to 0.86.)

Everything else seems to work fine with the Mill component.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):


Traceback (if applicable):


Additional information:
Checked if the old UI "states" displayed it any differently, but the problem exists there as well.

mill stale

All 11 comments

Where are you setting the temperature?
In the Mill app?

From HomeAssistant, tried both the climate card and entity-card. I think it's reading the target temperature from the Mill app planning/scheduling instead of the temporary/override target you set when setting the target from HomeAssistant.

From the screenshot below, the Office-target was set from HomeAssistant to 22 degrees, and that target has nearly been reached. The heat-value still shows 16 degrees though.

image

Checked in the Mill App and the away-target temperature is 16 degrees for both rooms. So looks like that's the field being mapped to the Heat-field in HomeAssistant maybe?

Ok, it works here, and I am not reproduce it

Here's the state attributes if that helps:
{ "current_temperature": 22, "min_temp": 5, "max_temp": 35, "temperature": 16, "target_temp_step": 1, "fan_mode": "on", "fan_list": [ "on", "off" ], "operation_mode": "heat", "operation_list": [ "heat", "off" ], "open_window": null, "heating": 0, "controlled_by_tibber": 0, "heater_generation": 2, "room": "Kontor", "avg_room_temp": 16, "friendly_name": "Oven Office", "supported_features": 4289 }

Anything I could do to debug this? Might have something to do with difference in Mill Heater generations? Both are gen.2

I'll give this a try to debug later today.

logger: default: error logs: homeassistant.components.climate.mill: debug pymill: debug

Is the heater sat to "independent" in the mill app?

It's connected to a room in the app. If I check the oven settings from within the room it's possible to toggle on or off for the option: "control unit independently". This option is set to "off", is it supposed to be set to "on" instead?

Should work in both cases. But try to change it to "on"

Nice! Works after enabling independent control. Want me to debug any further to find out why it doesn't work with independent control set to "off"? Or are you able recreate that part?

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 馃憤
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Not sure if anyone else has reproduced this. The solution is to set the heater to "independent" even if it's added to a room. No need to keep this ticket open, but might be worth adding to the documentation though. Closing the ticket now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

MartinHjelmare picture MartinHjelmare  路  3Comments

neonandu picture neonandu  路  3Comments

Konstigt picture Konstigt  路  3Comments

i-am-shodan picture i-am-shodan  路  3Comments

arangates picture arangates  路  3Comments