[OpenTRV-interest] First impressions and questions
Simon Hobson
linux at thehobsons.co.uk
Wed Jan 25 20:17:40 GMT 2017
Jason Pearce <jason at pearce.org.uk> wrote:
> I wasn't explicit enough - remote sensor - something like a stats hub being used wirelessly in sensor mode to send data to a (or more than one) local trvs in a room - stats hub at a convenient height/location - the box you sent with my stats hub is discreet enough - the trv in my bedroom was measuring around 22 celcius - it wasn't actually that hot in the room, so the trv sensor is being affected by the radiator.
Sounds simple enough :-)
Comes back to 2-way communications again, and the security & battery life issues that go with it.
I do recall there's been a small amount of discussion about that here in the past - might be worth searching the archives and see what's been said before.
I have a question for you on how the unit is performing.
I assume you have the one unit, and it's not currently connected to a boiler controller. Is it doing "sensible" things when there's a call for heating in the room, but the boiler isn't running ? I can't help wondering if it might be winding the valve fully open, saturating any integral term in the control algorithm, and perhaps then overheating the room when the boiler does fire up (due to timer & room stat calling for heat).
There's also issues with combi boilers (spit) which go off (as far as the heating is concerned) while people are having showers so even with a full Radbot system and boiler interface, there'll still be "demand but no heat supply" situations.
More information about the OpenTRV-interest
mailing list