Support for controlling LED (RGB) in Shelly Plug devices? (Plus Plug S, Plug Gen3, ...)

[lukasMega]

Just asking, it would be nice feature.
I would like to reflect some state in Shelly Plug RGB light via Node-RED. Currently I'm using raw HTTP GET: https://shelly-api-docs.shelly.cloud/gen2/Devices/Gen3/ShellyPlugSG3/#plugs_uisetconfig-example
example:

http://192.168.33.1/rpc/PLUGS_UI.SetConfig?config={"leds":{"mode":"switch","colors":{"switch:0":{"on":{"rgb":[100,100,0],"brightness":100},"off":{"rgb":[100,100,100],"brightness":100}},"power":{"brightness":100}},"night_mode":{"enable":true,"brightness":10,"active_between":["22:00","06:00"]}},"controls":{"switch:0":{"in_mode":"detached"}}}

[windkh]

I guess that should not be a big problem to support that. Indeed it could already work out of the box... will try it out

[windkh]

I guess that should not be a big problem to support that. Indeed it could already work out of the box... will try it out

[windkh]

@lukasMega following up on this properly — my hunch back in January was right: it already works, no new feature needed.

The plug devices (Plus Plug S, Plug S MTR Gen3, Plug PM Gen3, …) are typed Relay in the catalog, and that type routes to the generic gen2 parser, which passes any RPC method straight through to the device. So your raw HTTP call becomes an ordinary message into a shelly-gen2 node:

{
  "method": "PLUGS_UI.SetConfig",
  "params": {
    "config": {
      "leds": {
        "mode": "switch",
        "colors": {
          "switch:0": {
            "on":  { "rgb": [100, 100, 0],   "brightness": 100 },
            "off": { "rgb": [100, 100, 100], "brightness": 100 }
          },
          "power": { "brightness": 100 }
        },
        "night_mode": {
          "enable": true,
          "brightness": 10,
          "active_between": ["22:00", "06:00"]
        }
      },
      "controls": { "switch:0": { "in_mode": "detached" } }
    }
  }
}

I ran that payload through the parser to be sure rather than assume. It produces exactly:

{
  "route": "/rpc",
  "method": "POST",
  "data": { "id": 1, "method": "PLUGS_UI.SetConfig", "params": { "config": { ... } } }
}

which is the JSON-RPC frame the device's /rpc endpoint expects — the POST equivalent of the ?config={…} GET you were using.

Two notes:

• params and parameters both work. The node's own docs say parameters, but Shelly's RPC docs say params, and only reading the former used to drop the arguments silently and get an HTTP 400 back. Fixed in #195 — either spelling is fine now.
• This is not specific to PLUGS_UI. The same message shape reaches any RPC method the device exposes, so anything in the Shelly gen2/gen3 API docs can be driven this way without waiting for explicit support here.

For your actual goal — reflecting a state in the plug's LED — send one of these messages whenever the state changes. mode: "switch" ties the LED to the relay state; use mode: "power" if you would rather have it follow consumption.

Closing as already supported. Please reopen if the payload above does not behave on your hardware.