Docs update for exposing scenes and setting scene name

[Koenkk]

See Koenkk/zigbee2mqtt#9056

[sjorge]

Is this name only use for the frontend? As there is also a scenename attribute in the ZCL so if the same constraint is used it can probably be written to the device as wel! (and retrieved if that ever gets implemented)

[Koenkk]

Yes it will be used in the frontend, @nurikk just added it.

I know scene names can be written to a device, however I don't see the benefit of it and I don't know if all devices support this.

[sjorge]

My original though was so you can read it out later or from devices that were paired on a different coördinator before. But that would make no sense as it seems the scenes table gets wiped when you reset the device to pair it. Kind of weird thing to have in the zcl come to think of it. ~ sjorge

…

On 8 Oct 2021, at 16:17, Koen Kanters ***@***.***> wrote:  @Koenkk commented on this pull request. In docs/information/scenes.md: > @@ -9,6 +9,7 @@ Scenes can be created in two ways, by storing the current state (`scene_store`) ### `scene_store` This is the easiest way to create a scene. First set the device or group in the desired state. Next store the current state as a scene by sending a command to `zigbee2mqtt/[GROUP_OR_DEVICE_FRIENDLY_NAME]/set` with payload `{"scene_store": SCENE_ID}` where `SCENE_ID` is a number (e.g. `1`). +To also provide a name for the scene (shown in e.g. the frontend) send e.g. `{"scene_store": {"ID": 1, "name": "My scene"}}`. Yes it will be used in the frontend, @nurikk just added it. I know scene names can be written to a device, however I don't see the benefit of it and I don't know if all devices support this. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.