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

Renamed entity: lost history #116645

Open
systemcrash opened this issue May 2, 2024 · 1 comment
Open

Renamed entity: lost history #116645

systemcrash opened this issue May 2, 2024 · 1 comment

Comments

@systemcrash
Copy link
Contributor

systemcrash commented May 2, 2024

The problem

I just renamed it - it cannot be in use? Lost history...

2024-05-02 18:31:42.022 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `update.tradfri_bedroom_250lm_firmware` to `update.bedside_250lm_firmware` because the new entity_id is already in use
2024-05-02 18:31:42.033 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `button.tradfri_bedroom_250lm_identify` to `button.bedside_250lm_identify` because the new entity_id is already in use
2024-05-02 18:31:42.045 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `light.tradfri_bedroom_250lm_light` to `light.bedside_250lm_light` because the new entity_id is already in use
2024-05-02 18:31:42.054 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `number.tradfri_bedroom_250lm_on_level` to `number.bedside_250lm_on_level` because the new entity_id is already in use
2024-05-02 18:31:42.064 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `number.tradfri_bedroom_250lm_on_off_transition_time` to `number.bedside_250lm_on_off_transition_time` because the new entity_id is already in use
2024-05-02 18:31:42.074 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `select.tradfri_bedroom_250lm_start_up_behavior` to `select.bedside_250lm_start_up_behavior` because the new entity_id is already in use
2024-05-02 18:31:42.083 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `number.tradfri_bedroom_250lm_start_up_current_level` to `number.bedside_250lm_start_up_current_level` because the new entity_id is already in use

What version of Home Assistant Core has the issue?

core-2024.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

recorder.entity_registry(?)

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2024-05-02 18:31:42.022 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `update.tradfri_bedroom_250lm_firmware` to `update.bedside_250lm_firmware` because the new entity_id is already in use
2024-05-02 18:31:42.033 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `button.tradfri_bedroom_250lm_identify` to `button.bedside_250lm_identify` because the new entity_id is already in use
2024-05-02 18:31:42.045 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `light.tradfri_bedroom_250lm_light` to `light.bedside_250lm_light` because the new entity_id is already in use
2024-05-02 18:31:42.054 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `number.tradfri_bedroom_250lm_on_level` to `number.bedside_250lm_on_level` because the new entity_id is already in use
2024-05-02 18:31:42.064 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `number.tradfri_bedroom_250lm_on_off_transition_time` to `number.bedside_250lm_on_off_transition_time` because the new entity_id is already in use
2024-05-02 18:31:42.074 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `select.tradfri_bedroom_250lm_start_up_behavior` to `select.bedside_250lm_start_up_behavior` because the new entity_id is already in use
2024-05-02 18:31:42.083 WARNING (Recorder) [homeassistant.components.recorder.entity_registry] Cannot migrate history for entity_id `number.tradfri_bedroom_250lm_start_up_current_level` to `number.bedside_250lm_start_up_current_level` because the new entity_id is already in use


### Additional information

Let me know whether you require more info. ( zigbee integration - zigbee bulb )

never had anything with that name in my system prior. 
@home-assistant
Copy link

home-assistant bot commented May 3, 2024

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (recorder) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of recorder can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign recorder Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


recorder documentation
recorder source
(message by IssueLinks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants