OpenMQTTGateway Non-persistent entity IDs in Home Assistant

Describe the bug I noticed that OMG always defaults its entity IDs. Custom set ones are ignored once entity ids are re-created.

To Reproduce Steps to reproduce the behavior:

Disable BT: Adaptive scan switch, new entities are created: number.bt_interval_between_active_scans and number.bt_interval_between_scans
Rename those entities to e. g. number.esp_omg_kitchen_bt_interval_between_active_scans and number.esp_omg_kitchen_bt_interval_between_scans
Enable BT: Adaptive scan switch, both interval number entities are removed
Disable BT: Adaptive scan switch:

Expected behavior created interval number entities are restored as configured (number.esp_omg_kitchen_bt_interval_between_active_scans and number.esp_omg_kitchen_bt_interval_between_scans)

Actual behaviour: created interval number entities default and ignore their previous names/IDs (number.bt_interval_between_active_scans and number.bt_interval_between_scans)

Environment (please complete the following information):

OpenMQTTGateway version used: v1.6.0 / development a046c8

Additional context

This obviously creates problems as entity ids are sensitive in HA. Imagine you have more than one OMG integrated - they sum up with _2 etc.
How can we get persistent entity IDs here?

Sep 22 '23 21:09 bcutter

This issue is stale because it has been open for 90 days with no activity.

Dec 22 '23 00:12 github-actions[bot]

Still not fixed and VERY annoying. At latest on every update this causes trouble.

Dec 22 '23 09:12 bcutter

This issue is stale because it has been open for 90 days with no activity.

Mar 23 '24 00:03 github-actions[bot]

Still not fixed and VERY annoying. At latest on every update this causes trouble.

Mar 23 '24 00:03 bcutter

This issue is stale because it has been open for 90 days with no activity.

Jun 22 '24 00:06 github-actions[bot]

Still not fixed and VERY annoying. At latest on every update this causes trouble.

Jun 22 '24 09:06 bcutter