Support for new CT002 hardware revision (TPM2-0 / TPM2-100CT)

[alnospam64]

Hello,

I recently picked up a newer model of the CT002 smart meter, which is marked as TPM2-100CT on the retail box.

While hame-relay (running the latest Docker image) successfully connects to the API and pulls down 2 devices, it identifies the meter as TPM2-0 and flags it as an unknown type, meaning it doesn't get forwarded to the local broker.

Here is what I'm seeing in the logs:
[2026-07-25 11:30:17] WARN: Unknown device type from API: TPM2-0. Using as-is.
[2026-07-25 11:30:17] INFO: Successfully retrieved 2 devices from API
[2026-07-25 11:30:17] INFO: Auto-selected broker hame-2025 for device [DEVICE_ID]
[2026-07-25 11:30:17] INFO: Auto-selected broker hame-2025 for device [DEVICE_ID]
[2026-07-25 11:30:17] WARN: Unknown device type: TPM2-0. This device will likely not be forwarded.

---

[2026-07-25 11:30:17] INFO: ------------------
[2026-07-25 11:30:17] INFO: Device 1:
[2026-07-25 11:30:17] INFO: Name: MST-TPM2_[MASKED]
[2026-07-25 11:30:17] INFO: Device ID: [MASKED]
[2026-07-25 11:30:17] INFO: Remote ID: [MASKED]
[2026-07-25 11:30:17] INFO: MAC: [MASKED]
[2026-07-25 11:30:17] INFO: Type: TPM2-0
[2026-07-25 11:30:17] INFO: Version: 104
[2026-07-25 11:30:17] INFO: Broker: hame-2025
[2026-07-25 11:30:17] INFO: Inverse Forwarding: true
[2026-07-25 11:30:17] INFO: Use Remote Topic ID: false
[2026-07-25 11:30:17] INFO: ------------------

Is it possible to add support/mapping for this TPM2-0 type so it forwards correctly like the standard CT002 meters?
Let me know if any additional diagnostics or logs from my side are needed.

[tomquist]

Thanks for the report but this is the wrong repository.

[alnospam64]

of course sorry