-
Notifications
You must be signed in to change notification settings - Fork 188
Node Red companion entities being duplicated on occasion after host reboot. #333
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
Comments
I found I can reproduce this 100% of the time if I Rename the NR Companion Integration from "name" to something else. It has also happened/been triggered other ways, but this is the most reliable. Restarting, then disabling, then restarting, then enabling, then restarting, seems to clear it (remove the _2 items) but it could be a fluke fix. I know the other issue/thread has more info on the fix. |
I see renamed if i just restart Node-RED Companion in Home assistant (config/integrations/integration/nodered) |
Can Anybody fix it? I have Many devices and i need rename all them in HA everyday. It is crazy. |
Absolutely crazy bug this is... If you rename it in core.config_entries it doesn't make the duplicate entities. I'm guessing when you rename the config item it starts creating the new one with the new name before it has deleted the old one and its entities, resulting in duplicates. |
Can you create an manual how i need do it? I not understand where i can found core.config_entries. |
Originally posted by @zachowj in #126
This works to resolve the issue. But is there any way to prevent this from happening in the first place?
I'm on HA version: 2025.2.5
Companion version: 4.1.2
Node Red version: 19.0.2
Running HA inside a virtualbox VM hosted on a Windows 10 machine. This seems to happen when I reboot the VM. But it doesn't happen consistently. I always shut it down with an ACPI shutdown.
The text was updated successfully, but these errors were encountered: