Open Chris909090 opened 7 months ago
This looks strange. Would you mind uploading the diagnose information? This might be helpful to investigate the issue further.
Thanks for your help! :)
As you could see in my statistic it do some very strange things
I've written an programm that sends every 15 Minutes the value I needed, but you could see after some time it always set a wrong a value. config_entry-stiebel_eltron_isg-764cc24f291671eca917ffeb68f0149c.json.txt
Hello @pail23 I now have a new account so you have to knopw that I#m the same than Chris909090.
Do you have any further questions or some news?
The problem is that I have the same problem with the water temperature.
In this case the heating curve ios rise at 18:04:59 and just at the same time my comfort temperature for the water falls from the new to the old value. Maybe this could help you to find the error?
Thanks for your help!
Greetings :)
Hello Paul,
I am also experiencing the described problem of automatic parameter changes. We have a Stiebel Eltron WPE-I 06 HK 230 Premium brine heat pump in use and I have noticed several times that the parameters
stiebel_eltron_isg_comfort_temperature_target_hk1
stiebel_eltron_isg_comfort_water_temperature_target
stiebel_eltron_isg_eco_temperature_target_hk1
stiebel_eltron_isg_eco_water_temperature_target
change "by themselves".
We were recently on vacation for a few days and I had previously set the heat pump to "vacation mode". When the WPM returned to "program mode", the above parameters changed "by themselves".
from 23°C to 30°C
from 45°C to 60°C
from 23°C to 30°C
from 40°C to 60°C
It is noticeable that the values have been set to the maximum possible for the respective parameters - but perhaps the value is also a random one. Previously, the changed values were always as stated above.
What else has been noticed: The values are not only changed when switching to "program mode", but also when switching the integration off and on.
Perhaps this information will help to narrow down the problem or even solve it. I would be very pleased.
Many thanks Paul for your useful work. Best regards from Martin
Translated with DeepL.com (free version)
Guys, we've seen this behaviour recently on a couple of plants, not integrated into home assistant, so there might be a bug in the WPM. We are monitoring the situation.
@Martin73666 oh wow thanks for that great report. It is hopeful to see that I'm not the only one with this problem.
I can see that you have made a much deeper investigation than I have. @pail23 ,on the other hand, has the technical understanding. So it should be possible to send a report to Stiebel Eltron so that they can possibly fix this bug, right?
Now to your report: I have hidden the function that allows you to switch the integration on and off, as I felt it was causing unwanted behavior. To be honest, I don't know why you would ever want to switch it off.
I can see that you have made a much deeper investigation than I have. @pail23 ,on the other hand, has the technical understanding. So it should be possible to send a report to Stiebel Eltron so that they can possibly fix this bug, right?
We are investigating the subject.
Guys, we've seen this behaviour recently on a couple of plants, not integrated into home assistant, so there might be a bug in the WPM.
At first I thought the same thing, because the operating mode change was carried out by the WPM. But, since I noticed that the values are (also) changed when the HA integration is switched OFF/ON, I think that it is at least involved in the undesired behavior. Regards
I have added additional logging in the release 2024.2.1 for whenever the component writes values on the modbus. Please activate info level logging. The component writes "set modbus register for xxx to yyy" in the logfile.
@pail23 Sry fpór asking but how exactly do I have to set it?
# log level for STIEBEL ELTRON
homeassistant.stiebel_eltron: info
Please find the relevant documentation here.
Adding this to your configuration.yaml file should work:
logger:
default: debug
logs:
custom_components.stiebel_eltron_isg: info
if you use SG-Ready. The SG-Ready implementation may change the Heatcurve to reach the desired temperature
Version of the custom_component
2023.10.2
Describe the bug
Im using the integration in my dashboard. (Nowhere else) Now I made changes to "Eco Temperature Target HK1" (20 --> 21) and To "Heating Curve Rise HK1" (0,3 --> 0,4). Now I'm wating 10-120minutes and have another look at the values and now they changed without doing anything.
I doesn't matte if I made the change at Servicewelt or in HomeAssistant the value is correct in all instances but after a time between 10-120minutes is resets the values to the old values.
If I deactivate the Integration all works fine.
In the log on the right side I'm just sseeing this. Maybe further Informations could help to find the error.
I looking forward to hearing from you.
Thanks for all!
Greetings