-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Entity search always returns unavailable entities regardless of the search #1149
Comments
I have the same experience. As a workaround I use a substring with the full entity name, the issue does not occur then. Environment Information Home Assistant version: Node-RED version: 3.1.1 |
Still occurring: Environment Information Home Assistant version: 2023.12.3 Node-RED version: 3.1.3 |
This issue has been automatically marked as abandoned because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still a bug, adding activity to prevent auto-closure. |
This issue has been automatically marked as abandoned because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still a bug |
This issue has been automatically marked as abandoned because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still a bug |
Describe the bug
If you type in the entity field for the events: state node (probably others as well). It will always return any "unavailable entities" even if what is typed does not match any part. example I could type "ASDFASKJASFDGD" which I have no entities that match this but ALL of the unavail entites are listed. I have a few devices that are seasonal and notice that when they are online they do not show in the list.
To Reproduce
Expected behavior
Only entities that match the search criteria should be shown.
Screenshots
No response
Example Flow
No response
Environment Information
Version:
Home Assistant version:
Companion version: 3.1.1
Node-RED version: 0.59
Docker: yes
Add-on: no
Node.js version:
OS:
Additional context
No response
The text was updated successfully, but these errors were encountered: