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

Entity search always returns unavailable entities regardless of the search #1149

Open
hagak opened this issue Nov 11, 2023 · 8 comments
Open

Comments

@hagak
Copy link

hagak commented Nov 11, 2023

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

  1. Have entities defined in HA that are unavailable, good test is a seasonal item that is offline most of the year
  2. In the events:state node type gibberish into the Entity field (that does not match any entity in your system)
  3. Note all unavailable entities are in the list.

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

@Raspatat
Copy link

Raspatat commented Dec 8, 2023

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
Version:

Home Assistant version:
Core 2023.12.0

Node-RED version: 3.1.1
node-red-contrib-home-assistant-websocket: 0.59.0
Docker: yes
Add-on: no

@Raspatat
Copy link

Still occurring:

Environment Information
Version:

Home Assistant version: 2023.12.3

Node-RED version: 3.1.3
node-red-contrib-home-assistant-websocket: 0.62.2
Docker: yes
Add-on: no

Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Feb 18, 2024
@hagak
Copy link
Author

hagak commented Feb 18, 2024

This is still a bug, adding activity to prevent auto-closure.

@github-actions github-actions bot removed the Stale label Feb 19, 2024
Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Apr 19, 2024
@hagak
Copy link
Author

hagak commented Apr 19, 2024

Still a bug

@github-actions github-actions bot removed the Stale label Apr 20, 2024
Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Jun 19, 2024
@hagak
Copy link
Author

hagak commented Jun 19, 2024

This is still a bug

@github-actions github-actions bot removed the Stale label Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants