Overview

The following figure summarizes the ISI Occupancy Sensor profile inputs and outputs.

This profile was generated automatically by the NodeBuilder® Resource Report Generator.

Use Cases

The following sections summarize the use cases supported by the Occupancy Sensor profile.

Required Use Cases

The following list summarizes the required use cases for the Occupancy Sensor profile.

• Monitor occupancy for an area.
• Provide a network output that can be used to control lamps, blinds, and shades based on the occupancy state of all the occupancy sensors in a zone.
• Provide a second network output that can be used by a user interface application to montior the occupancy state of the area monitored by the occupancy sensor.
• Report an area as occupied if occupancy is detected in the area monitored by the occupancy sensor.
• Report an area as unoccupied on the occupancy output if occupancy is not detected, and a configurable period has passed since the last transition to the unoccupied state.
• Support a test mode where the occupancy sensor is controlled solely by the hardware detection circuit. This simplifies verification of correct placement and aiming of the occupancy sensor.
• Store a friendly name assigned by a user interface device for the occupancy sensor.
• Report power consumption of the occupancy sensor hardware.

Optional Use Cases

The following list summarizes the optional use cases for the Occupancy Sensor profile.

• Report electrical energy usage of the occupancy sensor hardware.
• Specify a heartbeat rate for any of the outputs.
• Specify an update throttle for the any of the outputs.
• Specify a major and minor model number for the functional block implementation.
• Store a friendly name for the occupancy sensor location (for example, the room name).

Functional Requirements

An occupancy sensor reports one of two states--either occupied or unoccupied. These states are reported using two outputs. The occupancy sensor includes a feedback input from other occupancy sensors. All connected occupancy sensors create a zone. For example, all occupancy sensors within a large room may be connected to create a single zone for the room. One of the outputs from each of the occupancy sensors in a zone is used to control all lights, blinds, and shades that are connected to the zone. This output debounces the hardware detection circuit, holds off reporting a zone as unoccupied for a configurable period after occupancy is no longer detected, and does not report a zone as unoccupied if feedback is received indicating that the zone is occupied. The second output only reports the occupancy state for the area monitored by the occupancy sensor. This output debounces the hardware detection, but does not include a hold delay time, and does not take into account other connected occupancy sensors.

To keep multiple occupancy sensors in zone synchronized, all occupancy sensors will periodically update their switch outputs based on a heartbeat interval. By default, the heartbeat interval will be 2 minutes when occupied, and 20 minutes when not occupied. These intervals may be configurable. While reporting an area as unoccupied via the switch output, do not propagate the output unless more than 3 minutes has passed since the last report that the area is occupied is received via the feedback input.

The following diagram illustrates the relative timing of the hardware occupancy detection, the calculated occupancy, and the two network outputs from the occupancy sensor.

ISI Requirements

Devices implementing the ISI Occupancy Sensor profile must implement the interoperable self-installation (ISI) protocol. A functional block implementing this profile must support manual and controlled enrollment with one assembly as described in this section, and may optionally support automatic enrollment for use by UI or gateway applications, and may also support additional assemblies.

A functional block implementing the ISI Occupancy Sensor profile will typically be connected with functional blocks implementing one or more of the following functional profiles (functional blocks implementing other profiles may also be connected):

• ISI Keypad Profile
• ISI Lamp and Appliance Module Profile
• ISI Monitor Point Profile
• ISI Occupancy Sensor Profile
• ISI Sunblind Actuator Profile
• ISI Thermostat Profile

A device implementing this profile must include a Connect button for each occupancy sensor functional block. An occupancy sensor device may implement multiple occupancy sensor functional blocks, in which case it will have one Connect button for each functional block. When a Connect button is pressed or an isiOpen controlled enrollment request is received from an enrollment controller, a CSMO message will be broadcast with the values listed in the Offered Value column in the following table. The offered assembly will consist of the nvoSwitch and nviSwitchFb functional block members sharing assembly member number 1.

When a CSMO message is received by an application implementing this profile, the connection invitation will be provisionally approved if the fields of the CSMO message match the Accepted Value column in the following table. A provisionally approved connection invitation will be accepted if the user presses the Connect button, or if an isiCreate controlled enrollment request is received from an enrollment controller.