Vive Wireless Hub User Guide

June 7, 2024
Vive

Vive Wireless Hub

product

The Vive hub provides a connection point for Lutron Vive devices such as PowPak wireless dimming and switching modules, Pico remote controls, Radio Power Saver occupancy sensors, and daylight sensors. For a complete list of compatible devices, see the last page of this document. For more information on the Vive hub, including training materials, design information and software updates, please visit www.lutron.com/vive.image 1 image 2

Features

  • Can be easily programmed with any Wi-Fi enabled iOS® or Android® compatible device using the free Lutron Vive app (available for download from the App Store or Google Play®) or by using web-based software.

  • iOS® and Android® Apps – Helper apps act as an intermediary between Vive systems and the Lutron Cloud without the need of a permanent internet connection. It connects to hubs when on-site and passes data back and forth when the smart device reconnects to the Internet. Visit www.lutron.com/ VivePrivacyNotice for more about this data.

    • Registration of jobs / users for extended warranty.
    • Manage multiple jobs with contacts and job info.
    • Invite facility users to have access to hubs / job.
    • Automatically send hand-off documentation personalized to your firm to facility management team. Including programming user guide, online “How-to” videos, and support number.
    • Connection to hub browser user interface for setup. Normal web browser still works and the app is not required.
    • Connection to hub browser dashboard for control and monitor. Normal web browser still works and the app is not required.
    • Backup the database to the Lutron Cloud for hub replacement.
    • Download reports that list the inventory of hubs and devices commissioned in your job.
  • Communicates with controls on a floor using Lutron wireless Clear Connect technology.

  • Distributed system architecture.

    • Wireless sensors and controls must be located within 9 m of the associated device.
  • Supports timeclock events based on both sunrise and sunset or fixed time-of-day.

  • Timeclock events can control individual devices, areas, or groups of areas.

  • Note: This feature is not available once a hub is paired with a Vive Vue server.

  • Uses Lutron RF signal strength measurements to find devices nearby for quick association and programming without having to climb ladders.

  • Dashboard of current status for control and monitoring of the system. Also shows current energy usage.

  • Integrated multi-color LED provides feedback on what mode the hub is in.

  • Connects directly to any smartphone, tablet or computer using built in Wi-Fi. 2.4 GHz 802.11b / g using WPA2 Security.

  • Ethernet 10 / 100 Mbps connection for:

  • Native BACnet® / IP (see Lutron P/N 369996 at www.lutron.com for PIC Statement) integration into Building Management Systems (HNS-2-XX only). The Vive Hub has been tested by BACnet® Testing Laboratories (BTL) and is certified to comply with all necessary interoperability requirements.

  • Network multiple Vive hubs together as an independent system or as part of an existing building network.

  • Native OpenADR® support, to manage Automatic Demand Response / Load Shed events dictated by a utility company.

  • Each Vive hub hosts a unique virtual BACnet® network. As such, each Vive hub requires a unique BACnet® network number.

  • Firmware upgradable for future features and security patches.

  • Password protected access.

  • Flush-mount or surface-mount options available.

  • Supported on most devices that use an HTML5 compliant browser (iOS®, Android®, Windows®, Mac®).

  • Required browsers are Google® Chrome® and Safari®.

  • Supports HTTPS.

  • Recommended configurations for smart devices:

  • Daylighting Setpoint Tweaking – If the lights are too bright or too dim while using daylighting, adjust the settings in real time from a smart device to alter the setpoint for the light level that is maintained between natural and electric light.

  • Daylighting-to-Low-End or Daylighting-to-Off – The Vive system will allow the user to select either daylighting-to-low-end or daylight-to-off on an area by area basis.

  • Customer Supplied Security Certificates

  • Provides customers the abiltiy to load their own authentication certificates for their specific domain.

  • Provides customers using the Vive hub application to use secure browser communications without receiving any authentication warnings due to the self-signed certificates that are shipped with the hubs.

  • Timeclock Occupancy Sensor Settings Changes

  • Requires devices shipped after September 2017. Devices shipped prior to that date will be displayed as “unsupported” in the software UI. Allows timeclock events to change the behavior of occupancy settings based on time of day. For example, change the unoccupied level of corridors / hallways from 25% during the day, and off at night. The following settings can be changed:

  • Occupied Level – The level the lights go to when occupied. Changes are not applied immediately to currently occupied spaces, but will change the next time the space goes occupied to minimize distraction.

  • Unoccupied Level – The level the lights go to when unoccupied. Changes are applied immediately to spaces not currently occupied.

  • Enable / Disable Occupancy – Change whether devices will respond to the occupancy sensor.

  • Timeout of the sensors (requires FC-VSENSOR). LRF5 sensors still require this setting to be set on the sensor.

  • 365-day schedulable timeclock with exceptions for holidays.

  • Allows scheduling events 10 years in advance.

  • Set recurring events with exceptions on holidays.

  • Allows scheduling events on specific day of the year.

  • Calculated energy data for PowPak modules at ±10% accuracy.

  • Create and edit areas.

  • Tune area light levels by trimming the high-end and low-end output.

  • Adjust occupancy settings. Create occupancy groups.

  • User can choose to extend the RF range of up to 15 of the total Pico wireless remotes per Vive hub. These remotes will be able to control any devices within the 22 m range.

  • RF range of occupancy sensors can be extended for up to 14 areas per Vive hub. In a range-extended area, an occupancy sensor can control any device in that area, regardless of distance between sensor and device. Requires Vive hub software 01.09 or higher.

  • Configurable Fade Time

  • Up to 90 minutes for timeclock events and scenes.

  • Limited to 90 seconds for RMNS-DAL32-SZ and RMNS-DAL4-SZ devices.

  • NOTE: This feature is not available once a hub is paired with a Vive Vue server.

  • Up to 90 seconds for Pico remote control programming.

  • Fade time may differ between buttons on the same Pico remote control.

  • Single fade time applies to all programming for a button.

  • Automatic Demand Response / Load Shed

  • Load Shedding will physically dim the lights to a bprogrammable level.

  •  OpenADRR 2.0b compliant.

  • May be enabled (or disabled) via any of the following methods:
    o The first contact closure input (CCI 1)
    o BACnetR integration
    o OpenADRR integration

  • OpenADRR requires access to utility companies over the Internet, so the hub must be connected via Ethernet to use OpenADRR.

  • Alerts View run-time issues which may prevent devices from operating as expected, such as low batteries or missing devices.

  • API Integration

  • To integrate with third-party devices, systems, and software, RESTful APIs are available over the Ethernet.

  • Scenes Scenes can control individual devices, areas, or groups of areas on demand.

  • May be activated via any of the following methods:
    o The second contact closure input (CCI 2)
    o API integration
    o Manual activation in the app

  • Programmable CCI

  • The second contact closure input (CCI 2) can be programmed to activate a scene.

  • Scene activation
    o Set a scene to activate using second contact closure input (CCI 2) on the Vive hub.
    o Requires Vive hub software 01.13 or higher.

  • Occupancy Dependency

  • Occupancy sensors in one room/area can control devices in other rooms/areas.

  • Radio Power Saver occupancy sensors only.

  • Requires Vive hub software 01.14 or higher.

