This driver integrates MolSmart RS485 presence sensors with Control4. Each sensor shows up as a contact connection (Sensor 1, Sensor 2…) that is bound to a Control4 Motion Sensor and then works in programming, scenes and Navigator like any motion sensor.
A single driver handles every sensor on the bus. There are no addresses to set: when the pairing button of a new sensor is pressed, the driver gives it an address and creates the matching connection.
Real-time presence and absence of each sensor.
Automatic pairing from the button on the sensor, or from the Pair New Sensor action.
Connection number equal to the sensor address (sensor 1 is connection Sensor 1), regardless of pairing order.
Sensor list kept across controller restarts; on start, the driver queries each sensor to refresh its state.
State of each sensor and time of the last change in the Sensors property.
Communication test showing the firmware version of each sensor.
Model: MolSmart RS485 presence sensor.
Sensor settings (sensitivity, detection area, hold time, LED) are not handled by the driver: set them on the sensor itself, as described by the manufacturer.
Prerequisites
RS-485 bus of the sensors connected to a serial port of the Control4 controller through an RS-232/RS-485 converter (9600 bps, 8N1, no flow control).
New sensors leave the factory without an address.
Pair one sensor at a time: only one sensor may be in pairing mode on the bus.
Add the ZoomDH - MolSmart Presence Sensor RS485 driver to the project in Composer Pro. It is installed only once, whatever the number of sensors.
Under Connections → Control/AV, bind the driver's Serial RS-485 connection to the controller serial port where the converter is connected.
On each sensor not yet paired, press the pairing button. Within a few seconds the driver gives the sensor an address and creates the Sensor N connection. Driver Information shows the progress.
Repeat for the other sensors, one at a time.
For each sensor, add a Control4 Motion Sensor (Composer: Items → Sensors → Motion Sensor) in the room where it is installed and bind its contact connection to the driver's Sensor N connection.
After purchasing the license, enter the key in License Key.
Tip: to find out which sensor is which, walk in front of it: the Sensors property shows which number changed to presence.
Several sensors on the bus
All sensors share the same driver instance and the same serial port. The driver accepts up to 999 sensors, within the physical limits of the RS-485 bus.
A sensor that is already paired does not announce itself as new when the button is pressed. To pair it again, do a factory reset first (hold the button for more than 3 seconds).
A sensor that already has an address (for example, paired in another installation) is added automatically the first time it transmits.
Properties
Property
Description
License Key
Driver license key.
License Status
License state and remaining trial time.
Control4 MAC Address
Controller MAC, used by the license.
Driver Name / Driver Version
Driver name and version.
Log Level / Log Mode
Driver log level and destination. Leave Off in normal use.
ZOOMDH Debug
For ZoomDH support use.
Driver Information
Driver messages: pairing, communication test, warnings.
Connection Status
Whether the serial connection is bound in Composer.
Bus Status
Online when data arrives from the sensors; No response when the communication test gets no answer; Waiting for data after start. Sensors only transmit when something changes, so Online is kept for 6 hours after the last data.
Presence Contact State
How presence shows on the contact: Opened (default) or Closed. Use Closed if the Motion Sensor shows the state inverted.
Sensors
One item per paired sensor, in order: current state (presence or absence) and date and time of the last change. E.g.: Sensor 1: presence since 03/11 15:58:02 | Sensor 2: no reading.
Actions
Action
Description
Test Communication
Queries the firmware version of each paired sensor and of a sensor still without an address. Within a few seconds, Driver Information shows who answered, or warns that no sensor answered. Then the driver refreshes the state of each sensor.
Pair New Sensor
Gives an address to a sensor that is already in pairing mode (LED blinking) when the button notice did not reach the driver. Keep only one sensor in pairing mode.
Remove Sensor
Removes a sensor from the list along with its connection (use when replacing or removing a sensor).
Rename Sensor
Gives the sensor connection a name to organize the project, for example Sensor 1 - Living Room. The sensor number stays in front. The Motion Sensor binding does not change. Leave the name empty to go back to Sensor 1.
Clear Sensor List
Erases the whole sensor list and the sensor connections. Sensors still on the bus are added again when they transmit, and the Motion Sensor bindings must be redone.
Connections
Connection
Description
Serial RS-485
Bind to the controller serial port where the bus converter is connected.
Sensor 1, Sensor 2…
One contact connection per paired sensor, created by the driver. Bind each one to a Control4 Motion Sensor. Use the Rename Sensor action to name them. The Motion Sensor receives the current state as soon as it is bound.
Troubleshooting
The sensor does not show up after pressing the button: make sure only one sensor is in pairing mode. With two sensors without an address at the same time, pairing fails.
The sensor LED blinks but no connection is created: the button notice did not reach the driver. With the LED still blinking, run the Pair New Sensor action. If the sensor does not confirm, check the RS-232/RS-485 converter and the A/B wiring.
The state does not change when moving in front of the sensor: the sensor only reports when the state changes. If it was already in presence, new movement does not generate a report. Leave the area until the sensor reports absence, or run Test Communication to read the current state.
Presence shows inverted on the Motion Sensor: change Presence Contact State to Closed.
Pressing the button on a paired sensor does nothing: normal sensor behavior. Do a factory reset (hold the button for more than 3 seconds) before pairing it again.
No sensor answers: run Test Communication. If Driver Information warns that no sensor answered, check the serial binding in Composer, the converter, the A/B wiring and the port settings (9600 bps, 8N1).
Licensing
30-day trial included; the remaining time shows in License Status.
One license per controller covers every sensor on the bus. Enter the key in License Key.
The controller needs internet access to activate the license.
Initial version: every sensor on the bus in a single driver, automatic pairing from the sensor button, one Motion Sensor connection per sensor, named by the installer, state of each sensor and communication test.
