We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Newly created switch node ends up showing as "Unavailable" after a while...
I created a switch node and the entity shows in HA.
After some days or weeks have passed, the entity shows as "Unavailable".
If I reload the integration, it shows as "Not provided".
If I delete the entity and recreate the switch node, it works again for a while.
Would expect the entity to show as available. Node red shows no issues.
No response
Version: 0.74.1
Home Assistant version: 2024.12.5 Companion version: 4.1.2
Node-RED version: 4.0.5 Docker: yes Add-on: no
Node.js version: v20.18.0 arm64 linux OS: Linux 6.1.21-v8+ arm64
The text was updated successfully, but these errors were encountered:
Updated to 0.75.0 (node-red-contrib-home-assistant-websocket), let's see how long it lasts for...
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Newly created switch node ends up showing as "Unavailable" after a while...
To Reproduce
I created a switch node and the entity shows in HA.
After some days or weeks have passed, the entity shows as "Unavailable".
If I reload the integration, it shows as "Not provided".
If I delete the entity and recreate the switch node, it works again for a while.
Expected behavior
Would expect the entity to show as available. Node red shows no issues.
Screenshots
Example Flow
No response
Environment Information
Version: 0.74.1
Home Assistant version: 2024.12.5
Companion version: 4.1.2
Node-RED version: 4.0.5
Docker: yes
Add-on: no
Node.js version: v20.18.0 arm64 linux
OS: Linux 6.1.21-v8+ arm64
Additional context
No response
The text was updated successfully, but these errors were encountered: