[OpenTRV-interest] Adaptive comfort

Marko Cosic marko at coheat.co.uk
Wed Jul 13 09:31:50 BST 2016

Nest is a business built on (1) shiny and (2) creating setpoint schedules
based on nudges up and down.

They've managed it for people who run like clockwork but are too
lazy/stupid to set a clock.

It fails hard if there's the slightest variability in lifestyle or comfort
criteria though.

Hard problem. Luckily (1) shiny is most important.

More codified fudge factors based on weather (cloud cover for solar gain,
windspeed for draughts) to influence actual setpoint vs perceived setpoint;
and ramp rate/setpoint influence that depends whether you're heating up to
a setpoint from sleep mode/out mode/or as a bake/freeze request; sound more
promising to me.
On 13 Jul 2016 10:36 a.m., "Damon Hart-Davis" <dhd at exnet.com> wrote:

> Hi,
> A very interesting thread thank you.
> > On 12 Jul 2016, at 16:15, Lisa Ann Pasquale <
> lisa.pasquale at six-cylinder.co.uk> wrote:
> >
> > Humidity is a metric which is more relevant for controlling ventilation
> than heating. When the humidity rises, you need to ventilate to remove the
> moisture. Increasing the temperature only disperses it and adjusts the
> dewpoint - it doesn't remove the moisture, which is a risk of condensation
> and mould problems within the home - regardless of comfort. Tweaking the
> temperature is unlikely to alleviate discomfort caused by high or low
> humidity levels as efficiently or effectively as ventilation.
> The only effect humidity has on our temperature setpoint currently is to
> raise the frost protection temperature if RH is high to try to prevent
> condensation.
> We could provide more subtle tweaks to the set point (principally I’d be
> interested in opportunities to turn down the set point to save energy if
> the user wouldn’t notice), but I suspect that they’d be lost in the noise.
> Note that the rather nice humidity and temperature sensor that we use
> (SHT21) is more expensive than and larger than and has tougher power supply
> requirements the temperature-only device that we otherwise use (TMP112).
> There is a significant cost implication of using RH (maybe even a fiver at
> retail) so it needs to pay its way.
> > There's been some good research on fuzzy logic controls, in the past,
> which most closely relates to how we control our comfort from an adaptive
> comfort perspective. One of the main tenants of adaptive comfort is that we
> 'adapt' when we feel DIScomfort. It's not a means of maintaining comfort so
> much as a means of continually eliminating discomfort. Might sound like two
> sides of the same coin, but the distinction is actually very important in
> control logics. Some fuzzy logic controllers even take into account the
> likelihood of window opening, as it may relate to outdoor noise levels, etc.
> >
> > personally, I'd be very interested to see a controller which allows
> people to adjust the thermostat based on "I'm too hot", "I'm too cold"
> commands to boost temperatures for short periods of time. That way, when an
> individual might be wearing heavier clothes than normal (like, when I'm
> cooking in a hoodie), I can just tell the controller "I'm too hot" and it
> adjusts the temperature accordingly. Or when I'm walking around barefoot
> (for whatever reason), I can say "I'm too cold" and the temperature bumps
> up for an hour or two. That responds to my immediate needs for comfort, and
> also gives me a chance to either peel off a layer, or put on some slippers
> once the discomfort has been alleviated (which, again is "adaptive"...).
> Our ‘bake’/‘boost’ mode is intended to be a “I’m too cold” or “make me
> warm” temporary override.
> > The learning/programming part would need to consider how often someone
> calls out they're too hot or too cold at specific times of day, and at give
> set points. It would need to learn a safe "base" behaviour, and then be
> able to identify 'outlier" requests which can be excluded from being
> averaged into the base behaviour.
> Yes, indeed.  I’m keen on the ‘median filtering’ type of approach.  We
> already apply filtering to some stats records.
> Thank you.
> Rgds
> Damon
> _______________________________________________
> OpenTRV-interest mailing list
> OpenTRV-interest at lists.opentrv.org.uk
> http://lists.opentrv.org.uk/listinfo/opentrv-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opentrv.org.uk/pipermail/opentrv-interest/attachments/20160713/ad16289e/attachment.html>

More information about the OpenTRV-interest mailing list