Overview
Several different faults can cause Hybird breakers to stop returning data, and the symptoms overlap. This article helps narrow down which underlying cause you are looking at so the joint troubleshooting between installer and Hybird support can go straight to the right fix without rewiring things that are already correct. Most issues come down to one of three patterns: a single device wired incorrectly, a group of devices physically disconnected together, or two devices sharing an address.
How this issue is diagnosed
Diagnosis of any of the underlying faults is a shared workflow between the installer on site and Hybird support. The installer reports the visible symptoms (which breakers, where in the panel, when they stopped reporting); Hybird support reads the controller logs from Hybird Admin to confirm the symptom pattern and identify the matching fault type. The fix is then performed by the installer on site, with support confirming from Hybird Admin once the devices return to reporting. The path is: installer observes symptoms → contact Hybird support at [email protected] or +45 3020 4900 → joint diagnosis → installer performs fix.
Symptom
One or more Hybird breakers have stopped returning data, or appear to be returning unreliable measurements.
How to triage
Work through these questions in order before contacting support. Having the answers ready makes the joint diagnosis much faster.
1. Is the controller itself online?
If the controller is offline, this is a network connectivity issue, not a bus issue. Check Ethernet, Wi-Fi, and LTE connectivity to the controller before assuming anything is wrong with the breakers. The controller falls back in the order Ethernet → Wi-Fi → LTE, so if the primary connection has failed, it should be operating on a backup link.
2. How many breakers are affected?
If known, count the Modbus IDs that are not reporting. If you do not have that visibility on site, describe to Hybird support what is observable in the panel · which physical breakers have stopped functioning or which downstream loads have stopped responding correctly.
3. If only ONE breaker is affected
The fault is almost certainly local to that breaker · either reversed A/B wires or a loose RS485 conductor. See Single breaker not reporting · troubleshooting guide. On-site inspection is required; installer self-reports of "wires are correct" are unreliable.
4. If MULTIPLE breakers are affected, look at the pattern
The key question is whether the affected breakers cluster physically in the panel, or whether they are scattered across the bus.
NONE of the breakers are reporting. Every device on the bus shows timeouts and the controller is otherwise online. This points to a controller-end fault · either reversed A/B polarity at the controller, or in rare cases physical damage to the controller's RS485 port. Start with No devices reporting · troubleshooting guide. If polarity is verified correct and the bus is properly connected, see Total bus failure after wiring to wrong terminal · troubleshooting guide.
A physically clustered group of breakers is not reporting · for example, one row of the panel, one side of the enclosure, or one of two panels sharing a controller. The affected Modbus IDs may not be sequential. This points to a break in the RS485 daisy chain. See Group of breakers offline · troubleshooting guide.
One breaker is showing intermittent or unreliable data, and a neighbouring Modbus ID is unexpectedly absent. This signature · non-timeout errors on one address combined with consistent timeouts on the adjacent address · points to a Modbus address collision. See Modbus address collisions · troubleshooting guide.
5. Symptom patterns can overlap
It is possible for multiple faults to be present at once. For example, reverse polarity on three adjacent breakers will look identical to a daisy-chain break that took those same three devices offline. The single most useful disambiguating question is whether the affected breakers share a physical region (likely a daisy chain break) or a numerical Modbus range that doesn't match their physical layout (more likely individual wiring faults or address collisions). When in doubt, work from the most likely cause to the least likely: single-device wiring, then daisy chain integrity, then address collisions, then hardware damage.
What you can check on site before contacting support
The following can all be inspected on site without Hybird support, and the answers help narrow the diagnosis quickly. For a fuller reference, see On-site visual checks · what to inspect on a Hybird panel.
Device status LEDs on the breakers themselves. Flashing purple = setup mode; blue = OFF / idle; red = ON / active. If multiple breakers are showing flashing purple at once, this is itself a potential cause of an address collision and should be corrected.
Controller power LED. Green = controller has power. If off, restore power to the controller before investigating bus issues.
RS485 plug seating. The push-in plug at the controller end and at each breaker should be fully inserted and resistant to light tension.
Wire condition. Look for any obviously disconnected, damaged, or pulled-out conductors, particularly at panel-to-panel transitions.
Live-panel work
RS485 is low-voltage signal wiring and can be worked on with the panel live. Do not de-energise the panel · the installation is likely powering active loads. Apply standard panel-work precautions: avoid contact with AC terminals, and follow local regulations (Stærkstrømsbekendtgørelsen in Denmark, BS 7671 in the UK, VDE 0100 in Germany) for working inside a live distribution panel.
When to escalate
If you have worked through the relevant troubleshooting article and the issue persists, contact Hybird support at [email protected] or +45 3020 4900. Have the controller ID, the affected Modbus IDs if known, and a summary of what you have already checked ready before contacting support.
Summary
Most bus faults fall into a small number of patterns, and the pattern of how many devices are affected and whether they cluster physically narrows the cause significantly. Work through the four questions above, then contact Hybird support to confirm the matching fault from the controller logs and go to the specific article for the fix.