Recent searches
Search options
@jrconlin no, honestly it's funny to me that you think this is good?
Hold should be a single thing that works a single way. You turn on hold and now it is a dumb thermostat until you turn hold off.
This scheme is needlessly complicated and opaque.
Honestly, nest had it right in that a temporary override would always stay until the next schedule point. The way ecobee is doing it is maddening. I'd like to see a combination of nest's temporary override and permanent hold. That seems obvious.
@TechConnectify @jrconlin The Ecobee is literally the first thermostats I’ve ever owned (Grew up in Europe where each radiator has a manual dial you turn to decide how warm it gets) - So I have no bagge or context here, seriously.
To me the “hold for X duration” seems like a helpful feature. Some evenings the preset doesn’t quite hit the mark, and we want to turn it up for a bit. But I don’t want to have to remember to disable that fact as I go to bed.
@TechConnectify @jrconlin I guess what I don’t quite understand is: Are you saying you can’t imagine a scenario where this is useful? Or are you saying there’s a clearer way to communicate the requirement I just suggested?
@philip @jrconlin a little of both, actually. I don't see that as particularly useful because I run a program already, and I would expect it to maintain my temporary override until the next programming point. And that program point happens to change at bedtime.
But, I see its usefulness - the other problem, though, is folding "just stop being smart until I tell you to be smart again" into the same action.
*That* is what should be pulled out as its own function.
@philip @jrconlin basically, I want a toggleable action to turn its brain off and make it a dumb thermostat. That is what "Hold" does on pretty much every programmable thermostat ever. It is distinctly different from a temporary override because it is a *permanent* override.
I find it needlessly confusing to fold that into a subset of overrides. While I can appreciate having various time spans for the overrides, they are all still temporary and thus, to me, are not what "hold" even does.
@TechConnectify @jrconlin I’m not sure what a better word would be, but I will definitely concede that “Temporary hold” probably isn’t the best choice.
As a software developer by trade, it fits fine in my mental model, but I can see how it wouldn’t for other folks.
@philip @jrconlin Right. I guess, maybe some of this has to do with the people in charge of smart thermostats not having much experience with dumb-but-programmable thermostats.
I mean, Nest doesn't even let you make it be dumb. That alone is crazy to me - what do you do when you have a house sitter?
But bottom line, it's too much. My paradigm is "run the program" and "don't run the program" with "deviate from the program until the next set point" being the only necessary mid-point.
@philip @jrconlin and that is how every programmable-but-not-smart thermostat I have used works.
And I think it's very logical. Either you want to be running the program, or you don't want to be running the program. And if for some reason you want to deviate from it right now, you probably want it to resume the program so you don't forget to put it back on.
And if you don't want it to do that? You turn on hold. And now it's a dumb thermostat.
Other options seem contrived, honestly.