Skip to content

Home Assistant Lockup #331

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

Open
metril opened this issue Jan 13, 2025 · 1 comment
Open

Home Assistant Lockup #331

metril opened this issue Jan 13, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@metril
Copy link

metril commented Jan 13, 2025

Describe the bug

The nodered companion integration is setup with the configuration name of "name". Attempting to rename this to anything else will cause Home Assistant to stop responding. Checking the logs later will reveal that Home Assistant load had drastically increased and hence, no response.###

To Reproduce

  1. Install the companion integration.
  2. Rename the companion configuration from "name" to anything else.

Expected behavior

The integration should have a proper name other than "name". Renaming the configuration should work without locking up Home Assistant.

Screenshots

No response

Example Flow

No response

Environment Information

Version: 0.75.0

Home Assistant version: 2025.1.2
Companion version: 4.1.2

Node-RED version: 4.0.8
Docker: yes
Add-on: 19.0.0

Node.js version: v22.11.0 x64 linux
OS: Linux 6.6.66-haos x64

Additional context

No response

@kylerm42
Copy link

Confirming this is happening for me as well.

Companion: 4.1.2
Home Assistant: 2025.1.3 in Docker
Node-RED: 4.0.8 in Docker

@zachowj zachowj added the bug Something isn't working label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants