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

Update to 0.66.0 breaks get_entities node #1478

Closed
klatka opened this issue Aug 17, 2024 · 2 comments · Fixed by #1479
Closed

Update to 0.66.0 breaks get_entities node #1478

klatka opened this issue Aug 17, 2024 · 2 comments · Fixed by #1479

Comments

@klatka
Copy link

klatka commented Aug 17, 2024

Describe the bug

After updating to 0.66.0 my existing get_entitites nodes breaks. I am running now 0.67.0 but it is still the same behavior.
I have to open the editor for each node and save it without making changes to force an update to its config.

Here is an example:

751 | 751 | "rules": [
752 | 752 | {
  | 753 | +        "condition": "state_object",
753 | 754 | "property": "entity_id",
754 | 755 | "logic": "starts_with",
755 | 756 | "value": "media_player.wallpanel_",

As you can see line 753: "condition": "state_object" was added after closing the editor.
With this updated config the node works again.

I love the new features in this release! 👍🏻

To Reproduce

No response

Expected behavior

No response

Screenshots

No response

Example Flow

No response

Environment Information

Version: 0.67.0

Home Assistant version: 2024.8.2
Companion version: 4.0.2

Node-RED version: 4.0.2
Docker: yes
Add-on: no (yes but I am using my own credentials)

Node.js version: v18.20.3 x64 linux
OS: Linux 6.6.44-haos x64

Additional context

No response

@zachowj
Copy link
Owner

zachowj commented Aug 18, 2024

Did it throw an error or not return the expected results?

@klatka
Copy link
Author

klatka commented Aug 18, 2024

Did it throw an error or not return the expected results?

No errors were thrown, but either no results were returned. Thanks for fixing this!

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

Successfully merging a pull request may close this issue.

2 participants