2.2.25. Central Scene Command Class, version 3¶

The Central Scene Command Class, version 3 extends version 2 by adding a new mode for the transmission of Key Held Down notifications. This allows a node to send Key Held Down refreshes at a low rate for the duration of the key held down.

The purpose of this new feature is to provide improved compatibility with FLiRS beaming and network routing.

Central Scene Command Class, version 3 introduces three new commands to allow a controller to query and configure node capabilities.

Central Scene Configuration Set Command
Central Scene Configuration Get Command
Central Scene Configuration Report Command

Central Scene Command Class, version 3 extends the following commands for a scene launching node to advertise its optional capabilities.

Central Scene Supported Report Command
Central Scene Notification Command

2.2.25.1. Compatibility considerations¶

\requirement{CC:005B.03.00.22.001}{0}

A scene controller SHOULD NOT try to detect multiple key presses from the reception of successive key press notifications in any single or multiple key attribute combination. FLiRS beaming, collisions or routing may add delays between messages and render the timing between notifications unreliable.

Version 1 and version 2 required to send Key Held Down notifications commands every 200ms. It has been found that this requirement cannot be observed when the network is using FLiRS beaming or routing. Further, issuing the 200ms refreshes also degrades general network reliability and availability.

Version 3 introduces the Slow Refresh Capability, which allows a node to send refreshes every 55 seconds instead of 200ms. For details about the Slow Refresh capability, refer to Section 2.2.25.7.

\requirement{CC:005B.03.00.21.001}{0}

In order to ensure a functioning network, the Slow Refresh capability MUST be enabled by default after inclusion.

\requirement{CC:005B.03.00.22.002}{0}

When creating associations from a version 3 node, the node creating the association SHOULD enable the Slow Refresh capability in the node if the association destination does also support Central Scene Command Class, version 3. When using the version 3 Slow Refresh capability, the controller relies on the reception of a Key Up notification instead of the Key Held Down refreshes. The new mode still sends refreshes at a low rate, for the controller to detect if a node failed after sending a Held Down Key notification. This means that a version 2 controlling node may time out when receiving Key Held Down Notifications from a version 3 node.

However, it has been found that there exist nodes supporting version 1 or version 2 which do not send Central Scene Notification refreshes every 200ms when the Key Held Down notification is issued.

\requirement{CC:005B.03.00.22.003}{0}

A controller SHOULD apply an adaptive approach based on the reception of the Key Released Notification. Initially, the controller SHOULD time out if not receiving any Key Held Down Notification refresh after 400ms and consider this to be a Key Up Notification. If, however, the controller subsequently receives a Key Released Notification, the controller SHOULD consider the sending node to be operating with the Slow Refresh capability enabled.

2.2.25.1.1. Central Scene Configuration commands support¶

If a node supports Slow Refresh Capability (that allows a node to send refresh every 55 seconds instead of 200 ms), may not allow users to turn off the ‘Slow Refresh’ functionality. If this is the case, the node MAY choose to ignore the Central Scene Configuration Set Command with ‘Slow Refresh’ bit set to zero.

If the node chooses to ignore the Central Scene Configuration Set Command, the node MUST return an application Reject Request Command when receiving Central Scene Configuration Set command (if it received without Supervision encapsulation).

2.2.25.1.2. Multi Channel considerations¶

\requirement{CC:005B.03.00.22.004}{0}

Multi Channel End Points SHOULD NOT support the Central Scene Command Class.

2.2.25.2. Central Scene Configuration Set Command¶

This command is used to configure the use of optional node capabilities for scene notifications.

Table 2.121 Central Scene Configuration Set Command¶
7	6	5	4	3	2	1	0
Command Class = COMMAND_CLASS_CENTRAL_SCENE (0x5B)
Command = CENTRAL_SCENE_CONFIGURATION_SET (0x04)
Slow Refresh	Reserved

Slow Refresh (1 bit)

This flag is used to configure the use of the Slow Refresh capability.

\requirement{CC:005B.03.04.11.001}{0}

The value 1 MUST indicate that the scene launching node MUST use Slow Refresh.

The value 0 MUST indicate that the scene launching node MUST NOT use Slow Refresh.

Reserved

\requirement{CC:005B.03.04.11.002}{0}

This field MUST be set to 0 by a sending node and MUST be ignored by a receiving node.

2.2.25.3. Central Scene Configuration Get Command¶

This command is used to query the configuration of optional node capabilities for scene notifications.

\requirement{CC:005B.03.05.11.001}{0}

The Central Scene Configuration Report Command MUST be returned in response to this command.

\requirement{CC:005B.03.05.11.002}{0}

This command MUST NOT be issued via multicast addressing.

A receiving node MUST NOT return a response if this command is received via multicast addressing. The Z-Wave Multicast frame, the broadcast NodeID and the Multi Channel multi-End Point destination are all considered multicast addressing methods.

