new CID after each reboot of OctoPrint

[speedAmaster]

I am happily using OctoPrint and found your plugin to connect to my home automation system (FEHM).

Conectivity works and allows (even too deep) insights into my printer and its printing progress.

Unfortunately - whenever I reboot Octoprint - I am receiving a new device being discovered even it is coming from the same IP-address.

define MQTT2_3ffx5QKDQ6BfcAdND4QYlg MQTT2_DEVICE **3ffx5QKDQ6BfcAdND4QYlg** setuuid MQTT2_3ffx5QKDQ6BfcAdND4QYlg 628b9912-f33f-d0eb-4e99-3d776ccfe7578999 attr MQTT2_3ffx5QKDQ6BfcAdND4QYlg readingList 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/mqtt:.* mqtt\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/progress/printing:.* { json2nameValue($EVENT, 'printing_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/progress/slicing:.* { json2nameValue($EVENT, 'slicing_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/event/ClientOpened:.* { json2nameValue($EVENT, 'ClientOpened_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/event/UserLoggedIn:.* { json2nameValue($EVENT, 'UserLoggedIn_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/event/ClientAuthed:.* { json2nameValue($EVENT, 'ClientAuthed_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/event/ClientClosed:.* { json2nameValue($EVENT, 'ClientClosed_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/event/FirmwareData:.* { json2nameValue($EVENT, 'FirmwareData_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/temperature/tool0:.* { json2nameValue($EVENT, 'tool0_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/temperature/bed:.* { json2nameValue($EVENT, 'bed_', $JSONMAP) }\ 3ffx5QKDQ6BfcAdND4QYlg:octoPrint/event/plugin_pi_support_throttle_state:.* { json2nameValue($EVENT, 'plugin_pi_support_throttle_state_', $JSONMAP) }
or

define MQTT2_2AjoLPx8nMSdyWNun7V1G4 MQTT2_DEVICE **2AjoLPx8nMSdyWNun7V1G4** setuuid MQTT2_2AjoLPx8nMSdyWNun7V1G4 628b9b33-f33f-d0eb-c45a-076bf6626ac4942a attr MQTT2_2AjoLPx8nMSdyWNun7V1G4 readingList 2AjoLPx8nMSdyWNun7V1G4:octoPrint/mqtt:.* mqtt\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/progress/printing:.* { json2nameValue($EVENT, 'printing_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/progress/slicing:.* { json2nameValue($EVENT, 'slicing_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/event/FirmwareData:.* { json2nameValue($EVENT, 'FirmwareData_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/temperature/tool0:.* { json2nameValue($EVENT, 'tool0_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/temperature/bed:.* { json2nameValue($EVENT, 'bed_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/event/ClientOpened:.* { json2nameValue($EVENT, 'ClientOpened_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/event/UserLoggedIn:.* { json2nameValue($EVENT, 'UserLoggedIn_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/event/ClientAuthed:.* { json2nameValue($EVENT, 'ClientAuthed_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/event/plugin_pi_support_throttle_state:.* { json2nameValue($EVENT, 'plugin_pi_support_throttle_state_', $JSONMAP) }\ 2AjoLPx8nMSdyWNun7V1G4:octoPrint/event/ClientClosed:.* { json2nameValue($EVENT, 'ClientClosed_', $JSONMAP) }

after a reboot of Octoprint.

Is there way to avoid creation of the new CIDs?

Version of OctoPrint

Version 1.7.0

Version of the MQTT plugin

MQTT (0.8.12)