Overview
If the Hybird Edge Controller's RS485 port is accidentally wired into a different communication bus operating at a higher voltage · for example, a KNX bus in a mixed installation · the RS485 port can be permanently damaged. The fault looks similar to controller-end reverse polarity (no devices report), but no amount of rewiring will restore communication, because the port itself is destroyed.
How this issue is diagnosed
This fault is resolved jointly between the installer on site and Hybird support. The installer reports the symptoms and the wiring history; Hybird support reads the controller logs from Hybird Admin to confirm the bus-wide timeout pattern and rules out reverse polarity at the controller, which presents identically and is much more common. Replacement of the controller is the only resolution if hardware damage is confirmed. If the symptoms in the next section match what you are seeing, contact Hybird support at [email protected] or +45 3020 4900 to begin the joint diagnosis.
Symptom
No devices on the bus return data · every Modbus ID is consistently offline.
The controller is otherwise functional: powered, online, and reporting normally to the platform.
The fault persists after the RS485 wiring has been visually verified and any obvious wiring errors corrected.
There is a history of the controller having been wired into, or near, a non-RS485 bus · typically in a mixed-protocol panel containing KNX or another building-automation bus.
From the support side, controller logs in Hybird Admin show Modbus timeout errors on every device address. Each address produces a log line in the form: [<timestamp>] [ERROR] [GET_MEASUREMENTS] Failed to read measurement from Device <modbus_id> (<device_type>): Modbus error: Modbus query timed out. The pattern is identical to controller-end reverse polarity · see No devices reporting · troubleshooting guide. Log format may change over time as the underlying libraries are updated, so search by symptom rather than by exact string.
Possible causes
Controller RS485 port wired into a higher-voltage bus. The most likely cause when this pattern appears. Overvoltage destroys the RS485 driver in the controller; subsequent correction of the wiring does not restore function because the silicon has already failed.
Controller-end reverse polarity. Produces the same "no devices reporting" symptom. Always rule this out first · it is far more common and can be fixed in seconds. See No devices reporting · troubleshooting guide.
Bus not physically connected to the controller. The RS485 plug is not seated or has come loose. Verify before assuming hardware damage.
Diagnosis
Hybird support will confirm from the controller logs that the controller itself is online and that the timeout pattern is bus-wide rather than affecting only a subset of devices. The log signature is identical to controller-end reverse polarity, so the diagnostic question is what is found on site after wiring has been verified correct.
The installer performs the physical inspection on site:
Confirm the controller has power (green power LED on the controller body).
Inspect the RS485 connection at the controller. Confirm the plug is fully seated and that A and B polarity matches the rest of the bus. See No devices reporting · troubleshooting guide for the polarity check.
If polarity is verified correct and the plug is seated, ask whether the panel contains any other communication bus · KNX, DALI, or any other building-automation wiring. Confirm whether the RS485 plug may at any point have been connected to a terminal block belonging to another bus.
If polarity is verified correct, the plug is seated, and no device on the bus reports, hardware damage to the controller's RS485 port is the likely cause. For a fuller checklist of what to inspect on site, see On-site visual checks · what to inspect on a Hybird panel.
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.
Resolution
This fault cannot be resolved on site. The controller must be replaced.
Contact Hybird support at [email protected] or +45 3020 4900 to arrange advance replacement of the controller under warranty.
Before installing the replacement controller, confirm that the panel's RS485 wiring is correctly identified and isolated from any other communication bus in the enclosure. Label the RS485 conductors at the controller end if there is any risk of confusion with adjacent buses.
Once the replacement controller is wired correctly and powered, Hybird support will confirm from Hybird Admin that all devices on the bus return to reporting.
Prevention
In panels that contain more than one communication bus, label all signal-wiring terminations clearly · both at the controller end and at any panel-to-panel transition.
Verify that the RS485 plug is being inserted into the controller's RS485 port and not into any other terminal block in the panel before applying power.
Where space allows, physically separate RS485 wiring from other communication buses to reduce the chance of cross-connection during subsequent work.
When to escalate
This article describes a hardware-failure scenario that always requires controller replacement. Contact Hybird support at [email protected] or +45 3020 4900. Return the faulty unit to Hybird at Frederiksberg Allé 60A within 14 days of receiving the advance replacement.
Summary
If no device on the RS485 bus reports and the controller is otherwise functional, suspect reverse polarity first · it is much more common and easy to fix. If polarity is correct and the bus is properly connected, and there is any history of the panel containing a higher-voltage bus such as KNX, the controller's RS485 port may have been destroyed by overvoltage and the controller will need replacing under warranty.