Utility

Control4 BMS Monitor is a unique driver from Janus technology for monitoring thermostat and consumption data, providing a simple web interface for viewing this historic data. All data is stored directly on the main controller, and backed up in persistent memory, so it is preserved across power cycles and even system restores. Up to 30 days' data (or 10K samples) are stored for each of the monitored elements, with simple navigation between daily and weekly views.

The solution supports any thermostat proxy, v1 or v2 - no special thermostat drivers are required. Additionally, a range of generic monitoring drivers allow and data to be stored and a hostory visualised

Control4 BMS Monitor Lite is a unique driver from Janus technology for monitoring thermostat and consumption data, providing a simple web interface for viewing this historic data. All data is stored directly on the main controller, and backed up in persistent memory, so it is preserved across power cycles and even system restores. Up to 30 days' data (or 10K samples) are stored for each of the monitored elements, with simple navigation between daily and weekly views. This is a cost-reduced version of our BMS Monitor supporting a single thermostat.

The solution supports any thermostat proxy, v1 or v2 - no special thermostat drivers are required. 

Enables you to manage the state of Control4 Contact Sensors via programming.  This allows you to set and use Contact Sensors from many different sources which cannot be directly connected.

This driver is a simple convertor that allows you to use a Contact Sensor Input (like from a Controller, Z2IO, Z2C, etc….) within Composer and get a Keypad Connection output.

Features

• Quickly bind the contact connection
• Quickly bind the corresponding keypad connection to a device (like the Toggle of a light)
• Should mimic a keypad button press including the push and hold to dim a light.
• Contact Connection 1 is linked to Keypad Connection 1, and so on…

Properties

• Device Settings
  • Click Rate: This is where you set the click rate to differentiate from a quick click (single tap) or a longer push and hold

Connections

• • 20 Contacts Inputs: This is where you will bind the driver to devices like the contact on a controller, IO Extender, Z2IO or Z2C (or similar)
  • 20 Keypad Inputs: This is where you will bind the driver to a device like you would a keypad button

FAQ

• Can you give us some examples of how we could use this driver?
  • We have had some requests were an old, centralised lighting system is being changed and need to use existing switchgear. This allows for pulse, press, release inputs to a contact so that the existing switchgear acts as if it were a keypad button
• Can you have more than one Driver per project?
  • Sure can.
• Can you bind multiple connections to a contact connection?
  • Nope.
• Can you bind multiple connections to a keypad connection?
  • Nope.
• What if I have 2 buttons that need to control one light
  • You can bind the one contact to a connection and then connect to other to another contact connection. The corresponding keypad connections can both be bound to the toggle connection of the light.
• I want to try before I buy…
  • No problem, the driver comes with a free 15-day trial

This driver is a simple convertor that allows you to use a Dimmer Proxy (Dimmer Driver) within Composer and get 10 Relay Connections out.

Features

• Quickly select the lighting driver from System Design
• Quickly bind the Relay outputs to the Relay Driver you need to control
• If the light is dimmed on via the light icon on a navigator this will reflect on the relay driver
• If the relay device is triggered the commands are routed to the lighting device