A couple of different responses here, but I’m going put them all in one post.
1) Local Scene Control was defined as always being actuated by a physical action (typically a button press) on the local controller. To the best of my knowledge, there is no way to send a command to a local scene controller to tell it to initiate the scene.
2) there are seven local scene command sets.
The first one is what is used on a daily basis to launch the scene. Press a button on the local scene controller, it tells the end devices to launch that scene.
A) Scene Activation Set. Launches the scene each time. May be multicast. Sent by the local controller to the devices in the scene. ( again, the official spec does not include any way to turn a scene off.).
The next three are used by the local controller to set up the end devices so that they know what they are supposed to do when a specific scene activation set is received. So for Lamp A, Scene 12 means “turn on at 50%.” For lamp B, Scene 12 means “turn on at 75%.”
B) Scene Actuator Configuration Set. Cannot be multicast (it will be ignored if it is). Sent by a controller to a device in the scene with the values that device should use for that scene.
C) Scene Actuator Configuration Get. Cannot be multicast (it will be ignored if it is). Sent by a controller to a device in the scene to request what values are set in that end device for that scene. If The scene ID is “0” then the values for the current scene will be returned.
D) Scene Actuator Configuration Report. This is the response from the end device to the scene actuator configuration get.
The last three are used by the primary controller to map the buttons on the local controller to the specific scenes. So pressing button one on the local controller should launch scene 12. Pressing button two on the local controller should launch scene 15. And so on. Note that this is different than association, where the groups are just numbered one, two, three.
Again, the idea of local scenes was that they would be created through the primary controller and then assigned to various local controllers, so they might’ve been created in a way that didn’t map sequentially to the local controller’s buttons, which was fine. This is how vera and homeseer work.
E) Scene Controller Configuration Set. This is how the hub maps the physical buttons on a local scene controller after the scene is created by the primary controller. Last time I looked this was not supported by SmartThings, but maybe it’s changed. Cannot be multicast.
F) Scene Controller Configuration Get. The primary controller queries a local scene controller for its current button settings. Cannot be multicast. Scene ID cannot be “0” because this isn’t about the commands mapped to the scenes, it’s about the scenes mapped to the buttons. So there’s no “current scene.”
G) Scene Controller Configuration Report. The local scene controller response to the scene controller configuration get.