Every alarm the InteliHive raises has a numeric code, and every code has its own page. If the controller is showing an error, look it up here — or scan the QR code on the device to come straight to the right page.
Each code has its own short URL:
wiki.inteliverse.cloud/en/InteliHive/e/600
The leading digit tells you which subsystem the alarm came from, so a code you have never seen still tells you where to look.
| Range |
Subsystem |
Typically means |
| 1xx |
Device / bus |
A connected device’s connectivity or identity |
| 2xx |
Control-loop safety and policy |
A control loop is being blocked, limited, or held in a safe state |
| 3xx |
Process / sensor signals |
A measured value crossed a configured limit |
| 4xx |
Connectivity |
WiFi or cloud transport |
| 5xx |
System / lifecycle |
Commissioning, configuration, time, audit log |
| 6xx |
Hardware |
Power and board-level faults |
How alarms are named on the controller. The alarm list and toasts name the device first, then the condition — Acid Level Low, Conductivity Probe Disconnected, Feed Pump Manual On - 5 min. The code’s page uses the condition’s plain name, shown on each page as Shown as. Alarms about the controller itself name no device.
Not every code is a failure. Some are informational and exist so that a state change appears in the alarm history — Cloud Connected (421) is the healthy counterpart to Cloud Failed (420).
Every code has its own page. Codes marked reserved are not raised by current firmware but can appear in an older unit’s history.
| Code |
Shown as |
Severity |
|
| 100 |
Device Disconnected |
Warning |
A device the controller expects to be present has stopped responding |
| 101 |
Device Connected |
Info |
reserved |
| 102 |
Device Conflict |
Warning |
The device found at a saved location is not the device the controller expects — its type or serial number is different |
¶ 2xx — Control-loop safety and policy
| Code |
Shown as |
Severity |
|
| 200 |
Policy Blocked |
Warning |
An interlock, safety rule, or rate limit is holding a control mode’s output |
| 210 |
Rate Limit Warning |
Info |
An output has used 80 % of its actuation budget for the current rate-limit window |
| 211 |
Rate Limit Exhausted |
Info |
An output has used its whole actuation budget for the current rate-limit window |
| 212 |
Actuation Limit |
Warning |
A single blowdown or dose in a Setpoint Control mode has run longer than its limit alarm |
| 220 |
Profile Warning |
Info |
A control mode was saved with a setting outside boiler guidance: the conductivity change it accepts per sample exceeds 1000 µS/cm |
| 221 |
Sensor Asymmetry |
Info |
Two or more enabled control modes share one sensor, but not all of them have a Safety policy |
| 230 |
Control Inoperable |
Warning |
A control mode cannot run because a device it needs is missing, offline, or in conflict |
| 231 |
Local Override |
Warning |
An output was switched on locally, at the device itself, against what its control mode commands |
| 232 |
Dose Backlog Full |
Warning |
A Volume Dosing mode’s queue of owed doses is full, so some water is passing without being dosed for |
| Code |
Shown as |
Severity |
|
| 300 |
pH Warning |
Warning |
reserved |
| 301 |
pH Critical |
Severe |
reserved |
| 310 |
Low |
Warning |
A reading is below its configured low limit |
| 311 |
High |
Warning |
A reading is above its configured high limit |
| 312 |
Low-Low |
Severe |
A reading is below its configured critical low (low-low) limit |
| 313 |
High-High |
Severe |
A reading is above its configured critical high (high-high) limit |
| 320 |
Pipe Empty |
Warning |
reserved |
| 321 |
Clog |
Warning |
reserved |
| 322 |
Leak |
Severe |
reserved |
| 330 |
Pump Level Low |
Warning |
The NextStep dosing pump reports a low chemical level |
| 331 |
Pump Level Empty |
Severe |
The NextStep dosing pump reports an empty chemical tank |
| 332 |
Pump Overflow Warning |
Warning |
The NextStep dosing pump reports that an overflow is approaching |
| 333 |
Pump Overflow |
Severe |
The NextStep dosing pump reports an overflow |
| 334 |
Pump No Input |
Severe |
The NextStep dosing pump reports that an input signal it expects is missing |
| 335 |
Pump Over-Temperature |
Severe |
The NextStep dosing pump reports an over-temperature condition |
| 336 |
Pump High Pressure Warning |
Warning |
The NextStep dosing pump reports rising line pressure |
| 337 |
Pump High Pressure |
Severe |
The NextStep dosing pump reports high line pressure |
| 340 |
Probe Needs Cleaning |
Warning |
A Pyxis ST-500 reads fouled, so its readings may be low |
| Code |
Shown as |
Severity |
|
| 400 |
WiFi Disconnected |
Severe |
reserved |
| 401 |
WiFi Lost |
Warning |
The controller has lost its connection to the site’s WiFi |
| 402 |
WiFi Connecting |
Info |
reserved |
| 410 |
AP Enabled |
Info |
reserved |
| 411 |
AP Disabled |
Warning |
reserved |
| 412 |
AP Subnet Conflict |
Warning |
The site’s network overlaps the address range of the controller’s own WiFi network, so wireless devices cannot be reached |
| 420 |
Cloud Failed |
Severe |
The controller could not connect to Inteliverse |
| 421 |
Cloud Connected |
Info |
The connection to Inteliverse has been stable for 15 seconds |
| 422 |
Cloud Conflict |
Severe |
Inteliverse rejected this controller’s registration, usually because a device with the same name already exists |
| 423 |
Cloud Credentials Invalid |
Severe |
Inteliverse keeps accepting this controller’s credentials and then dropping the connection |
| Code |
Shown as |
Severity |
|
| 500 |
Setup Incomplete |
Warning |
One or more device roles the system profile requires have not been assigned |
| 501 |
Profile Unset |
Warning |
The controller has no system profile, so its saved control modes are paused |
| 502 |
Cloud Setup Pending |
Info |
This controller has never connected to Inteliverse, and has not been set to run offline |
| 510 |
Audit Log Full |
Warning |
The audit log reached its capacity and dropped its oldest entries |
| 520 |
RTC Missing |
Severe |
The controller’s hardware clock was not detected at start-up |
| 521 |
Time Not Set |
Warning |
The controller’s time is not trusted yet |
| 530 |
Config Error |
Severe |
A saved settings file could not be loaded, or a save was refused because it failed validation |
| 531 |
Config Changed |
Warning |
The controller changed a saved setting by itself; review, then acknowledge |
| 540 |
Display Degraded |
Warning |
The controller’s display has not updated for at least three seconds |
| 550 |
Firmware Update Failed |
Warning |
A firmware update failed, was interrupted, or was rolled back |
| Code |
Shown as |
Severity |
|
| 600 |
Power Fault |
Severe |
Input voltage has dropped below about 18 V DC on a supply that should be 24 V |
| 610 |
IO-Link Supply Short |
Warning |
The sensor supply on one IO-Link port is shorted or overloaded, so that port’s supply was switched off |
| 611 |
IO-Link C/Q Overload |
Warning |
The C/Q line on one IO-Link port is overloaded or shorted |
| 620 |
Modbus Supply Fault |
Warning |
The Modbus bus supply for port-powered devices is shorted, overloaded, or cannot come up, so it is held off |
| Severity |
Meaning |
| Info |
A state change worth recording. No action needed. |
| Warning |
Something needs attention but the system is still operating. |
| Severe |
Operation is compromised or has been stopped. Act now. |
An alarm is also either active or cleared, and separately acknowledged or not — so a fault that fixed itself overnight still leaves a cleared, unacknowledged entry in the history for you to review.
- Safety — read before servicing