2 mqttk app window about mqttk HOT 3 CLOSED

This will not be implemented this way.

Randomly changing the client ID can cause all sorts of problems with connections, for example: If the server is configured with ACLs that are specific to a client ID, changing the client ID specified in the configuration behind the scenes, especially without the user's knowledge, would cause totally unexpected behaviour. If in your use case this causes an issue, I recommend you to change the client ID manually before connecting the second client.

Alternatively, I could add an option in the connection configuration (a check box) to allow MQTTk to generate a unique client ID (random UUID) just before connecting.

from mqttk.

There are 2 computers in the office and this is how I solved the problem. It would be nice to add a random UUID option.

from mqttk.

This has been added to the test branch too.

from mqttk.