Skip to content

API: Better intance control handling #809

Closed
@brindosch

Description

@brindosch

Feature request

Current handling of the instance api isn't easy enough. When more than one instance should be controlled in the same way, or information should be gathered by instance it's getting complicated. So i propose

Add a new optional instance field to all requests or to specific requests

{"command":"xxx", "subcommand": "xxx", "instance":0, "tan":1}

It's open to the implementation if this should be limited to the number or if a string is also accepted with the user defined name. (Or an array with selections)

If the instance field is omitted or set to -1

  • Getter functions use the instance 0 (if applicable)
  • Setter functions like effect/color will be pushed to all instances (if applicable)

Further it might be possible to select more than one but less than all instances by providing a list of instances [0,3,4] (if applicable)

The last bit is how to "observe" the state of an instance, i think one instance for one connection is okay. More will increase load for the browser if not handled carefully. So no changes here.

What problem does this feature solve?

API usage when different instances should be selected

What does the proposed API look like?

Are you willing to work on this yourself?

Yes

cc @Lord-Grey @Paulchen-Panther

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions