38
39
06 element #6: six bytes
40
02 InputAndOptions: 0x02
41
03 Transition: any -> released
42
03 Source: Endpoint #3 (hosts tertiary scene client cluster on C4)
43
05 00 Cluster ID: 0x0005 - scenes
44
05 44 33 22 ZCL Command Template: Recall scene, group ID = 0x3344, scene ID =
0x22
45
46
06 element #7: six bytes
47
03 InputAndOptions: 0x03
48
0D Transition: released -> pressed
49
04 Source: Endpoint #4 (hosts quaternary scene client cluster on C4)
50
05 00 Cluster ID: 0x0005 - scenes
51
05 66 55 77 ZCL Command Template: Recall scene, group ID = 0x5566, scene ID =
0x77
52
53
06 element #8: six bytes
54
03 InputAndOptions: 0x03
55
03 Transition: any -> released
56
04 Source: Endpoint #4 (hosts quaternary scene client cluster on C4)
57
05 00 Cluster ID: 0x0005 - scenes
58
05 99 88 aa ZCL Command Template: Recall scene, group ID = 0x8899, scene ID =
0xaa
3.11. Single Momentary Switch (Push Button) as Scene Selector Switch
Related C++ class: CZigBeeDeviceSetupInputPatternPushScene.
This recipe allows to recall one or two scenes, i.e. one for a short press and optionally one for a long
press. In contrast to all other input actions, a recall scene command will always be sent as groupcast
to the group specified in the payload of the recall scene command.
The idea is that each transition from the pressed state to the released state fires a “recall scene”
command for one scene and a transition to the pressed state to the kept-pressed state fires a “recall
scene” command for another scene.
3.11.1. Example
This would be a configuration for C4, which assigns each of the four inputs as a stationary switch
(two stable positions) to a corresponding scene cluster instance on the primary, secondary, tertiary,
and quaternary level control switch endpoints. Each switch can recall two separate scenes (they need
not address the same group). Contrary to all other examples, no binding is required here on the
source endpoint to targets. This is to allow mixing groups and making sure the group address for the
multicast matches the group in the payload. The shown configuration must be written to the
InputActions attribute:
1
41 element type: 0x41 (raw data)
2
08 00 element count: 0x0008 (8 entries)
3
4
06 element #1: six bytes
5
00 InputAndOptions: 0x00
6
07 Transition: pressed -> released
7
01 Source: Endpoint #1 (hosts primary scene client cluster on C4)
8
05 00 Cluster ID: 0x0005 - scenes
17