Configuring Devices

The STR Template Library contains many preconfigured devices to make commissioning your project faster and easier. The following sections explain what to keep in mind for various devices you may use on your project.

Sensors

Occupancy sensors in a guestroom typically live and operate in area 2. The only exception is for an additional AntiStumble zone. Because the motion table is quite complicated, we recommend that you simply copy the settings from the Library file.

If PMS and/or Access Control (door lock) integrations exist the sensors will differentiate between guest and staff occupancy and will have different timeouts. The customer can adjust these timeouts from the dashboard.

Not all sensors have the same configuration. There are three different sensor configurations, and it is important to copy the right type onto the right sensor.

Sensor Types
Bedroom	Use for any sensor that can see someone sleeping so should not be part of AntiStumble Logic
Bathroom	Use for any sensor that is part of AntiStumble but not a bedside sensor
AntiStumble	Use for Bedside AntiStumble sensors

If you are not using AntiStumble, it is ok to apply the Bedroom configuration to all sensors. When using AntiStumble, make sure you tweak which tasks are fired during AntiStumble based on which side of the bed the sensor is on.

If you would like a sensor to also turn on/off lights (like a typical vacancy sensor) refer to Signify Knowledge Base Article KB00114820: STR - Occupancy Sensing to automate bathroom lighting.

UIs and Dry Contact Switches

Ensure that any buttons controlling lighting have their BLA set to area 16 so they will track correctly during automated sequences.

There are task templates on the various UIs for common requirements:

Thermostat

Controls page change and language change logic

Window Coverings

Provides logic for OneTouch curtain control and discrete Open/Close buttons

Nightlight Mode

Provides logic for changing nightlight modes

Wake-Up Lighting

Allows the PADPA (AntumbraDisplay) to be used as an alarm clock

Load Controllers

For the most part load controllers are configured the same way as any other Dynalite project. The main consideration is that all lighting channels need their BLA set to area 16.

You may use joins if needed, but many integrations do not check join values and may not work correctly.

Do not use preset excludes to make one area encompass many lighting zones. Room tiles, UI buttons, and integrations do not track preset excludes and will not function correctly. If necessary, segregate logical groupings using areas.

DDRC-GRMS-E Room Controller

Lighting on the GRMS controller should be configured like any other load controller but it has two sets of dipswitches that configure the network communications.

ID1 sets the units box number and by extension the area offset. Typically, this is set to match the room number on the floor to make configuration easier on the installer. The area offset will be the value of ID1(box number) +1*20. So a dipswitch setting of 1 for room one would have an area range of 40-59.

ID2 sets which floor gateway the unit will communicate through. Typically, this is set to match the floor number to make configuration easier on the installer. There is a gateway mapping table that tells the controller which IP address is associated with which dipswitch setting.

Fan Coil Unit Controllers (FCUC)

The DDFCUC) has firmware limitations that require workarounds to fit into an STR project. This is why they are configured in a room-only area and use a task template to function correctly.

For example, HVAC Zone 1 uses area 17 for the dashboard and thermostat, and area 217 for DDFCUC configuration and tasking.

STR uses a large fan speed table that includes Auto and Off as states, while the DDFCUC uses the Fan configuration type and Manual fan control (Enabled/Disabled) properties to determine fan operation. The task template on the DDFCUC aligns these two different ways of working.