Which probes, sensors, and switches the InteliHive supports, and from which firmware version. Check here before quoting a device to a customer. For how each kind of instrument works, and each model’s electrical interface and ratings, see Instrumentation.
How to read this page. Since is the first firmware release that includes the device. If a device is listed as Unreleased, the support exists in development firmware but is not yet in a release you can install — do not promise it to a customer without checking with engineering.
Current release: v0.1.0 (14 September 2026).
Wired to the controller’s RS-485 bus. Port powered is the default answer the controller suggests when you add the device — see Port powered or externally powered.
| Device | Type | Channels | Default address | Port powered | Since | Status |
|---|---|---|---|---|---|---|
| Sensorex Smart Sensor | Water-quality probe | See below | 240 | Yes | v0.0.1 | ✅ Supported |
| Pyxis ST-712 | pH and ORP probe | pH, ORP (mV), temperature (°C) | 13 | Yes | v0.0.1 | ✅ Supported |
| Pyxis ST-710 | pH probe | pH, temperature (°C) | 11 | Yes | — | ⚠️ Unreleased — development builds only |
| Pyxis ST-500 | PTSA and turbidity probe | PTSA (ppb), turbidity (NTU), cleanliness | 10 | Yes | v0.0.1 | ✅ Supported |
| Pyxis CR-300 | Corrosion rate probe | General corrosion (mpy), localized corrosion (index), temperature (°C) | 23 | Yes | — | ⚠️ Unreleased — development builds only |
| Pyxis LS-200, LS-202 | Tank level probe | Level, distance, volume remaining, volume used | 66 | Yes | — | ⚠️ Unreleased — development builds only |
| Legacy Relay Device 6 | Relays | 6 relays, each readable and switchable | 32 | Yes | v0.0.1 | ✅ Supported |
| NextStep Pump | Dosing pump | Pump on/off, dosing rate, speed (%), total dosed, operating mode, alarms | 1 | No | v0.0.1 | ✅ Supported |
NextStep Pump. A Pulsafeeder chemical metering pump — see Upgrading the NextStep Firmware for its own firmware. Reports its dosing rate and total in liters or gallons, following the pump’s own unit setting. The pump’s alarms — tank level, overflow, no input, temperature, pressure — appear as controller alarms in the 330s. It has its own supply and reports no serial number, so the controller checks only its type.
Pyxis probes. What each shows on the controller, and its own settings — the ST-500’s cleanliness check, the CR-300’s metal, the LS-200/202’s tank — are on Modbus Probes. Development firmware adds, for every Pyxis probe here, calibration from the controller (see Calibration) and moving its address from the controller (see Moving a probe to a new address). It also fixes how the ST-500 and ST-712 readings are decoded — see Modbus Register Map. The Pyxis LS-200 and LS-202 share an address and are added from one row; the controller tells them apart by product number.
Legacy Relay Device 6. A Modbus-controlled board with six relays, on the RS-485 bus. Each relay can be named and driven by its own control mode. Leave it port powered so a relay switched on by hand can always be forced off — see Modbus RTU devices.
The Sensorex Smart Sensor family shares one register map across variants: the measured value, temperature, and an alternate reading. The controller resolves which variant is attached from the probe’s firmware-version register, so units are never guessed.
| Probe | Measures | Also reports | Since | Status |
|---|---|---|---|---|
| Sensorex pH | pH | Temperature (°C), mV | v0.0.1 | ✅ Supported — calibration from the controller in development builds |
| Sensorex Conductivity (CP2) | Conductivity (µS/cm) | Temperature (°C), PPT | v0.0.1 | ✅ Supported |
Channels stay invalid until the variant is identified. A probe cannot report another variant’s units, so a misidentified probe reads as unavailable rather than as a plausible wrong number.
The Sensorex datasheet also defines ORP, dissolved oxygen, free chlorine, and toroidal conductivity variants. These are not supported — each needs its unit semantics productized before it can be enabled. Ask engineering before quoting one.
Point-to-point digital sensors, one per port, powered by the controller. The controller reads each device’s identity on connection and applies a stored profile, so readings arrive already named, scaled, and in the right units.
Profiles are keyed by the device’s identity, and one profile covers a whole product family. That is why the table lists several model numbers per row: they are electrically and digitally interchangeable as far as the controller is concerned.
| Models | Measures | Range | Also reports | Since | Status |
|---|---|---|---|---|---|
| ifm UGT203, UGT509 | Distance | 150–1600 mm | 2 switch outputs, device status | v0.0.8 | ✅ Supported |
| ifm UGT207, UGT513 | Distance | 200–2200 mm | 1 switch output, device status | v0.0.8 | ✅ Supported |
| Keyence FR-L | Radar level | mm | Flow conversion, 5 outputs, stability, detailed error bits | v0.0.8 | ✅ Supported |
| Keyence FR-S01 | Radar level, short range | mm | Accumulated level value, 5 outputs, stability, detailed error bits | v0.0.9 | ✅ Supported |
Distance sensors can be used as tank gauges. Give the controller the tank height and the sensor’s mounting offset and it converts the measured distance to a liquid level, so control modes work in level rather than in distance-from-lid.
| Models | Measures | Range | Also reports | Since | Status |
|---|---|---|---|---|---|
| ifm PV7604 | Pressure | −1 to 10 bar | 2 switch outputs | v0.0.8 | ✅ Supported |
| Keyence GP-M001T, GP-M010T, GP-M025T, GP-M100T, GP-M250T, GP-M400T | Pressure | Per model | Temperature, 2 outputs, over/under-limit and system error bits | v0.0.8 | ✅ Supported |
| Models | Measures | Also reports | Since | Status |
|---|---|---|---|---|
| Keyence FD-H10 (clamp-on) | Instantaneous flow | Accumulated flow, two temperatures, flow-stability level, 4 outputs, per-sensor error bits | v0.0.8 | ✅ Supported |
| Kobold MIK with C3T0 electronics (magnetic-inductive) | Flow, l/min | Volume total (liters), temperature, 2 outputs | — | ⚠️ Unreleased — development builds only |
ifm UGT (ultrasonic). A sensor aimed at nothing still streams a valid “no-target” reply rather than going silent — it is connected and healthy, with nothing to measure. A reading closer than 100 mm or 150 mm, depending on model, is shown but flagged, so a sensor mounted too close is visible as a mounting problem rather than a strange number. The sensor’s rated blind zone is larger — 150 mm or 200 mm — so mount it far enough above the highest liquid level to stay clear of that. Switch outputs are available as separate boolean channels alongside the distance reading: two on the UGT203 family, one on the UGT207 family, whose second output is analog. See ifm UGT Series.
Keyence FD-H10 (clamp-on flow). Takes around 15 seconds to become ready after power-up — noticeably longer than other devices. A sensor that looks missing immediately after a restart may simply still be starting. It reports accumulated as well as instantaneous flow, plus separate error bits per internal sensor, so a partial failure is visible rather than showing as a dead device.
Kobold MIK (magnetic-inductive flow). Reports flow, a running volume total, and the liquid’s temperature. The volume total can drive Volume Dosing: the controller reads it in liters and converts to gallons for the dose threshold. Keep the meter’s flow and volume units at their factory settings — the controller assumes l/min and liters. An empty or partly full pipe reads as zero flow. Bench-tested dry; wet-flow accuracy is not yet qualified. See Kobold MIK.
Keyence FR-L and FR-S01 (radar level). The FR-S01 is the short-range model with a built-in display. The controller treats both the same, except that flow conversion is an FR-L feature — on the FR-S01 the same field carries an accumulated level value. See Keyence FR Series. Both report detailed diagnostic bits beyond the measurement — interference, decreased stability, not-measurable, learning error, and per-output overcurrent. Useful in tanks with agitators or foam, where a reading can be present but untrustworthy. When the level changes suddenly, an FR-S01 occasionally sends one frame of all zeros; the controller ignores it as a dropped reading rather than seeing an empty tank, so a level interlock does not trip on it (upcoming firmware).
Keyence GP-M (pressure). One profile covers all six range variants. The controller reports temperature alongside pressure, and surfaces over/under-limit error bits separately from the reading.
An IO-Link sensor whose identity is not in the table is detected and shown as unsupported, but it is not added. Without a profile the controller cannot name, scale, or give units to its readings, so it cannot be used.
Bring an unrecognized sensor to engineering with its model number and vendor documentation. Adding a profile is routine, but it ships in a firmware release.
Paired onto the controller’s own WiFi network and controlled directly — not through the site network or the vendor’s cloud.
| Device | Type | Ports | Since | Status |
|---|---|---|---|---|
| Wireless Relay Expander | Switched outlets | 2 | v0.0.1 | ✅ Supported |
| Wireless Relay Strip | Switched outlets | 3 or 6 | v0.0.8 | ✅ Supported |
Only the models and device firmware that the controller recognizes during pairing are accepted.
Every wireless output device must install a failsafe. The controller refuses to register an output device that cannot be given one, so a switched pump turns itself off if the controller stops talking to it rather than running unattended. See Wireless devices.
Support for a device is not a configuration change — it needs a firmware entry describing its channels, units, and how to read and write it. Adding one is routine work, but it ships in a firmware release.
When requesting support, include the manufacturer and exact model number, the protocol, a datasheet or register map, and what you need to read or switch.