Handling local vs network actions

[jonsmirl]

In the light demo toggling the bulb is handled locally.

    attribute::get_val(attribute, &val);
    val.val.b = !val.val.b;
    attribute::update(endpoint_id, cluster_id, attribute_id, &val);

In the light-switch demo toggling the bulb is handled via the network

    uint32_t command_id = OnOff::Commands::Toggle::Id;

    g_cluster_id = cluster_id;
    g_command_id = command_id;
    lock::chip_stack_lock(portMAX_DELAY);
    client::cluster_update(endpoint_id, cluster_id);
    lock::chip_stack_unlock();

So how do I implement the use-case described in this issue?
project-chip/connectedhomeip#21243

You can't just do both actions because the toggle will happen twice, once locally and again when it arrives via the group.

So I see two options, which one is better and how do I implement it?

1. Keep track of whether the dimmer has been bound to a group. If it has been bound use the network, if not use a local action.

2. Somehow construct a loopback binding when not bound to a group, then always use a network action.

[jonsmirl]

I made this issue on CHIP
project-chip/connectedhomeip#21470

Can you please help push it with them so that they don't ignore it?