"_zone_unknown" for 1 TRV in a multi TRV zone

Hi there,

One of my EvoHome zones has 2 TRVs in it.

Messages about one of the TRVs correctly identify the zone e.g.

evohome/evogateway/rear_living/trv_04:022963/heat_demand
evohome/evogateway/rear_living/trv_04:022963/temperature

Yet for the other TRV, some messages correctly identify the zone, but some have the zone set as _zone_unknown:

evohome/evogateway/rear_living/trv_04:020517/heat_demand
evohome/evogateway/_zone_unknown/trv_04:020517/temperature

Furthermore, if I look in to the schema definition there's no reference of the TRV which has the _zone_unknown messages:

"02": {
      "_name": "Rear Living",
      "actuators": [
        "04:022963"
      ],
      "class": "radiator_valve",
      "sensor": "04:022963"
    }

If I compare this to another multi TRV zone (which doesn't suffer from the above issue) I can see that both TRVs are registered as actuators in the zone with no issues:

"07": {
      "_name": "Master Bed",
      "actuators": [
        "04:020489",
        "04:037125"
      ],
      "class": "radiator_valve",
      "sensor": "04:037125"
    }

I'm running v3.11-0.22.40, which I think is the latest version?

I've tried restarting evoGateway, but this doesn't seem to have any effect.

FWIW I'm running in eavesdropping mode, I know that not the recommended mode but I'm yet to get around to creating a device allowlist. That said, I think eavesdropping mode is probably the most useful mode for figuring out this problem?

Very grateful if you have any ideas for things I could try!

smar000 / evoGateway

"_zone_unknown" for 1 TRV in a multi TRV zone #64