ConfigSet writes the node's desired configuration, which is read at ENI-generation time (MotionController::NetworkEniGenerate) and translated into the generated ENI. The typical flow: start the network, ConfigSet on the desired nodes, regenerate the ENI, restart. Because membership travels in the ENI, it survives subsequent restarts; repeat this flow only to change the grouping. See Sync Groups.
Sample Code:
controller->NetworkStart(); // 1. discover the network
controller->NetworkEniGenerate(); // 3. consumes the staged configs
controller->NetworkShutdown(); // 4. restart on the new ENI
controller->NetworkStart();
Note
This is desired/staged config, not runtime state: network discovery re-zeroes it on every restart by design – after a restart, the loaded ENI is the source of truth and the node's ACTUAL group is reported by Status.SyncGroupId (StatusGet), not ConfigGet.