8.4.2. Sub Static Controller (SSC)¶
The Sub Static Controller Role Type is intended for static controllers which are not suitable as central controllers. It is aimed at applications that require a static controller to manage a subset of nodes. It is typically offered as a bundled package with e.g. sensors.
8.4.2.1. SSC Protocol Requirements¶
\requirement{RT:02.11.0001.1}{0}
The SSC MUST respect requirements described in Section 8.2
\requirement{RT:02.11.0002.1}{0}
The SSC MUST be mains powered and MAY have battery back-up.
\requirement{RT:02.11.0003.1}{0}
The SSC MUST set the listening flag to 1 in its NIF.
\requirement{RT:02.11.0004.1}{0}
The SSC MUST NOT support the SIS functionality.
\requirement{RT:02.12.0001.1}{0}
The SSC SHOULD NOT configure lifeline associations.
\requirement{RT:02.11.0005.1}{0}
The SSC MUST support the following network roles:
Primary controller
Secondary controller
Inclusion controller
8.4.2.1.1. If first node in the network¶
\requirement{RT:02.11.0006.1}{0}
If the SSC is the first node in the network, it MUST take the Primary Controller role and MUST support the following network functions:
Include new nodes (“Add mode”)
Exclude nodes
Learn mode
\requirement{RT:02.11.0007.1}{0}
It MUST NOT be possible to activate Learn Mode if the SSC is the Primary Controller and other nodes are included in the network.
8.4.2.2. SSC Setup¶
8.4.2.2.1. Inclusion process¶
\requirement{RT:02.12.0002.1}{0}
It is RECOMMENDED to use a physical push button for activating learn mode and a soft button for activating add mode on a SSC Role Type.
8.4.2.2.2. Lifeline configuration¶
No requirement
8.4.2.2.3. SSC including a CSC¶
\requirement{RT:02.11.0008.1}{0}
If the SSC is the Primary Controller and a CSC is added to the network, the SSC MUST assign the SIS role to the CSC.
\requirement{RT:02.13.0001.1}{0}
If the SSC is the Primary Controller and has previously included some Wake Up nodes, it MAY re-assign the Wake Up destination NodeID to the CSC/SIS for the previously included Wake Up nodes at the next Wake Up Notification.
\requirement{RT:02.11.0009.1}{0}
The SSC becomes an inclusion controller and MUST support the following network functions:
Include new modes (“Add mode”)
Exclude nodes
Learn mode
Battery considerations
None.
8.4.2.2.4. SSC including an RPC, PEN, RSEN or WOEEN¶
\requirement{RT:02.12.0003.1}{0} \requirement{RT:02.11.000A.1}{8}
If there is a SIS in the network, the SSC SHOULD NOT send a Wake Up Interval Set Command to the included node. If there is a SIS in a network and the SSC sends a Wake Up Interval Set Command, the destination NodeID MUST be the SIS’ NodeID.
\requirement{RT:02.12.0004.1}{0} \requirement{RT:02.11.000B.1}{4}
If there is no SIS present in the network, the SSC SHOULD send a Wake Up Interval Set Command with its own NodeID as destination. If issuing a Wake Up Interval Set Command, the SSC MUST respect the following rules:
\requirement{RT:02.12.0005.1}{4}
If the included node is of Role Type RPC, PEN or RSEN:
The SSC SHOULD set the Wake Up Interval Set Command Seconds field to the default Wake Up time advertised by the included node.
\requirement{RT:02.11.000C.1}{8}
If the included node is of Role Type PEN:
If the node advertises Wake-Up Capabilities (Wake-Up Command Class, version 2 or newer), the Wake Up Interval Set Command Seconds field MUST be within the allowed range.
8.4.2.2.5. SSC including an SSC, PC, AOEN, LSEN, or NAEN¶
Battery considerations
None.
8.4.2.3. SSC Runtime Configuration¶
No requirements.
8.4.2.4. SSC Runtime communication¶
No requirements.