Specifications

Regulatory Approvals

  • WPC
  • Compliant to IEC 62368-1

Power / Performance

  • Input to power supply: 100–277 V~ 50 / 60 Hz 0.7 A at 230 V~
  • Input to Vive hub:
    24 V- 350 mA

System Limits

  • HNS-1, HNS-2 support up to 700 Lutron Wireless devices. HNS-0 supports up to 75 Lutron

Wireless devices.

  • Any given load device can be controlled by 10 occupancy sensors, 10 Pico remote controls and 1 daylight sensor (Pico remote controls and sensors must be located within 9 m of the load device they are controlling).

Metal Ceiling Mounting

  • Metal ceiling grids must have a > 3 mm gap of non-metal material which extends the entire length of the tile on at least one edge. This is often achieved by foam spacers that are used to prevent tile-to-tile rattling.
  • Metal ceiling grids which are continuous (with no gap) or those that are interlocked, must have a total surface area that is less than 81 m2 for each section. The overall space can be larger as long as there are non-metal sections bordering or intersecting the metal sections.
  • Do not install the Vive hub above metal ceilings or tiles with a metal backing.

Mounting

  • Mount the Lutron QSPS-DH-1-75 power supply in a thirdparty DIN-style enclosure (IP20 minimum).
  • The power supply must be mounted within 150 m of the Vive hub when using 1.0 mm2 (18 AWG) minimum low-voltage wiring.

Environment

  • For indoor use only.
  • 0 °C to 40 °C.
  • Relative humidity less than 90% non-condensing.

Contact Closure Input Terminals

  • First contact closure input (CCI 1) is to be used for initiating load shed only.
  • The second contact closure input (CCI 2) may be programmed to activate a scene. If activating a scene, a “deactivation” behavior may be set in the scene in order to set two behaviors for the one input.
  • Accepts only maintained inputs.
  • Off-state leakage current must be less than 100 μA.
  • Open circuit voltage: 24 V- maximum.
  • Input wiring: 0.2 mm2 to 2.5 mm2 (24 AWG to 12 AWG).
  • Contact Closure Inputs on multiple hubs can be wired in parallel. DO NOT wire inputs in parallel with other equipment as it can cause the inputs on either of the devices to falsely trigger.
  • Up to 4 hubs in parallel.
  • To ensure proper operation of Contact Closure Inputs, a QSPS-DH-1-75 power supply may not be used to provide power to more than one hub.
  • Inputs must be dry contact closure, solid state, open collector, or active-low (NPN) / active high (PNP) output.
  • Open collector NPN or active-low on-state voltage must be less than 2 V and sink 3.0 mA.
  • Open collector PNP or active-high on-state voltage must be greater than 12 V and source 3.0 mA.

