[luxtronikheatpump] wrong channel name for setting hot water target temperature

[pelerner]

The channel "temperatureHotWaterTarget" seems to be disfunctional - at least for writing back to the heat pump.

One has to link the channel "temperatureHotWaterCoverage" to some setpoint item, in order to be able to control the hot water temperature on heatpump.

I propose the following docu change
temperatureHotWaterTarget => temperatureHotWaterCoverage

Eventually clarify misleading channel name "temperatureHotWaterTarget" - seems to be a read only chanel currently !?

[pelerner]

Maybe the issue need some more investigation on the software side.

see #11135

I can confirm, that on my "Buderus WPL IK 12" only the channel "temperatureHotWaterCoverage" can write back to the heatpump.

Channel "temperatureHotWaterTarget" is more or less disfunct.
It shows a value on Startup but does not mirror chanel "temperatureHotWaterCoverage" on changes.

I've also used luxtronik binding on ohab v2.5.x.
There was a channel to mirror the hot water target temperatur.

ohab v2.5 - working ok

.items

// ** Warmwasser
Number iWP_WARMWASSER_TEMPERATURE   "WP Warmwasser Temperatur [%.1f]"	{ novelanheatpump="warmwater_temperature" }
Number iWP_WARMWASSER_SOLL	"WP Warmwasser Soll [%.1f °C]"	{ novelanheatpump="temperature_servicewater_reference" }
Number iWP_WARMWASSER_IST	"WP Warmwasser Ist (TBW) [%.1f °C]"	{ novelanheatpump="temperature_servicewater" }

.sitemap

Setpoint item=iWP_WARMWASSER_TEMPERATURE  minValue=10 maxValue=65 step=1
Text     item=iWP_WARMWASSER_SOLL
Text     item=iWP_WARMWASSER_IST	

Note: iWP_WARMWASSER_TEMPERATURE is Setpoint item !!

ohab v3.2 - also working ok

.items

// Betriebsart Warmwasser
Number:Temperature iWP_WARMWASSER_COV	"WP Warmwasser Temperatur [%.1f]"			<temperature>	{ channel="luxtronikheatpump:heatpump:heatpump:temperatureHotWaterCoverage" }
Number:Temperature iWP_WARMWASSER_SOLL	"WP Warmwasser (PRÜFEN!!) [%.1f °C]"		<temperature>	{ channel="luxtronikheatpump:heatpump:heatpump:temperatureHotWaterTarget" }
Number:Temperature iWP_WARMWASSER_IST	"WP Warmwasser Ist (TBW) [%.1f °C]"			<temperature>	{ channel="luxtronikheatpump:heatpump:heatpump:temperatureHotWater" }

.sitemap

Setpoint item=iWP_WARMWASSER_COV minValue=10 maxValue=65 step=1
Text     item=iWP_WARMWASSER_SOLL
Text     item=iWP_WARMWASSER_IST

Note: iWP_WARMWASSER_COV is Setpoint item !!

[lolodomo]

@sgiehl as binding maintainer, can you please comment ?

[sgiehl]

@lolodomo I'm actually not notified when changes are proposed for the binding. So unless someone mentions me I might not notice that.

@pelerner Maybe it depends on the heatpump and/or the software version if the one or the other channel can be used.
Personally I own a Novelan LD7 with software version 2.86. For me the channel temperatureHotWaterTarget works correctly, while the coverage channel isn't abel to update values. It always returns the value from the target channel.
Do you maybe have some additional heat source connected to your heat pump, like solar panels or gas therme or anything?

We maybe could update the docs to at least mention both channels.

[pelerner]

@sgiehl My heatpump is just a plain air-water-heatpump from 2015. The only additional heat source is an electrical heat element for backup purposes or in the event of extreme cold ("Zusatzheizstab"). When it's too cold, it seems the heatpump can engage bivalent mode.

I think the temperatureHotWaterTarget channel is one of the most used settings.
A documentation hint would help others ...

On my Buderus WPL IK 12 I have softwareVersion="B1.62" ... don't know if this is somehow matchable to the Novelan line of development ... is there any way to reliable reverse engineer all available channels for a given heat pump? Or is it just trial and error ...

BTW ... I had logged the attached values with opendta-v0.15-win some time ago ... perhaps this tells you something ...or some one else ...

buderus-wpl12ik - 20190425.csv

P

[sgiehl]

@pelerner
I'm not sure if it is easily possible to detect if the one or the other channel should be used. For me and a couple of others on the forum it works like it is now. Maybe updating the documentation is the only thing we can do 🤔

Regarding a channel list: On older heatpumps there was a java applet to configure the heatpump. That applet has been used to kind of reverse engineer the parameter list. Unfortunately the ids/names used for those channels in the applet are in some cases not very helpful. That is where the name of the constants in the binding are coming from:
You can find a quite complete list here: https://loxwiki.atlassian.net/wiki/download/attachments/1529022643/3003.txt?version=1&modificationDate=1487708834000&cacheVersion=1&api=v2

[pelerner]

@sgiehl Contrary to your assumption in #11135 the v2.5 binding might also have been correct. So complementing the main documentation makes sense.

Could add the following channel docu ... e.g. ...

"Please note: Depending on brand and/or firmware version of your heatpump the channel 'temperatureHotWaterCoverage' has to be used for adjusting the hot water target temperatur instead of channel 'temperatureHotWaterTarget'. Channel 'temperatureHotWaterTarget' seems to be disfunctional on those models/firmwares. // Feedback welcome."

P

[sgiehl]

@pelerner would you mind updating the PR so it lists both channels, but mentions that one of both needs to be used, depending on the device? Guess there's not much more we can do without knowing where exactly the difference is with the heatpumps...

[lolodomo]

@pelerner : any chance you will finish this PR by considering last comment from @sgiehl ?

[pelerner]

@pelerner : any chance you will finish this PR by considering last comment from @sgiehl ?

I would like to do it ….

… but sorry I‘m not a github PRO user. Could you help, how to do it right …. ?

How can I change a file WITHIN this change request?
Or how can i RELATE a new file change to this change request?

P

[sgiehl]

@pelerner It seems you already removed the fork again where you did this changes propose from. So there won't be any possibility to update the files for this PR anymore. Guess the simplest solution would be to close this PR and open a new one with the adjusted changes.

[lolodomo]

Guess the simplest solution would be to close this PR and open a new one with the adjusted changes.

While there was only one work updated by this PR and while the PR is not building, yes I think the best is to close this PR and to create another one. Thank you.

[openhab-bot]

This pull request has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/migration-of-novelan-luxtronic-binding-to-openhab2/70743/139