feat: auto-migrate entity IDs from _2 to _am and _pm suffixes #9

Merged
jrittenh merged 2 commits from feature/entity-id-am-pm-migration into main 2026-10-28 22:40:32 -04:00
Owner

This PR introduces automatic entity ID migration and suggested object IDs:

  • Automatic Entity ID Migration: Inspects the entity registry during integration setup. If an existing entity ID contains generic collision suffixes like _2 or lacks an _am / _pm suffix, it updates the entity ID to include _am or _pm (e.g., device_tracker.<student>_bus_am and device_tracker.<student>_bus_pm).
  • Suggested Object IDs: Defines suggested_object_id across all device trackers and sensors so newly added entities natively generate specific _am and _pm entity IDs.
  • Manifest Version: Bumps version to 0.2.3.
  • Unit Tests: Full test suite verifying entity registry migration and suggested object IDs.
This PR introduces automatic entity ID migration and suggested object IDs: - **Automatic Entity ID Migration**: Inspects the entity registry during integration setup. If an existing entity ID contains generic collision suffixes like `_2` or lacks an `_am` / `_pm` suffix, it updates the entity ID to include `_am` or `_pm` (e.g., `device_tracker.<student>_bus_am` and `device_tracker.<student>_bus_pm`). - **Suggested Object IDs**: Defines `suggested_object_id` across all device trackers and sensors so newly added entities natively generate specific `_am` and `_pm` entity IDs. - **Manifest Version**: Bumps version to `0.2.3`. - **Unit Tests**: Full test suite verifying entity registry migration and suggested object IDs.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jrittenh/ha-myride!9
No description provided.