Its may be good idea in future, but we needed "backward compatibilities" for older sketches.
backward compatibility will continue, older solutions will still wait 0.5 sek and then send configuration.
New solution instead of ticking time send configuration upon receipt of this new information
its broker troubles, but all brokers can receive and send many messages per second.
Config payload send and receive with QoS=1, status message have QoS=0. Several status messages can be discarded by broker (or delayed), for high load traffic of messages, but config messages delivery guarantee by QoS=1.
So eg. your Arduino example:
for (int i = 0; i < nWidgets; i = i + 1) {
pubStatus(sTopic[i], stat[i]);
delay(100);
}
Is this delay(100) is because of broker, not because of IoTmanager and I do not need to use it ??
(I think my broker is fast enough)
How to change/delete the location of ALL tab ?