The hardware and firmware variations of the InteliHive controller, what each one changes, and how to tell which one a unit is — if a feature is missing, check here first.
If you don’t see a feature, check the unit before assuming a fault. Most “missing” menu items come from one of four things: the firmware build, the profile the unit is locked to, a capacity limit already reached, or the type of device selected.
¶ Telling which unit you have
| To find out | Look at |
|---|---|
| Firmware version and build | Settings → System Info — Version and Build. A new unit also shows its firmware version at the bottom of the Welcome screen. |
| Board revisions | Settings → System Info — Main Board and Port Board |
| Release or field-test firmware | Build reads Release or RC — see Firmware builds |
| Profile | Settings → Setup Wizard is only there on Boiler and Closed-loop units. Running it shows the profile on its Review setup screen. |
| Profile locked at the factory | First-time setup skips Pick profile |
| IO-Link ports | Settings → Devices → Add Device lists IO-Link Device |
Main Board and Port Board show the revisions the firmware was built for. The controller does not read them from the boards themselves, so they confirm the firmware build rather than prove what hardware is fitted.
¶ Hardware
| Option | What it changes | Covered in |
|---|---|---|
| IO-Link board | Controllers fitted with the IO-Link board have two ports, Port A and Port B. IO-Link Device is offered under Add Device only when the firmware’s board profile includes IO-Link. | IO-Link Devices |
| Main board revision | Current release firmware is built for main board v4 | Specifications |
| Port board revision | Current release firmware is built for port board v3 | Specifications |
Every port board revision the current firmware supports (v2 and v3) includes the IO-Link board, so in practice IO-Link Device is offered on every unit running current firmware.
¶ Firmware builds
The Build line in Settings → System Info says which build a unit runs.
| Build | Version looks like | What it is | Calendar |
|---|---|---|---|
| Release | v1.2.3 | Release firmware, for units in service | Not offered |
| RC | A short code ending in -rc, for example v8e808a4-rc | Release candidate, used for field testing | Offered |
Dev  |
A short code ending in -dev, or 0.0.0-local | Engineering bench build. Not for units in the field. | Depends on the build |
- Field-test features appear only on RC builds. Today that is the Calendar control mode. On a release build, Calendar is missing from Choose type. Saved calendar modes are kept, but do not run.
- A release build only moves forward. OTA Updates installs a newer release version and never an older one. If the offered firmware is from a different build, it asks Switch channel? first. See Firmware Updates.
- An RC or Dev build takes whatever it is offered. Its version is a code, not a number, so the controller cannot tell whether the offered firmware is newer. It asks Replace dev build? before installing.
¶ Profiles
The profile is chosen once, at setup, and locks until a factory reset. It decides what setup asks for and whether Setup Wizard appears in Settings. It does not limit which control modes you can add.
| Profile | Subtitle on screen | How it is chosen | Setup Wizard in Settings |
|---|---|---|---|
| Boiler | Blowdown by TDS | At setup, or locked at the factory | Yes |
| Custom | No preset | At setup, or locked at the factory | No — it has no roles to change |
| Closed-loop | Setpoint control | Locked at the factory only | Yes |
Pick profile also lists Cooling Tower, Closed-loop, and Repressurizer as Coming soon. They cannot be chosen at setup.
A unit locked at the factory skips Pick profile during first-time setup and goes on to time and device roles. Only a factory reset clears the lock.
See Profiles.
¶ Capacity limits
A limit that has been reached can look like a missing feature. The full list is in Specifications.
| Limit | Per controller |
|---|---|
| Control modes | 8 |
| Interlocks | 8 per control mode |
| Modbus devices | 8 |
| IO-Link sensors | 2 — one per port |
| IO-Link contacts | 4 — the I/Q and C/Q pin on each port |
| Wireless devices | 20 saved, 4 active at a time |
| Calendar programs | 3 steps before the action, 3 lockouts |
¶ What each device type offers
The device menu only shows what the selected device supports, so the same menu can look different from one device to the next.
| Device | Device menu items | Covered in |
|---|---|---|
| Sensorex Smart Sensor, Pyxis ST-712, Pyxis ST-500 | Info, Limits, Used by, Remove Device. The Sensorex conductivity variant also has Calibrate. | Supported Devices |
| Legacy Relay Device 6 | Info, Configure, Used by, Remove Device | Modbus RTU Devices |
| NextStep pump | Info, Control, Used by, Remove Device | Modbus RTU Devices |
| Wireless Relay Expander | Info, Configure, Used by, Remove Device. Configure also has Setup, to run its two relays as one valve. | Wireless Devices |
| Wireless Relay Strip | Info, Configure, Used by, Remove Device | Wireless Devices |
| IO-Link sensor | Used by, Remove Device. A level sensor also has Configure, for its tank settings. Remove Device is only offered while the sensor is disconnected. | IO-Link Devices |
| IO-Link contact | Configure, Used by, Reset counter | IO-Link Devices |
Items that change settings or switch outputs are hidden until the controller has confirmed the device’s identity — during a device conflict, for example.
Limits are set from the controller for Modbus sensors only. The device menu does not offer Limits on IO-Link sensors.
The Wireless Relay Expander is accepted with stable device firmware 1.6.0 or later in the 1.x line. Pre-release device firmware and 2.x are refused at pairing with Firmware unsupported.