Closed sraka1 closed 11 months ago
Perhaps we'd need to create two ClimateEntity instances (well, DaikinClimate) in such a case? One for the actual leaving water temp and one for the offset? Or, perhaps create just the entity for the offset itself. You can get the other value (the actual leaving temp) via a sensor to view it. Open to suggestions
Same as #172. Did only notice recently that also on my device I have two values, one under advanced.
I guess it's similar, however the control mode in my case is leavingWaterTemperature
, not roomTemperature
or externalRoomTemperature
as it is in the other issue. In any case, would appreciate some guidance on how to best tackle this. Do you think my idea with two DaikinClimate
entities is feasible or should the single entity have the offsets only in this case and all the read-only stuff be exposed via sensors?
What do you mean by two values - in the Onecta app?
That I can change the leavingWaterOffset in the advanced settings even for my device which I control using the roomTemperature. Not sure about the best way to support this, will need some more time to think about this.
Can you try
tempSettable = tempSettable or device.getData(ATTR_TARGET_LEAVINGWATER_TEMPERATURE)["settable"]
Would be very nice to implement this because my heating curve is not linear. I would be able with this enhancement to correct the leaving water temperature automatically with the offset.
First I want to fix #194 coming week, this is second on the current todo list for this integration
Started with this, see https://github.com/jwillemsen/daikin_residential_altherma/tree/jwi-climatecontrolrework. This is really work in progress, only created multiple climate control entities, for each one found. When I have spare time next week I will continue with this.
https://github.com/speleolontra/daikin_residential_altherma/pull/205 has now support for this, still working on cleanup and adding support for regular Daikin AC units, could you test this in a second HA setup?
Can you retest with https://github.com/speleolontra/daikin_residential_altherma/pull/205, this refactors all code and resolves your issue.
Be aware that all entity IDs have changed, so check your automations and energy dashboard!
See https://github.com/jwillemsen/daikin_residential_altherma/releases/tag/v3.0.0 for a release including the necessary changes for this issue
@sraka1 @edautz Can you retest with https://github.com/jwillemsen/daikin_residential_altherma/releases/tag/v3.0.1 and let me know if that works.
@jwillemsen it works like charms! Thanks for your work, setting leaving water temperature for heating was a long awaited feature!
Thanks for the confirmation @scrivoluce! Sponsoring is always welcome, this was way more work as initially thought ;-)
I can barely imagine..! With this kind of interface (BRP069A78 in my case) can we imagine to have a local integration instead going trough cloud?
@scrivoluce As far as I know Daikin disabled the local access years ago, hopefully @Daikin-Europe does make this possible in the future
Installed it by hand. Seems to work OK. Thanks for your great work.
One remark: If I look at the downloades repos by HACS. It reports V2.8.2 of @speleolontra.
Thanks for the confirmation, I have a PR for hacs to add my fork
Question: I see an additional button. Climate Control On Off mode. What does this button do?
One of the bool on off switches, just on/off directly
Gateway: BRP069A62 controlMode: leavingWaterTemperature
https://github.com/speleolontra/daikin_residential_altherma/blob/master/custom_components/daikin_residential_altherma/climate.py#L103
The same issue exists for
current_temperature
is a bit trickier, because it would be nice to see both the actual leaving water temperature AND the currently set offset.I think it would be nice to have maybe 2 panels with this data (one with the actual leaving water temperature with the actual min and max, but not settable and one with the offset with -10 min and +10 max and settable!) - I'm not that familiar with HA's infrastructure and how that would be done. Would appreciate at least some guidance, then I could perhaps tackle this myself in a PR. cc @jwillemsen
It is also interesting that the leaving water offset is not shown as a sensor, despite it clearly being available. I haven't debugged the issue there yet.
P.S.: I added some extra logging lines when debugging the issue above
daikin_residential_altherma-24ce5eb0fce07b4c3af128b7d8e4b0a1--0cccec009d4350716d5d3e4f863b31e4.json.redacted.txt
home-assistant_2023-10-23T08-10-13.348Z.log