Quick answer

A B-hyve fault means the controller detected excessive current, usually from a shorted solenoid, crossed or damaged wire, wet splice, or too much load on one terminal. Record the station, disconnect power, then isolate the field wires from the timer before replacing parts.

This guide also answers
Orbit B-hyve fault messageB-hyve station wire shortB-hyve solenoid resistance fault

Match the pattern before opening anything

Possible causeBest clueFirst check
Bad solenoidFault follows one valveDisconnect and test the coil
Shorted field wireFault remains with solenoid removedInspect cable and recent digging
Wet or crossed connectionFault began after rain or serviceInspect terminal and valve-box splices
Overloaded terminalMultiple valves share one stationReduce load to rated output

Read the system before replacing a part

Use the observation that most closely matches your yard. Each row changes the next test, so you do not spend an afternoon proving the wrong theory.

Fault names one station and returns when it starts

What it meansB-hyve detected excessive current on that station circuit.

Do nextPower down and isolate its conductor, splices, cable, and solenoid.

Fault clears when the station and associated common are disconnected

What it meansThe unloaded timer output is not producing the fault.

Do nextTest field cable and solenoid separately.

Fault remains with the output unloaded

What it meansThe B-hyve terminal or controller may be faulty.

Do nextDocument the unloaded test for Orbit support.

Two valves share the faulted terminal

What it meansCombined current may exceed the output limit.

Do nextCompare the design with the timer rating rather than repeatedly clearing Fault.

Four tests that narrow the fault

Stop as soon as one result gives you a clear boundary. The goal is not to perform every test; it is to eliminate whole groups of causes safely.

  1. 01

    Record the faulted station

    Photograph the app or timer message before clearing it.

    IF YES / NORMALThe named output defines the circuit to isolate.

    IF NO / ABNORMALA device-wide power or communication message needs a different path.

  2. 02

    Inspect the terminal power-off

    Disconnect power, label the conductor, and check for crossed strands or multiple loads.

    IF YES / NORMALThe terminal is clean and correctly loaded.

    IF NO / ABNORMALCorrect visible crossing or unsupported load before retest.

  3. 03

    Run the official unloaded comparison

    With power off, remove the named station wire and associated common as Orbit directs, then run a brief test.

    IF YES / NORMALNo fault unloaded places the cause in field wiring or solenoid.

    IF NO / ABNORMALFault unloaded points back to the timer.

  4. 04

    Measure the complete circuit

    With power off, measure station-to-common resistance at the timer and compare with Orbit's guidance and the exact solenoid maker.

    IF YES / NORMALA plausible reading supports a controlled retest.

    IF NO / ABNORMALVery low or high readings require coil, splice, common, or cable isolation.

Numbers worth measuring

Orbit B-hyve field-circuit guidance20–60 ohms in Orbit's fault article

Valve makers differ. Treat under 20 or over 60 as a branch to isolate, not a universal component verdict.

Values are diagnostic references, not universal pass/fail limits. Confirm the specification for the exact controller, valve, solenoid, nozzle, and local installation.

Common fixes that waste time

Clearing Fault repeatedly

The controller is protecting itself; the short or overload remains.

Reading continuity beep as proof of a good circuit

Continuity alone does not distinguish a healthy coil from an abnormally low resistance.

Replacing the controller before unloading the station

Orbit's comparison explicitly separates timer output from field load.

Worked diagnostic example

How the evidence changes the repair

B-hyve reported Fault on station 6 after landscape work.

  • The fault disappeared with station 6 and its common disconnected.
  • Station-to-common measured far below the neighboring circuits.
  • A crushed cable beside a new edging stake was repaired; the resistance normalized.
Conclusion

The unloaded test protected the controller from a false diagnosis. The abnormal field reading and recent disturbance converged on cable damage.

Reconstructed teaching case based on documented system behavior. It is not presented as a laboratory test or a repair performed by Sprinkler Fix Lab.

How to confirm the repair actually held

A single successful start can hide an intermittent splice, sticky valve, remaining leak, or scheduling problem. Recreate the original conditions before calling the job finished.

01
Run the repaired station three short times and confirm Fault does not return.

Pass: The original symptom stays absent during the direct test.

If not: Repeat the last isolation step; the fault is incomplete or intermittent.

02
Allow that station to operate once from its normal program.

Pass: Automatic behavior and recorded status now match physical watering.

If not: A schedule, sensor, smart feature, master command, or cloud-state issue remains.

03
Inspect repaired splices after the valve box becomes wet.

Pass: The correction holds under normal time, moisture, load, and network conditions.

If not: Use the first changed condition to locate the remaining intermittent boundary.

Recognize the controller state

Check these in order

  1. 01

    Capture the exact station fault

    Photograph the app or timer message. A numbered station turns a broad controller problem into a specific circuit diagnosis.

  2. 02

    Disconnect power and label wires

    Remove power before moving conductors. Label the station and its common path so you can restore the original configuration exactly.

  3. 03

    Test the timer with the field load removed

    Orbit recommends removing the identified station wire and associated common, then running a short test. A fault with wires removed points toward the timer; no fault shifts attention into field wiring or the solenoid.

  4. 04

    Inspect waterproof splices and coil

    Open the valve box and check for crossed copper, water-filled connectors, corrosion, or damaged insulation. Test the solenoid separately rather than replacing both valve and controller.

  5. 05

    Restore one known-good circuit

    After correcting the fault, reconnect one load, clear the message, and run a one- or two-minute test. Stop if the fault returns immediately.

  • The short is underground.
  • Several valves or a pump relay share the output.
  • The timer faults even with the affected field conductors removed.

What homeowners ask about this symptom

Can a B-hyve fault be caused by the controller?

Yes, but isolate it. If the same terminal faults with its station and common field wires removed, the timer becomes the leading suspect.

Why should I disconnect the common too?

Removing both conductors isolates the external circuit more completely and prevents a shared field path from confusing the test.

Sources and review notes

General maintenance logic is checked against EPA WaterSense outdoor irrigation guidance. Product controls and disassembly steps vary by model; use the current manufacturer manual for your exact valve, controller, or sprinkler head.

Orbit: Resolve a B-hyve Fault ErrorOrbit: Valves Not Turning On
Published and last reviewed: August 30, 2026