I am only a week or so in to my Evohome system, and this morning noticed that the readings from the two radiators in a multi-room zone were reading significantly higher than the controller was reporting. Because I've also written a script to collect data via the API I could see from the trend that the reported temperature "froze" from about midnight last night. I ran the RF comms check, and both valves reported a signal strength of 5, but the controller said one of the actuators was failing to respond.
I ended up deleting the zone, clearing the binding on the valves, and then and re-creating the zone. Both valves re-bound correctly and the controller now seems to be reporting correctly too. I wondered if there was a reason for the initial failure, and whether there is an easier way to 'reset' the communications if this happens. It wasn't a long job to fix, but it was a bit of a pain having to re-create the schedule for the re-created zone! There was nothing in the fault log on the controller to indicate that there had been a problem.
I must admit, the ability to trend has been fantastic as I've spotted a glitch in the configuration of another HR92, and it's also proving really useful insights in to how the rooms, and the system, are behaving.
I ended up deleting the zone, clearing the binding on the valves, and then and re-creating the zone. Both valves re-bound correctly and the controller now seems to be reporting correctly too. I wondered if there was a reason for the initial failure, and whether there is an easier way to 'reset' the communications if this happens. It wasn't a long job to fix, but it was a bit of a pain having to re-create the schedule for the re-created zone! There was nothing in the fault log on the controller to indicate that there had been a problem.
I must admit, the ability to trend has been fantastic as I've spotted a glitch in the configuration of another HR92, and it's also proving really useful insights in to how the rooms, and the system, are behaving.