Milesight · Single-phase current monitor
Milesight CT10x integration with EpiSensor Edge
CT101, CT103 and CT105 are self-powered, single-channel LoRaWAN current monitors. Choose by conductor size, rated current and the lowest current that must be reported, not by maximum amperage alone.
Connection design
Choose the path that matches the device
This is a protocol-compatible route, not a built-in Edge device mapping. Confirm the exact hardware generation, regional LoRaWAN parameters and network-server decoder. Hardware v2 energy values are estimates calculated from configured voltage and power factor; the CT does not measure either input.
For a new or existing private LoRaWAN network
LoRaWAN network-server route
- CT10x on one insulated conductor
- Compatible LoRaWAN gateway
- LoRaWAN network server and CT10x decoder
- Supported MQTT or HTTPS integration
- Gateway running Edge
Provision the device with the regional frequency plan and unique application credentials. Decode the vendor payload at the network-server layer, then map timestamped current, accumulated-current and status values into Edge without treating a missed uplink as a zero reading.
When another team already operates the gateway and network server
Existing LoRaWAN estate
- CT10x device identity
- Existing LoRaWAN coverage
- Network-server application output
- Authenticated IP handoff
- Edge data model
Agree ownership of keys, decoder revision, retries and timestamp semantics before integration. Edge needs the decoded application data and device identity; it does not replace the LoRaWAN network server.
Variant check
Match the exact model to its interface
Use the complete catalogue number, not the family name, when selecting an Edge connection.
| Models | Documented interface | EpiSensor route |
|---|---|---|
| CT101 · hardware v2 | 100 A rating · 16 mm aperture · minimum reported current 1.5 A at a 1-minute interval or 1.4 A at 10 minutes | LoRaWAN Class A through a network server; suited to the smallest conductors and lowest-current circuits in this family |
| CT103 · hardware v2 | 250 A rating · 16 mm aperture · minimum reported current 3 A at a 1-minute interval or 2.8 A at 10 minutes | Same LoRaWAN route; use the 250 A datasheet rating rather than treating configuration limits as a rating |
| CT105 · hardware v2 | 500 A rating · 36.5 mm aperture · minimum reported current 5 A at a 1-minute interval or 4.7 A at 10 minutes | Same LoRaWAN route; larger window and current range, with a higher self-power reporting threshold |
| Earlier hardware | Older manuals publish materially higher minimum reporting currents and a different feature set | Read the hardware and firmware versions from the device and use the matching Milesight documentation and decoder |
Data model
What Edge can exchange
The exact list depends on the model and its published data map. Start with the monitoring and control points the project will actually use.
- RMS current for the single monitored conductor, with minimum and maximum current records
- Accumulated current, documented by Milesight as ampere-hours; preserve the network receive timestamp and rollover behaviour
- Current threshold and over-current alarm states where enabled in the matching device generation
- Optional cable-temperature value and temperature alarm states when the external NTC probe is fitted
- Device, current-sensor and temperature-sensor status values from the matching decoder
- Hardware v2 estimated energy only when reporting type, nominal voltage and load power factor have been deliberately configured
- Hardware and firmware identity for selecting the correct decoder and interpreting generation-specific fields
- No inferred zero: an absent report, collection-failure sentinel or stale timestamp must remain missing or invalid
Site acceptance
Commission it once, then preserve the map
A successful network connection is the start of the check, not the end.
- Confirm CT101, CT103 or CT105, record the hardware and firmware versions, and select the matching base or v2 decoder before field mapping. Retain representative raw and decoded payloads because current manuals and decoder code differ in some optional wire types.
- Have a qualified installer isolate the circuit as required, clamp the CT around one insulated conductor only, and verify that the aperture closes fully.
- Check the expected lowest operating current against the model's reporting threshold at the chosen interval. A self-powered CT below that level may not produce a usable report.
- Provision the correct regional frequency plan, activation mode and unique LoRaWAN credentials; then verify uplink counters and timestamps at the network server.
- Compare live current with a suitable reference instrument at representative low and normal loads, and confirm sign, units, scaling and alarm semantics after decoding.
- If using hardware v2 energy reporting, document the configured nominal voltage and power factor as assumptions. Reconcile the result against a true energy meter before using it for decisions.
- If USB power is needed below the self-power threshold, confirm the approved accessory arrangement: the Type-C connection is also used by the optional NTC probe, and the reviewed documentation does not establish simultaneous USB power and temperature sensing.
- Test stale-data and sensor-failure handling by interrupting reports. Dashboards and alerts must distinguish missing telemetry from a measured zero.
- If temperature is required, confirm that the optional NTC probe is installed and validate its location and plausible reading; a codec field does not prove that a probe is fitted.
Design review
Useful strengths and real constraints
These judgements are scoped to integrating this device family into an energy-data system. They are not a generic product award or a substitute for project design.
- Open integrationStrong
- LoRaWAN and published vendor codecs support a standards-based network route. The integration still depends on a network server, the correct decoder generation and an authenticated IP handoff.
- Retrofit fitStrong
- Split-core installation and current-derived self-power can avoid a separate local supply, provided the conductor fits and normal load remains above the reporting threshold.
- Measurement scopeCurrent-led
- The primary measurement is current. Hardware v2 kWh is an estimate using configured voltage and power factor, not measured voltage, measured power factor or a revenue-grade energy value.
- Low-load visibilityDesign constraint
- Self-power thresholds vary by model, interval and hardware generation. Select against the lowest current that matters and retain stale or missing data explicitly.
- SecurityShared responsibility
- LoRaWAN provides device and application security mechanisms, while the project must protect unique keys, network-server accounts and the downstream MQTT or HTTPS integration.
- Evidence qualityRevision-sensitive
- Current product pages, older manuals and current decoder files differ in thresholds and some wire-format details. Keep the installed hardware identity, decoder revision and acceptance payload together.
Primary evidence
Sources
- CT10x LoRaWAN Smart Current TransformerMilesight
- CT10x configurable propertiesMilesight Development Platform
- Milesight IoT device release notesMilesight
- CT-series codec source at the reviewed revisionMilesight IoT
Reviewed by EpiSensor technical review on . Revision 1. Product names and trademarks belong to their respective owners; this guide does not imply endorsement or a commercial relationship.