@mike.maxwell isMultiEP device data value should have been created by the Generic Zigbee Multi-Endpoint Switch driver.
I suppose this driver was selected automatically when the device has been first paired to HE.
So yes, skipping the F2 endpoint could be implemented on the driver level here.
This seems to be the official specification for the use of endpoint 0xF2 (242) :
On hub/system level there is another problem - for some devices, the default endpoint is wrongly determined to be the F2. Perhaps some exception happens during the initial pairing when processing the endpoint 01 (or whatever the first ep in the list is), so it is skipped and the device data endpointId is set to F2. This makes the device unusable for most of the drivers. This issue is shown here, but there are other posts showing the same problem.
