connecdoor connecdoor.controller Modbus RTU template

connecdoor.controller

Controls and monitors smart door access points via RS485

The connecdoor.controller template connects smart door controllers to ModbusCloud via Modbus RTU over RS485. It reads door states, lock detection, manipulation alerts, and daily access counters, and allows remote unlocking and day/night mode switching.

Protocol
Modbus RTU
Connection
RS485, 9600 baud
Registers
0, read only
Key readings
Door state (open, closed, locked, error) · Interface X20/X21 lock detection · Daily openings and access counter · Day/night mode status · Manipulation detection
Available commands
Unlock door · Day/night mode switching · Temporary opening trigger
Compatible models
connecdoor.controller
Last updated

Send your device list

If a device is not in the library yet, we build the template for free as soon as we have the register data.

Number of installations (optional)

Use cases

  • Monitor real-time door states across multiple buildings from a single cloud dashboard.
  • Create an alert when manipulation detection flags an impossible lock and door state combination.
  • Track daily opening and access counters to audit foot traffic for facility management reports.
  • Trigger a remote temporary door unlock for authorized visitors without being on site.
  • Schedule automatic day and night mode switching based on building operating hours.
  • Detect hardware errors on door controllers and notify the maintenance team immediately.

Installation

  1. Connect one RS485 extension per door to the connecdoor.controller and supply 24V DC to the door and its integrated components.

  2. Wire the RS485 A and B lines from the extension to the Modbus RTU port on your ModbusCloud Gateway.

  3. Set the Modbus RTU baud rate on the gateway to 9600 to match the connecdoor.controller default.

  4. Assign a unique Modbus slave address to each connecdoor.controller if multiple doors share the same RS485 bus.

  5. Import the connecdoor.controller template in the ModbusCloud platform and map it to the configured gateway and slave address.

  6. Verify communication by checking that door state and counter registers return expected values on the live dashboard.

Things to watch for

What baud rate should I use for the connecdoor.controller?

The default baud rate is 9600. Make sure the ModbusCloud gateway RS485 port is also configured to 9600, 8N1.

Do I need one RS485 extension per door?

Yes. Each connecdoor.controller requires its own RS485 extension module to communicate over the bus.

What happens to the door after a power cycle or gateway reboot?

The connecdoor.controller defaults to night mode (safe condition) on reboot. Any day mode or temporary unlock state is lost and must be re-sent from the cloud or automation logic.

Can I put multiple connecdoor.controllers on a single RS485 bus?

Yes, as long as each controller has a unique Modbus slave address. Keep total cable length and termination resistors in mind for reliable communication.

Want to see how it works?

Electrician working in an open distribution board