Setpoint sync issues
Posted: Thu Jan 11, 2018 1:25 pm
Hi,
We just had Evohome installed yesterday, and so far it's really not working properly.
If I change the setpoint on an HR92, it works fine. I can hear the valve open/close immediately, and the override temperature shows up on the controller in a few seconds. In the other direction, however, any setpoint change made by the controller takes ages to show up on the HR92s - anything from 15 minutes to an hour seems to be common so far, and even multiple hours at one point. This applies whether it's setting a new override, cancelling a previous override, or even a scheduled change.
I'm also seeing a weird problem whereby the currently-scheduled temperature shows up as an override, with a seemingly random end time. This is frustrating because it often continues past the next scheduled change. This definitely isn't something anyone's done - I've disabled manual control of the HR92s, nobody but me yet has access to the controller, and I haven't set up any IFTTT etc integration yet.
Finally, in case it's relevant, that disabling of manual control I mentioned took forever to take effect - I disabled them at 1pm yesterday, and it took until about 9pm to take effect on the first HR92, and only three of seven were done by midnight, though they were all done by the time I got up this morning.
I've run an RF check on all the TRVs and they all show as excellent / strength 5 - no surprise, it's a small house and the controller is centrally located. In any case, the problems still occur with the HR92 that's a metre away from the controller.
No issues with the BDR91s - as far as I can tell, they're calling for heat at exactly when I'd expect them to be (and separately, no double binding issue there). Well, I mean the heating one is obviously coming on late, but in sync with when the HR92s get updated.
My installer said that I need to give it time to bed in, but that doesn't ring true to me - I totally understand it's got a learning period to go through, but I'd expect that to be related to what the controller actually decides, rather than the controller actually becoming capable of controlling - right?
We just had Evohome installed yesterday, and so far it's really not working properly.
If I change the setpoint on an HR92, it works fine. I can hear the valve open/close immediately, and the override temperature shows up on the controller in a few seconds. In the other direction, however, any setpoint change made by the controller takes ages to show up on the HR92s - anything from 15 minutes to an hour seems to be common so far, and even multiple hours at one point. This applies whether it's setting a new override, cancelling a previous override, or even a scheduled change.
I'm also seeing a weird problem whereby the currently-scheduled temperature shows up as an override, with a seemingly random end time. This is frustrating because it often continues past the next scheduled change. This definitely isn't something anyone's done - I've disabled manual control of the HR92s, nobody but me yet has access to the controller, and I haven't set up any IFTTT etc integration yet.
Finally, in case it's relevant, that disabling of manual control I mentioned took forever to take effect - I disabled them at 1pm yesterday, and it took until about 9pm to take effect on the first HR92, and only three of seven were done by midnight, though they were all done by the time I got up this morning.
I've run an RF check on all the TRVs and they all show as excellent / strength 5 - no surprise, it's a small house and the controller is centrally located. In any case, the problems still occur with the HR92 that's a metre away from the controller.
No issues with the BDR91s - as far as I can tell, they're calling for heat at exactly when I'd expect them to be (and separately, no double binding issue there). Well, I mean the heating one is obviously coming on late, but in sync with when the HR92s get updated.
My installer said that I need to give it time to bed in, but that doesn't ring true to me - I totally understand it's got a learning period to go through, but I'd expect that to be related to what the controller actually decides, rather than the controller actually becoming capable of controlling - right?