Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-persistent entity IDs in Home Assistant #1756

Open
bcutter opened this issue Sep 22, 2023 · 4 comments
Open

Non-persistent entity IDs in Home Assistant #1756

bcutter opened this issue Sep 22, 2023 · 4 comments

Comments

@bcutter
Copy link

bcutter commented Sep 22, 2023

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:

  1. Disable BT: Adaptive scan switch, new entities are created: number.bt_interval_between_active_scans and number.bt_interval_between_scans
  2. Rename those entities to e. g. number.esp_omg_kitchen_bt_interval_between_active_scans and number.esp_omg_kitchen_bt_interval_between_scans
  3. Enable BT: Adaptive scan switch, both interval number entities are removed
  4. 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?
Copy link

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

@github-actions github-actions bot added the stale label Dec 22, 2023
@bcutter
Copy link
Author

bcutter commented Dec 22, 2023

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

@github-actions github-actions bot removed the stale label Dec 23, 2023
Copy link

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

@github-actions github-actions bot added the stale label Mar 23, 2024
@bcutter
Copy link
Author

bcutter commented Mar 23, 2024

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

@github-actions github-actions bot removed the stale label Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant