-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Target temperature for TRV (used for underfloor heating) never hit #863
Comments
Hello, All your temperature are set to 7°:
how it can just work ? Or maybe you don't use the preset but only the "manual" mode (no preset) ? Ok let assume this. In Here we have:
This mean that VTherm set the setpoint to 32.5° (!!) and this is still not enough. This is very high value is due to the expert mode with some very strong parameters. If yes, this means this is still not enough I guess there is nothing to do and it means your underfloor heating is not sufficient. Maybe you should increase the water temperature (if you can do that). |
Apologies I was not clear on this. Yes, this is what I am doing as I typically use something like Schedy to change temperatures for the entire house and keep that config in one place. For now however, I am just using manual mode as you say.
Yup, that is what is happening. Below is a graph of the set point on that device, along with temperature (mean) reported by both thermometers in the room. What this tells me is that a) when the the setpoint is at 32.5 degrees and the underfloor heater is enabled, the room heat does start climbing as expected.
Sadly in this room, the underfloor heating is electric and I've always had issues with it. However, I replaced the controller recently with a Zigbee one and have been able to get the room way above the target (22 degrees or so), but sadly the sensors for air temp and underfloor temp are not working (which explains why the previous unit does not work). So there is no way to provide more heat as such without setting the target temperature higher and maintaining that temperature for longer. My question therefore is:
I just wanted to just add, thank you @jmcollin78 for this integration and your support. Hugely appreciated 🙏 |
There is a misunderstanding here: VTherm doesn't stop the heating but it just send a setpoint to the underlying climate. And the underlying climate device, stops by its own.
This is totally useless I think. If you could set 80°, it won't heat more because the device is not enough strong. It is not a matter of temperature setpoint but a matter of power of heating (if my understanding is good of course).
The "Use Internal Temperature" don't sent calibration to the device but add the compensation factor to the setpoint sent to the device. It has the same effect. In your case, this parameter will be useless also due to the insufficient heating power. The only configuration which allow sending the calibration is to use the |
Version of the custom_component
7.1.4
Configuration
My VTherm attributes are the following:
Note my expert settings are as follows:
If it is releveant to regulation performance or optimisation some curves are needed
Describe the bug
I have set up a versatile thermostat for an underlying electric underfloor heating TRV, a Moes BHT-002-GCLZB. The target temperature is never reached by quite a few degrees, and it's just not evident, even after going to an extreme setting for the regulation, what is causing the versatile thermostat to hold off on keeping the underlying heating on until the target temp is reached
I'm trying to:
Reach a target temperature for my room, using my underfloor heating TRV, and an external Zigbee thermometer to ensure I have an accurate room temperature reading (unaffected by the device heat etc).
And I expect:
The target temperature of 23 degrees to be reached within an hour or two, as I know I can heat up the room this quickly when setting the temp manually.
But I observe this ....
It's been on for most of the day and the temperature is oscillating at around 20 degrees.
I read the documentation on the README.md file and I don't find any relevant information about this issue.
Debug log
The text was updated successfully, but these errors were encountered: