I get my Kelvin accurate when the time changes and over the next six
months it drifts fifteen or so minutes fast! When the heat comes up
at five in March, I know I have fifteen minutes before the alarm goes off!
Pat, K9JAUAt 09:32 AM 11/18/2013, you wrote:
>Kevin,
>
>I went through a lot of gyrations to try to set the clock accurately until I
>realized that (1) the clock isn't all that accurate anyway, and (2) 30
>seconds one way or the other doesn't really matter in a thermostat. I have
>another brand of talking thermostat whose clock is much less accurate than
>the one you've got, so I just count myself lucky that the damned thing works
>at all.
>
>Steve
>
>----- Original Message -----
>From: "Kevin Minor" <[log in to unmask]>
>To: <[log in to unmask]>
>Sent: Monday, November 18, 2013 10:01
>Subject: OT: Is there a way to set accurate time on the VIP 3000 talking
>thermostat?
>
>
> > Hi.
> >
> >
> >
> > I know this isn't exactly ham radio related, but one thing I've learned
> > about a lot of hams, and I include myself in this group, is we like all
> > our
> > clocks to be accurate to the second. With that in mind, here's my
> > question.
> > I got the VIP 3000 talking thermostat, and it's working great, except for
> > one detail. I can't get the time to be as accurate as I'd like. I set
> > it,
> > but it was about 30 seconds fast. I called up Harry with Talking
> > Thermostats, and he told me that the clock on the thermostat can be off by
> > up to a minute either way, and there was no way to set it to the second.
> > I
> > can accept this, but I thought I'd ask other folks who have a talking
> > thermostat to see if you've mastered setting the clock on this thing? As
> > I
> > said before, I'm quite happy with how it's working, and if all that's
> > wrong
> > is the clock on it can't be set as accurately as I'd like, that's fine. I
> > just hope it stays where it is, not losing or gaining time quickly.
> >
> >
> >
> > Thanks in advance for help on this.
> >
> >
> >
> > 73
> >
> > Kevin Minor, Lexington, KY
> >
> > [log in to unmask]
> >
|