A KNX bus power supply overload is one of those faults that can bring an entire installation to its knees, and often at the worst possible moment. Whether devices are resetting unexpectedly, the bus is behaving erratically, or the installation simply refuses to respond, a stressed power supply is frequently the culprit. Diagnosing a KNX bus power supply overload requires a structured approach: knowing what to look for, how to measure it, and where the problem is likely hiding. This guide walks through the full diagnostic process, from the first warning signs to long-term prevention.
Warning signs of a KNX bus power supply under strain
The earliest indicators of a KNX power supply problem are often subtle and easy to misattribute to software or configuration issues. A bus voltage that drops below the nominal 29 V DC is one of the clearest red flags. When the supply cannot maintain adequate voltage under load, connected devices start to behave unpredictably: telegrams get lost, actuators respond slowly, or sensors drop off the bus entirely.
Beyond voltage drops, watch for these common warning signs in a struggling KNX installation:
- Devices resetting or rebooting without any apparent trigger
- Intermittent communication failures between bus participants
- The power supply unit running unusually hot or its status LED showing a fault
- Increased telegram errors visible in the ETS diagnostics tool
These symptoms tend to worsen during peak usage periods, when many devices are active simultaneously and current demand spikes. If the problems appear only at certain times of day or when specific functions are triggered, that pattern is a strong hint that the supply is being pushed beyond its rated capacity.
How to measure bus current and locate the fault
Accurate measurement is the backbone of any solid KNX bus fault diagnosis. Start by measuring the bus voltage directly at the power supply output terminals using a calibrated multimeter. A healthy KNX bus should sit between 28 V and 30 V DC under normal operating conditions. A reading consistently below 27 V under load points to either an overloaded supply or a failing unit.
Next, measure the total bus current draw. Most KNX power supplies have a rated output current, typically 160 mA, 320 mA, or 640 mA depending on the model. The actual current consumption of each bus device is listed in its technical datasheet, usually between 5 mA and 15 mA per device. Add up the declared current values for all connected participants and compare this total against the power supply’s rated output. If the sum approaches or exceeds the rated figure, the supply is working at its limit.
To locate a specific fault rather than a general overload, a line coupler or area coupler can help isolate individual bus segments. Disconnect segments one at a time and monitor whether the bus voltage recovers. When disconnecting a particular segment causes the voltage to stabilise, that segment is drawing excessive current and warrants closer inspection. A clamp meter placed around the bus cable can also give a real-time current reading without interrupting the circuit.
Common causes of KNX bus power supply overloads
Understanding why a KNX power supply becomes overloaded makes it far easier to resolve the problem at its root rather than simply replacing hardware. The most frequent cause is a bus that has grown organically over time: devices added incrementally without recalculating the total current budget. What started as a modest installation can quietly exceed the power supply’s capacity after a few expansions.
Wiring faults are another major contributor. A short circuit on the bus cable forces the power supply to deliver far more current than it is designed for, often triggering the built-in current limiting protection. Similarly, a damaged or degraded cable with high resistance can cause localised voltage drops that mimic the symptoms of an overloaded supply even when the total device count is within limits.
Faulty bus devices are worth investigating too. A malfunctioning actuator or sensor can draw significantly more current than its rated value, effectively acting as a drain on the entire line. This is particularly hard to spot because the device may still appear to function normally from a control perspective while silently consuming excess current in the background.
Resolving and preventing overloads in KNX installations
Once the source of the overload is identified, the resolution path becomes straightforward. If the total device count simply exceeds what a single supply can handle, the most reliable fix is to split the bus line and add a second power supply to share the load. KNX guidelines recommend no more than 64 devices per line segment, and current budgets should always include a safety margin of at least 20% above the calculated total.
For wiring faults, a thorough visual inspection combined with a continuity test will reveal shorts or breaks in the bus cable. Replace any damaged sections and re-test bus voltage before reconnecting all devices. If a specific device is suspected of drawing excessive current, remove it from the bus temporarily and monitor whether the supply stabilises, a simple but effective isolation technique.
Prevention is ultimately the most cost-effective strategy for KNX installation troubleshooting. Keeping a detailed record of every bus participant, its rated current consumption, and the line it belongs to makes future capacity planning straightforward. Revisiting that documentation whenever the installation is expanded prevents the gradual overloading that catches many installers off guard. Choosing power supplies with built-in diagnostics or status outputs also makes ongoing monitoring far easier, giving early warning before a fault develops into a full outage.
How xxter supports KNX professionals in the field
Diagnosing and resolving bus power issues is only one part of delivering a reliable KNX installation. xxter builds tools and controllers that help professionals monitor, manage, and expand KNX systems with confidence. The xxter controller and full product range sits at the heart of any KNX setup, giving integrators and end users a single interface to oversee all connected devices, run diagnostics, and manage automation logic without additional licensing costs.
For professionals focused on energy performance alongside reliability, xxter’s Smart Energy Manager for KNX installations integrates directly with KNX infrastructure to actively manage energy endpoints based on solar production forecasts, dynamic pricing, and real-time consumption data. This means the same bus infrastructure that controls lighting and climate can also optimise EV charging and battery storage intelligently.
Here is what xxter brings to KNX professionals specifically:
- A KNX controller with full app-based monitoring, available on iOS, Android, and Windows
- Compatibility with KNX, EnOcean, Modbus, BACnet, and Philips Hue: no protocol silos
- No subscription fees or device limits on the free xxter app platform
- Smart Energy Manager for active energy optimisation within existing KNX installations
If you are building or maintaining KNX installations and want a platform that grows with your projects, contact the xxter team directly or explore what xxter has to offer at xxter.com.
Preguntas frecuentes
How do I know if I need a second KNX power supply or just a replacement unit?
If your total calculated current consumption across all bus devices is approaching or exceeding the rated output of your existing supply, adding a second power supply and splitting the line is the right move — replacing the unit with an identical model will not solve the underlying capacity problem. However, if the total device current is well within the rated limit but the supply is still underperforming, a failing unit is more likely and a like-for-like replacement makes sense. Always recalculate your current budget after any expansion before deciding which path to take.
What safety margin should I build into my KNX current budget when planning an installation?
KNX best practice recommends leaving a minimum safety margin of 20% above your calculated total current consumption, meaning if your devices collectively draw 250 mA, your power supply should be rated for at least 320 mA. This headroom accounts for inrush currents during device initialisation, future device additions, and any slight variation in actual versus datasheet-rated consumption. Building in this buffer from the start is far cheaper than diagnosing an overload fault after commissioning.
Can a single faulty device really take down the entire KNX bus line?
Yes — a malfunctioning bus device that draws excessive current can deprive other participants of the voltage they need to operate reliably, effectively degrading or collapsing communication across the entire line. The tricky part is that the faulty device may still respond to commands and appear functional in ETS, making it easy to overlook. The most efficient way to identify it is to remove devices from the bus one at a time while monitoring bus voltage, narrowing down to the culprit by elimination.
What is the maximum number of devices I can connect to a single KNX power supply?
The KNX standard sets a maximum of 64 bus devices per line segment, but the practical limit is almost always determined by current capacity before you reach that device count. A standard 160 mA power supply, for example, can realistically support around 20 to 30 devices depending on their individual current draw. Always sum the datasheet current values for every planned device on the line and compare against the supply’s rated output — the current budget, not the device count, is typically the binding constraint.
How do I test for a short circuit on a KNX bus cable without specialist equipment?
With the power supply disconnected, a basic continuity test using a standard multimeter between the two bus conductors (TP+ and TP−) will reveal a short circuit — a reading close to 0 Ω confirms a fault in the cable or a connected device. To isolate whether the short is in the cable itself or inside a device, disconnect all bus participants first and retest the cable in isolation. If the short disappears once devices are removed, reconnect them one by one to identify the offending unit.
Does the physical length of the KNX bus cable affect power supply performance?
Yes, cable length introduces resistance that causes a voltage drop along the bus, which means devices at the far end of a long run may see a lower voltage than those close to the power supply — even if the supply itself is performing correctly. KNX guidelines specify a maximum cable length of 1,000 metres per line and recommend positioning the power supply centrally within the line rather than at one end to distribute the voltage drop more evenly. For very long runs, using a thicker cable gauge or adding a line repeater can help maintain adequate voltage across all participants.
How often should I audit the current budget of an existing KNX installation?
You should revisit your current budget any time a device is added to the bus, not just during major expansions — even a single high-draw device can push a supply that was already near its limit into overload territory. Beyond change-driven reviews, an annual audit is a good habit for larger or frequently modified installations, cross-referencing your device register against the power supply’s rated output. Maintaining a live spreadsheet or using your ETS project documentation as a running record makes these checks quick and straightforward.