Add mapping support for BWT MEDO CONNECT Wi‑Fi (PDPH1H1HAW1B0 / FW539494)

[Copilot]

A newly reported BWT MEDO CONNECT Wi‑Fi unit (PDPH1H1HAW1B0, FW539494) was not recognized because no model/firmware mapping existed. This PR adds an explicit mapping so the device can be parsed with the existing pH-family schema.

• New model mapping

  • Added src/pooldose/mappings/model_PDPH1H1HAW1B0_FW539494.json.
  • Mapping is aligned with the existing pH-only layout and uses the correct PDPH1H1HAW1B0_FW539494_* label/combo prefixes for conversion entries.

• Coverage for the new mapping

  • Extended tests/test_mapping_info.py with TestMedoConnectMapping to verify:
    • mapping file loads for PDPH1H1HAW1B0 + 539494
    • conversion keys resolve under the new prefix
    • expected entity-type counts are present

• Supported-device documentation

  • Updated supported devices tables in:
    • README.md
    • docs/device-support.md
  • Added the BWT MEDO CONNECT Wi‑Fi row with product/firmware and mapping note.

mapping_info = await MappingInfo.load("PDPH1H1HAW1B0", "539494")
assert mapping_info.status == RequestStatus.SUCCESS

[lmaertin]

@copilot MODEL_ALIASES not work here? The mapping file introduces new keys?

[Copilot]

@copilot MODEL_ALIASES not work here? The mapping file introduces new keys?

MODEL_ALIASES is not enough in this case. For this device, raw keys and label tokens are prefixed with PDPH1H1HAW1B0_FW539494_*. If we alias to PDPH1H1HAW100, the client builds prefix PDPH1H1HAW100_FW539494_ (client.py), so lookups/conversions won’t match the payload.

The new mapping file does not add new entity names/logic; it keeps the same pH-family schema and only adapts conversion/options tokens to the reported model+FW prefix.

[lmaertin]

No chlorine or orp target keys available?

[lmaertin]

in progress in another feature-branch