MQTT 2 - ClientID not used

I just saw, that the configured clientID is not used. Instead the generated value is sent to Broker.

Can you post the MQTT log file
@David_Graeff, maybe a bug?

Yes that’s a known bug with an existing bug report.

Happy new year,

Happy new year

Thanks - for the moment I will use the generated ClientID.
But my next problem is “No MQQT client”

14:45:46.237 [INFO ] [o.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to ‘’ with clientid paho10169275198078 and file store ‘C:\openhab\userdata\mqtt\’
14:45:46.245 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘mqtt:broker:d550f48f’ has been updated.
14:45:46.263 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘mqtt:broker:d550f48f’ changed from OFFLINE to ONLINE
14:45:46.291 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘mqtt:topic:32d1e183’ changed from OFFLINE (BRIDGE_OFFLINE) to ONLINE
14:45:46.313 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘mqtt:broker:d550f48f’ has been updated.
14:49:25.893 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘mqtt:topic:32d1e183’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): java.lang.Exception: No MQTT client
14:49:25.899 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘mqtt:topic:32d1e183’ has been updated.

Any idea?

This is a know bug that has been corrected in the snapshots.
However there is a workaround but only if you are using things text files.
Put the broker in one file and the mqtt things in another

Hi Vincent
thanks for helping. Snapshot solves this problem.
regards, Toni

By the way: the port has to be configured, otherwise an error is shown during initializing