Programming
The Vive Hub is meant to be permanently installed. It is not intended to be used as a programming tool that can be removed from the site after commissioning. Various Vive system features are dependent on the hub for proper functionality. In addition, users and other maintainers will be forced to recommission the entire system in order to make simple changes or additions if the hub is not installed on-site as part of the commissioned system.

Warranty
1-year limited warranty. The customer can register the product to increase the warranty period from 1 year to 5 years. Please visit Limited Comm [PDF]

How to Build a Model Number

Frequency
N = 865.500 – 866.500 MHz (India)
Type
0 = Starter Vive hub without BACnetR limited to 75 devices.
1 = Vive hub without BACnetR
2 = Premium Vive hub with BACnetR
Mounting
FM = Flush-Mount (non-metal ceiling tiles or drywall)
Replacement Part Model Numbers
QSPS-DH-1-75 Vive hub external power supply
H-MOUNT-FM Flush-mount installation adapter
H-MOUNT-SM Surface-mount installation adapter.

Dimensions
Dimensions are shown as: mmimage 3

Range with multiple Vive hubs
All wireless devices to be associated to the Vive hub must be within 22 m of the Vive hub and must be on the same floor as the Vive hub.
Note: Vive hubs should be mounted greater than 3 m apart on the same floor.
Note: Lutron requires that the Vive hub not be installed above metal ceilings or tiles with a metal backing.
Note: A corporate Wi-Fi network can interfere with the Wi-Fi on the Vive hub. Where a corporate Wi-Fi network exists, it is recommended to do the following:
Connect the Vive hub to the corporate network using the Ethernet connection on the hub and disable Wi-Fi on the hub.
Note: Vive hubs should be mounted greater than 3 m from a Wi-Fi router or access point.image 4

Wiring and Mounting

image 5

Product Overview

image 6image
7

Vive Security Statement

Lutron takes the security of the Vive Lighting Control System very seriously. The Vive Lighting Control System has been designed and engineered with attention to security since its inception. Lutron has engaged security experts and independent testing firms throughout the entire development of the Vive Lighting Control System. Lutron is committed to security and continuous improvement throughout the Vive product lifecycle.
The Vive Lighting Control System uses a multi-tiered approach to security. They include:

  1. An architecture that isolates the wired Ethernet network from the wireless network, which strictly limits the possibility of the Vive Wi-Fi being used to access the corporate network and gain confidential information

  2. A distributed security architecture with each hub having its own unique keys that would limit any potential breach to only a small area of the system

  3. Multiple levels of password protection (Wi-Fi network and the hubs themselves), with built-in rules that force the user to enter a strong password

  4. ISO-recommended best practices including salting and SCrypt for securely storing usernames and passwords

  5. AES 128-bit encryption for network communications

  6. HTTPS (TLS 1.2) protocol for securing connections to the hub over the wired network

  7. WPA2 technology for securing connections to the hub over the Wi-Fi network

  8. Azure provided encryption-at-rest technologies.
    The Vive hub can be deployed in one of two ways:

    • Dedicated Lutron Network
    • Connected to the corporate IT network via Ethernet. The Vive hub must be connected via Ethernet to access certain features such as BACnet® for BMS integration or OpenADRR integration. Lutron advises following best practices in this instance, including separating the business information network and the building infrastructure network. Use of a VLAN or physically separated networks is recommended for secure deployment.

Dedicated Lutron Network Deployment
The Vive hub is not connected to the building network. Wi-Fi is used to connect to a smart device such as a phone, tablet, or PC for commissioning and configuration only. The Vive hub serves web pages for setup and maintenance via a password-protected connection. The Wi-Fi SSID can be set to not broadcast. The Vive hub Wi-Fi may be disabled if desired.

Corporate IT Network Deployment
The Vive hub may be deployed with a fixed Ethernet IP address or served over DHCP. The Vive hub reserves the IP subnet 192.168.3.0/24 for its Wi-Fi, so the hub cannot be assigned an Ethernet IP address in that range. Once the IT network is operational, the Vive hub will serve password-protected web pages for access and maintenance. The Vive hub Wi-Fi may be disabled if desired. The Vive hub acts as a Wi-Fi access point purely for the configuration and commissioning of the Vive system. It is not a substitute for your building’s normal Wi-Fi access point. The Vive hub does not act as a bridge between wireless and wired networks. It is strongly recommended that local IT security professionals be involved with the network configuration and set-up to ensure the installation meets their security needs.

