Hi, I have another question.
I set up the VThermostat using my underlings and is fine, apparently.
I set up also scheduler component and scheduler card - which I used also last season - to set different preset at different times. However, I do not see the target temperature I set if I look into the thermostat.
The explananion I gave to mysef is becasue the thermostat used by VT is a virtual one, that just takes the temperature misured by the underling. Doesn’t send to the underlying the target temperature, but I can be wrong.
Additonally, if I open the window I see the thermostat in my room going to off, as expected.
I tried to read all inputs there, but I didn’t find any about couple temperature sensors.
Any advice which way I should go?
Here’s my setup of devices:
gas boiler for whole flat
4 rooms with the radiators
separate temperature sensors for each room (4x)
PLANNED: 4x Moes thermostat for each radiator (to have possibility to regulate temperature over each room, e.g. keeping lower temperature in the bedroom)
4x window sensors (grouped already into one binary entity)
Should I setup separate Versatile Thermostat for each room?
I didn’t find option to add more than 1 internal temperature sensor.
You should have one VTherm per heating zone. A heating zone is defined by one temp sensor, one window sensor and at least one heater. A zone is basically a room.
If you have many temp sensor or window sensor you can group it by zone and give the group to the configuration of VTherm. You can also create a template sensor to combine them with the helpers.
At first a big thanks to the dev of this integration for this great job
At this time I play around with on versatile thermostat and have a couple ideas how I will integrate this virtual thermostat in my project.
After looking a little deeper in the generated entities, I have a couple of questions:
The “xxxx_energy” entity, is that the total consumption over the total runtime of the thermostat? If yes, I wonder why it shows different values as the power entity of the used smart plug for the time I played around…?
The “xxx_mean_power_cycle”, how is this entity to be understood and how exactly does this value come about?
Oh yes, now that I’m reading your explanation, the penny drops
I remember now that I was asked about the device power during configuration… and I entered the power from the device label, which of course never matches the real power to 100%.
Yes, that’s right, my thermostat runs as “over switch”.
OK, now I understand. So it’s a calculated value from the entered device power and the “switch-on percentage” multiplier that results from the TPI !?
I have now set up VTherm on yet another radiator, and I have seen some strange behavior with its reaction. I am currently on Light self-regulation in a VTherm over Climate Setup.
What’s a little odd is that before the current temp of the VTherm even hit the external target temperature, it increased the target temperature of the underlying TRV, causing heating and later on an ever higher offset from the target. Shouldn’t both k_i and k_p work the other way in this case? The accumulated error should be high, and the proportional error should also be >0.
Before I start messing around with TPI-parameters, I wanted to check if someone could give me feedback on how to handle this best.
Please follow the instruction in the README before trying to tweak the parameters of the PI algo (this is not TPI if you are in over_climate with light self-regulation).
I have tried medium before, it was pretty much the same picture. My problem is that I think VTherm is heating way too often. The problem got even worse with stronger self-regulation. I also have the Use internal temperature of the underlying enabled.
I have now disabled the option to use internal temp of the underlying, situation has massively improved. I went to strong self regulation, looking good for so far, the setpoints for the underlying TRVs now make sense. I’ll keep watching how it behaves for now.
Glad to here it is working now. The option “use internal temp” is to be used only if all others self regulation have failed. Sometimes the internal temp is so bad that it is worst with it.
So I started using VTherm a couple of days ago with my Sonoff TRVZB, and it works quite well. I’m using over_climate with self-regulation and it’s able to open my TRV gradually, not just on/off as the default behaviour.
Now, I only have one problem. Manual control doesn’t work at all - meaning whatever I set manually on the TRV, I don’t see it in VTherm. It just ignores it and only takes into account the temperature I set in VTherm.
My preset is always set to Manual by the way. Is this how it’s supposed to work?
Edit: figured it out myself - you need to check ‘Follow underlaying temperature change’
Sorry guys, I hope you can help me or point me in the right direction, but I don’t even know if this is the right thread to ask. Asked in other thread but it seems my problem is quite unique.
Using KNX with all the “intelligence” and logic in EiBPort. My goal is the port it to HA.
What I’d like to control is an additional heading system to my heating pump. This additional system consists of an ordinary actor with 2 addresses. One opening the valve the other closing the valve. Additionally a outside temperature and an actual flow temperature and on a heating curve calculated flow temperature and a water pump. Consequently all the intelligence must be in HA, respecify in unter climate in configuration.yaml.
The features what I’m looking for, besides the smooth and controlled adjustment of the valve, are:
max. flow temp. 35 degrees
door open = closes the valve and stops the pump
outside temp < 20 degree closes the valve and stops the pump
modes: away, eco, normal
Is this even possible to realize? If possible, could someone please guide me / point me in the right direction. As indicated … I’m “just” beginning with HA …
Thank you
Thanks for trying to help, but if you are (like me) not deep into coding it’s almost impossible to realize. This is the level I’m coming from Startseite - LOGIKEDITOR NETWORK
It will be long way to HA … f
