Dry Contact vs RS485: Wiring Panels Into a Third-Party BMS

YHOPE · 智能开关面板

Dry Contact or RS485? How to Wire Panels Into a Third-Party BMS

Most integration problems on site are not protocol problems. They are interface mismatches, agreed in a chat thread and discovered at commissioning: the BMS wants a contact, the panel speaks a bus; or the BMS speaks KNX while the room is wireless. Both are solvable, but with two different interfaces. Knowing which one the controller wants before the wall-box schedule is frozen removes most of the pain.

Two Interfaces, Two Different Jobs

Dry contact is a handshake, not a protocol. A dry contact is a potential-free closure: the panel side only opens or closes a loop, and the controller supplies whatever voltage it wants to read. That makes it natural for binary facts - a room card inserted, a door or window contact, a presence signal, an alarm input, a scene trigger, or a status feedback from a relay. Nothing needs addressing, no driver is installed, and the control side stays electrically separate from the mains side. The Tuya hotel SaaS integrated host (RCU) provides 6 dry contacts (IN2-IN7) for exactly this class of signal.

RS485 is a bus for panels that need identity and payload. Where the controller must talk to many addressed devices, or must carry more than an on/off fact, RS485 is the right layer. The same RCU pairs with RS485 12V 24-key panels, so a room keypad becomes an addressed device rather than a bundle of discrete wires. The wired 485, low-voltage 485 and wireless options across the YHOPE range exist for the same reason: a bus where deterministic addressing matters, mesh or Zigbee where the wiring is not there. A separate AC gateway with RS485 and UART covers 9+ VRF and ducted AC brands.

When the BMS speaks KNX, use a gateway instead of rewiring. KNX fusion gateway LG1 combines a KNX bus with ZigBee/BLE, exposes 200 channels, covers 30+ device types, and is configured in ETS5.7+. The third-party KNX controller sees the wireless panels and sensors as objects on its own bus, so the BMS side keeps its engineering tooling and the room side keeps its devices, with no new cabling between them.

What to Confirm Before You Specify

The RCU also carries 1 x 40A plus 12 x 10A relays, 4 local dimming groups with PWM groups that keep working with the gateway out of the loop, 4 curtain binding groups, and a wide-voltage design: 90-280V on the mains side and a 24-48V low-voltage side. Those numbers decide how many loads and panels a room can carry, and they are best settled at design time rather than during commissioning.

Wiring and Acceptance: What to Verify on Site

• Label every dry-contact channel and its function at both ends. Unlabelled IN2-IN7 wiring is the most common source of "the wrong light came on" calls.
• Confirm who supplies the loop voltage, then measure it at the contact with the panel connected.
• Verify A/B polarity and termination on the RS485 run, keep low-voltage cable separated from mains, and test the panels furthest from the host - not only the nearest one.
• Map each panel address to its room number and record the mapping. A panel swapped between rooms is an addressing problem, not a hardware fault.
• Test every contact channel against the BMS point list one by one, in both directions: command out, feedback in.
• Disconnect the higher-level link and confirm the room still behaves. Local dimming groups and curtain bindings should keep working when the gateway or BMS is offline.
• Record the baseline specification on the handover sheet: 5-year warranty, 40-400V wide voltage, 4kV surge tolerance, V0 flame-retardant PC housing.

Three Failures Worth Anticipating

A dry contact treated as a powered signal: the installer expects voltage on the pair, reads nothing, and concludes the port is dead. A NO/NC convention decided by whichever crew showed up rather than by drawing. And a room that depends entirely on the BMS for basic function, so a host offline for an afternoon leaves the room unusable. The first two are paperwork problems; the third is a design choice, and local control belongs inside it.

FAQ

Can a dry contact carry a dimming level or a temperature?

No. A dry contact only reports open or closed, so it suits binary facts such as card-inserted, door contact, presence or alarm. Anything with a value - brightness level, setpoint, scene number - needs an addressed interface: RS485, KNX, or the platform integration on the host.

My BMS uses a different bus and my panels are wireless. Do I have to rewire?

Not necessarily. KNX fusion gateway LG1 is built for exactly this case: KNX on the controller side, ZigBee/BLE on the device side, 200 channels and 30+ device types, engineered in ETS5.7+. The controller keeps its own tooling and no new cable has to run between the two systems.

What happens to the room when the BMS is offline?

It depends on the local control design, and it is worth deciding deliberately. On the RCU, local dimming groups with PWM groups work with the gateway out of the loop, and curtain bindings are local too, so the room keeps functioning. Confirm this during commissioning by opening the link on purpose.

How many dry-contact inputs does the host provide?

The Tuya hotel SaaS integrated host (RCU) provides 6 dry contacts, numbered IN2-IN7. Whether that covers a given room depends on how many binary signals the BMS needs to exchange; check the count against the point schedule before the design is fixed.

Send us the BMS interface list and the point schedule for one typical room, and we will map which channels and which interface carry which function.

• Website: **www.yhopecn.com**
• WhatsApp: **+86 18680023968**
• Email: **623177376@qq.com**

「Customer satisfaction is the only measure of our work.」

YHOPE 圆和智能 · 广东顺德圆合智能科技有限公司