Balancing EvoHome zone with multiple HR92s

[jonstatt]

One more "technical" question: why two HR92s with the same parameters should read different opening %? How EvoHome could decide to open one valve more than the other?

This comes back to what I said before. "IF" there is some kind of auto-sensing going on during the "CYCL" phase when you first add the HR92, then that would explain the different percentages. It almost certainly is nothing to do with the EVOHOME controller at all.....much more likely the individual HR92 making that decision. However, I would try an absolutely clean zone

1) Delete the zone
2) Make sure the HR92s are back to defaults
3) Remove both HR92s and swap them over between the two radiators. This will force a new CYCL phase and also rule out an oddly behaving HR92 (if the problem moves with it)
4) Re-add the zone

[emmeesse68]

... However, I would try an absolutely clean zone

Don't get me wrong, I know that could solve but being in IT management since 90's I'm used to the "reboot/reinstall" approach. They can be helpful in short, but issues use to come back sooner or later, until you actually understand why they appear and solve them.

Now I noticed an evolution in my valves behaviour. I can't explain that since I don't know how they work and how the learning phase is carried out (what part depends on the controller and what is carried out by the HR92 themselves, or even the remote thermostat used as a sensor), so basically I don't know if the system is not settled yet. Moving things around could prevent completion of such a learning phase - if it ever ends...

Now I'm trying something that I didn't check before: letting the zone alone for a few days, taking some notes (e.g. measured temperature, valve position, rad behaviour). Too bad I can't just download a log from the system...

Meanwhile, I'll throw in a few more "technical" questions:

- in a zone with multiple HR92s (single zone), there's one official temperature sensor only (one valve or a separate wireless thermostat). Is the temperature sensor of "actuator-only" HR92s used to "learn" or anything else? Is it reported to the central controller (and, via web gateway, to the TCC infrastructure) anyhow?

- in such a zone fitted with multiple HR92s, how does the open window detection work? Is it based on the zone sensor (one of the valves or the added thermostat) or is it carried out by each valve independently, or by any of the valves? Is the thermostat to be configured anyhow (DTS92 seem to have a related option)?

[jonstatt]

Don't get me wrong, I know that could solve but being in IT management since 90's I'm used to the "reboot/reinstall" approach. They can be helpful in short, but issues use to come back sooner or later, until you actually understand why they appear and solve them.

Now I noticed an evolution in my valves behaviour. I can't explain that since I don't know how they work and how the learning phase is carried out (what part depends on the controller and what is carried out by the HR92 themselves, or even the remote thermostat used as a sensor), so basically I don't know if the system is not settled yet. Moving things around could prevent completion of such a learning phase - if it ever ends...

Now I'm trying something that I didn't check before: letting the zone alone for a few days, taking some notes (e.g. measured temperature, valve position, rad behaviour). Too bad I can't just download a log from the system...

Meanwhile, I'll throw in a few more "technical" questions:

- in a zone with multiple HR92s (single zone), there's one official temperature sensor only (one valve or a separate wireless thermostat). Is the temperature sensor of "actuator-only" HR92s used to "learn" or anything else? Is it reported to the central controller (and, via web gateway, to the TCC infrastructure) anyhow?

- in such a zone fitted with multiple HR92s, how does the open window detection work? Is it based on the zone sensor (one of the valves or the added thermostat) or is it carried out by each valve independently, or by any of the valves? Is the thermostat to be configured anyhow (DTS92 seem to have a related option)?

I am in IT support management and believe me I would slap any engineers that give the "reboot", "restart" comment without qualification. I remember getting very very annoyed on a call centre once when I told them that smoke had poured out of the back of a device, to which they said, have you tried doing a factory reset on it?! That's why I built-in a little extra with what I suggested to you which was to swap the two HR92s over to see if the problem moves with the HR92, or it behaves exactly the same

[emmeesse68]

That's why I built-in a little extra with what I suggested to you which was to swap the two HR92s over to see if the problem moves with the HR92, or it behaves exactly the same

I appreciate your suggestion, it's a valuable advice and I think Ill actually try it at some point. Only, I don't want to miss out the possibility that it could just be a matter of time to let everything "learn" my room...

[Rameses]

Don't get me wrong, I know that could solve but being in IT management since 90's I'm used to the "reboot/reinstall" approach. They can be helpful in short, but issues use to come back sooner or later, until you actually understand why they appear and solve them.

Now I noticed an evolution in my valves behaviour. I can't explain that since I don't know how they work and how the learning phase is carried out (what part depends on the controller and what is carried out by the HR92 themselves, or even the remote thermostat used as a sensor), so basically I don't know if the system is not settled yet. Moving things around could prevent completion of such a learning phase - if it ever ends...

Now I'm trying something that I didn't check before: letting the zone alone for a few days, taking some notes (e.g. measured temperature, valve position, rad behaviour). Too bad I can't just download a log from the system...

Meanwhile, I'll throw in a few more "technical" questions:

- in a zone with multiple HR92s (single zone), there's one official temperature sensor only (one valve or a separate wireless thermostat). Is the temperature sensor of "actuator-only" HR92s used to "learn" or anything else? Is it reported to the central controller (and, via web gateway, to the TCC infrastructure) anyhow?

- in such a zone fitted with multiple HR92s, how does the open window detection work? Is it based on the zone sensor (one of the valves or the added thermostat) or is it carried out by each valve independently, or by any of the valves? Is the thermostat to be configured anyhow (DTS92 seem to have a related option)?

- The other 'sensor' is 'muted' and not considered in the learning (in a single room config), but the unit will be still 'aware' of its surroundings. Eg if you had (like I do) a Hr92 that was under a radiator cover, and then moved the cover, and nominated it as the primary, dont expect it to behave immediately as per the other unit - it will have climatise, as it was aware of a differ behavior area before.
- It works the same as it's using the nominated 'sensor' to determine the draft/window/open door etc