node-red-contrib-home-assistant-websocket
node-red-contrib-home-assistant-websocket copied to clipboard
zachowj
Entity search always returns unavailable entities regardless of the search
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
- Have entities defined in HA that are unavailable, good test is a seasonal item that is offline most of the year
- In the events:state node type gibberish into the Entity field (that does not match any entity in your system)
- 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
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
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
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[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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 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.
