Green power LED on the controller body should be illuminated. Green = controller has power.

If the LED is off, the controller has lost power. Confirm the PSU is wired correctly and supplying 24V DC. PoE is not supported. The controller has no voltage range; it requires fixed 24V DC. It is reverse-polarity protected, but reversed polarity will still prevent it from powering on.

Note that if a UPS is fitted in the panel, the controller will continue to run on battery for approximately four hours after mains power is removed. A controller that appears to lose power only after that delay points to a mains supply issue rather than a controller fault.

The RS485 plug at the controller should be fully seated in its port · push-in, hand-tightened. It should not pull out under light tension.

The two RS485 conductors at the controller end should match the polarity convention used at the first breaker in the daisy chain. One conductor typically carries a faint stripe; the other is solid. If the marked and unmarked conductors are in opposite positions at the controller versus the breakers, polarity is reversed at the controller end.

If the panel contains other communication buses (KNX, DALI, or similar), confirm that the RS485 plug is in the controller's RS485 port and not in any adjacent terminal block belonging to another bus. A higher-voltage bus connected to the RS485 port can permanently destroy the port.

If the controller's primary connection is Ethernet, the RJ-45 cable should be plugged in and the network port should show activity.

The controller falls back automatically through Ethernet → Wi-Fi → LTE, so a primary connection failure should not by itself cause the controller to go offline · it will switch to whichever backup is available. Every Hybird controller ships with a pre-configured LTE SIM for redundancy.

Blue = breaker is OFF / idle.

Red = breaker is ON / active.

Flashing purple = breaker is in setup mode (dip switch flipped for addressing). Should only ever apply to one breaker on the bus at a time. If two or more breakers are flashing purple, an address collision will be created or repeated · return the others to work mode before continuing.

Each breaker should have both A and B conductors plugged into its RS485 terminals. The conductors should be fully seated and resistant to light tension.

The polarity convention should be consistent across every breaker in the panel. A single device wired backwards will produce timeouts only on that device's Modbus ID.

Inspect any visible cable runs between breakers, and especially at panel-to-panel transitions, for damage or strain.

The green dip switch on each breaker selects between setup mode (for addressing) and work mode (for normal operation). For day-to-day operation, every breaker must be in work mode.

The LED is the visual confirmation of dip switch state: flashing purple = setup mode, blue or red = work mode.

The RS485 bus must be a single daisy chain · wired from the controller through each device in sequence, with no star or T-tap branches.

Inspect the daisy chain end-to-end if a contiguous group of devices has gone offline together. The most common break point is at a panel-to-panel transition where the cable crosses between enclosures.

For runs longer than approximately 30 m, screened twisted pair with the screen connected to controller GND and 120 Ω termination at each end is required. For runs over approximately 500 m a repeater is required.

Confirm the mains supply to the panel is intact and the panel is in its normal operating state.

Look for any signs of recent intervention · opened terminations, replaced devices, swapped breakers · that might explain a sudden change in behaviour. A breaker that was previously addressed at a different site and reused without re-addressing is a common cause of address collisions.

Look for any unusual environmental conditions: water ingress, signs of overheating, damaged enclosures.

Breakers not reporting · troubleshooting guide · triage between the common bus faults.

Single breaker not reporting · troubleshooting guide · when only one device has dropped off.

No devices reporting · troubleshooting guide · when nothing on the bus is reporting.

Group of breakers offline · troubleshooting guide · when a clustered group has dropped off.

Modbus address collisions · troubleshooting guide · when one device shows intermittent data and a neighbouring address is unexpectedly absent.