Table 2.122 Central Scene Configuration Get Command¶
7	6	5	4	3	2	1	0
Command Class = COMMAND_CLASS_CENTRAL_SCENE (0x5B)
Command = CENTRAL_SCENE_CONFIGURATION_GET (0x05)

2.2.25.4. Central Scene Configuration Report Command¶

This command is used to advertise the configuration of optional node capabilities for scene notifications.

Table 2.123 Central Scene Configuration Report Command¶
7	6	5	4	3	2	1	0
Command Class = COMMAND_CLASS_CENTRAL_SCENE (0x5B)
Command = CENTRAL_SCENE_CONFIGURATION_REPORT (0x06)
Slow Refresh	Reserved

Slow Refresh (1 bit)

This flag is used to advertise the use of the Slow Refresh capability.

\requirement{CC:005B.03.06.11.001}{0}

The value 1 MUST indicate that the scene launching node MUST use Slow Refresh.

The value 0 MUST indicate that the scene launching node MUST NOT use Slow Refresh capability.

Reserved

\requirement{CC:005B.03.06.11.002}{0}

This field MUST be set to 0 by a sending node and MUST be ignored by a receiving node.

2.2.25.5. Central Scene Supported Get Command¶

This command is used to request the maximum number of scenes that this device supports.

\requirement{CC:005B.03.01.11.001}{0}

The Central Scene Supported Report Command MUST be returned in response to this command.

\requirement{CC:005B.03.01.11.002}{0}

This command MUST NOT be issued via multicast addressing.

A receiving node MUST NOT return a response if this command is received via multicast addressing. The Z-Wave Multicast frame, the broadcast NodeID and the Multi Channel multi-End Point destination are all considered multicast addressing methods.

Table 2.124 Central Scene Supported Get Command, version 3¶
7	6	5	4	3	2	1	0
Command Class = COMMAND_CLASS_CENTRAL_SCENE (0x5B)
Command = CENTRAL_SCENE_SUPPORTED_GET (0x01)

2.2.25.6. Central Scene Supported Report Command¶

This command is used to report the maximum number of supported scenes and the Key Attributes supported for each scene.

Table 2.125 Central Scene Supported Report Command, version 3¶
7	6	2	0
Command Class = COMMAND_CLASS_CENTRAL_SCENE (0x5B)
Command = CENTRAL_SCENE_SUPPORTED_REPORT (0x02)
Supported Scenes
Slow Refresh Support	Reserved	Number of Bit Mask Bytes	Identical
Supported Key Attributes for Scene 1 - Byte 1
…
Supported Key Attributes for Scene 1 - Byte N
…
Supported Key Attributes for Scene M - Byte 1
…
Supported Key Attributes for Scene M - Byte N

All fields not described below are the same as in version 2.

Slow Refresh Support (1 bit)

This field indicates whether the node supports the Slow Refresh capability.

\requirement{CC:005B.03.02.11.001}{0}

The value 1 MUST indicate that the node supports the Slow Refresh capability.

The value 0 MUST indicate that the node does not support the Slow Refresh capability.

2.2.25.7. Central Scene Notification Command¶

This command is used to advertise a key event.

\requirement{CC:005B.03.03.11.001}{0}

If the device implements Z-Wave Plus Lifeline support, the device MUST send the Central Scene Notification Command to the actual Lifeline targets.

Table 2.126 Central Scene Notification Command, version 3¶
7	6	2
Command Class = COMMAND_CLASS_CENTRAL_SCENE (0x5B)
Command = CENTRAL_SCENE_NOTIFICATION (0x03)
Sequence Number
Slow Refresh	Reserved	Key Attribute
Scene Number

All fields not described below are the same as in version 2.

Slow Refresh (1 bit)

\requirement{CC:005B.03.03.11.002}{4}

This flag is used to advertise if the node is sending Key Held Down notifications at a slow rate. A sending node MUST always set this field according to the configured mode.

\requirement{CC:005B.03.03.11.003}{0}

A receiving node MUST ignore this field if the command is not carrying the Key Held Down key attribute.

If the Slow Refresh field is 0:

\requirement{CC:005B.03.03.12.002}{0}

A new Key Held Down notification SHOULD be sent every 200ms until the key is released.

\requirement{CC:005B.03.03.11.005}{0}

The Sequence Number field MUST be updated at each notification transmission.

\requirement{CC:005B.03.03.12.001}{0}

If not receiving a new Key Held Down notification within 400ms, a controlling node SHOULD use an adaptive timeout approach as described in Section 2.2.25.1.

If the Slow Refresh field is 1:

\requirement{CC:005B.03.03.11.006}{0}

A new Key Held Down notification MUST be sent every 55 seconds until the key is released.

\requirement{CC:005B.03.03.11.007}{0}

The Sequence Number field MUST be updated at each notification refresh.

\requirement{CC:005B.03.03.11.008}{4}

If not receiving a new Key Held Down notification within 60 seconds after the most recent Key Held Down notification, a receiving node MUST respond as if it received a Key Release notification.