Security

**

image 8**

Ports Used

Traffic Port Type Connection Description
Outbound 47808

(configurable)

| UDP| Ethernet| Used for BACnet® integration into Building Management Systems
80| TCP| | Used to discover the Vive hub when mDNS is not available
5353| UDP| Ethernet| Used to discover the Vive hub via mDNS
Configurable| TCP| Ethernet| Used for OpenADRR. Specified by utility company
Inbound| 443| TCP| Both Ethernet and Wi-Fi| Used to serve user interface to smart device
80| TCP| | Used by other Vive hubs to proxy
8081| TCP| Ethernet| Used for local LEAP connections to integrations and Vive Vue
8083| TCP| Ethernet| Used for local LAP connections to integrations and Vive Vue
8444| TCP| Ethernet| Used to communicate with the Vive Vue server
47808

(configurable)

| UDP| Ethernet| Used for BACnet® integration into Building Management Systems
5353| UDP| Ethernet| Used to discover the Vive hub via mDNS

Corporate Network (continued)image 9

Ports Used

Traffic Port Type Connection Description
Outbound 47808

(configurable)

| UDP| Ethernet| Used for BACnet® integration into Building Management Systems
80| TCP| | Used to discover the Vive hub when mDNS is not available
5353| UDP| Ethernet| Used to discover the Vive hub via mDNS
Configurable| TCP| Ethernet| Used for OpenADRR. Specified by utility company
Inbound| 443| TCP| Both Ethernet and Wi-Fi| Used to serve user interface to smart device
80| TCP| | Used by other Vive hubs to proxy
8081| TCP| Ethernet| Used for local LEAP connections to integrations and Vive Vue
8083| TCP| Ethernet| Used for local LAP connections to integrations and Vive Vue
8444| TCP| Ethernet| Used to communicate with the Vive Vue server
47808

(configurable)

| UDP| Ethernet| Used for BACnet® integration into Building Management Systems
5353| UDP| Ethernet| Used to discover the Vive hub via mDNS

Inter-Hub Link Wiring

Notes

  • The inter-hub wiring is rated IEC PELV.
  • Wiring distance for any single link segment is 100 m max; use third-party Ethernet switches for longer distances.
  • Up to 64 hubs can be networked together.
  • Up to 100 hubs can be networked together when Vive Vue is used.
  • Hubs communicate over the inter-hub link using multicast UDP or TCP; a dedicated network is recommended but not required.
  • The Wi-Fi access port cannot be used to create an ad hoc network for use as the inter-hub communication link.

Compatible Devices

  • PowPak Modules

    • RMNS-DAL32-SZ
    • RMNS-DAL4-SZ
    • RMNS-8T-DV-B
    • RMNS-16R-DV-B
    • RMNS-CCO1-24-B
  • Pico Remote Controls
    (“XX” indicates colour code — AW: Arctic White or BL: Black)

    • PN2-2B-TXX-L01
    • PN2-2BRL-TXX-L01
    • PN2-3B-TXX-L01
    • PN2-3BRL-TXX-L01
    • PN2-4B-TXX-L01 1
    • PN2-4B-TXX-L21 1
    • PN2-4B-TXX-L31 1
    • PN2-4B-TXX-EL1 1
    • PN2-4B-TXX-EL2 1
    • PN2-4B-TXX-P04 1
  • Wireless Occupancy and Daylight Sensors

    • LRF5-DCRB
    • LRF5-OCR2B-P
    • LRF5-OHLB-P
    • LRF5-OKLB-P
    • LRF5-OWLB-P
  • In-Line Phase Control Dimmers 2

    • RMNS-250NE
  1. Button programming is only for all devices paired to the Pico wireless control. These Pico wireless controls are unable to have their buttons be individually assigned to different rooms.
  2. Requires Vive hub software 01.12 or higher.

Lutron, Lutron, Clear Connect, Pico, PowPak, Radio Powr Savr, Vive Vue, and Vive are trademarks or registered trademarks of Lutron Electronics Co., Inc. in the US and/or
other countries. Mac, Safari, and iPhone are trademarks of Apple Inc., registered in the U.S. and other countries. App Store is a service mark of Apple Inc., registered in the U.S. and other countries. All other product names, logos, and brands are property of their respective owners.

References

Read User Manual Online (PDF format)

Loading......

Download This Manual (PDF format)

Download this manual  >>

Vive User Manuals

Related Manuals