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

Rules: blind position does not accept flow context #534

Open
nikipore opened this issue Aug 25, 2023 · 0 comments
Open

Rules: blind position does not accept flow context #534

nikipore opened this issue Aug 25, 2023 · 0 comments

Comments

@nikipore
Copy link

Describe the bug

Create an empty rule (catchall) and set blind position to some value, say 0.15. This sets the blind position to 0.15.

Now save that same value in flow.test, and set blind position to flow.test. (I use a persistent context storefor that which survives reloads of the Node-RED flow.) You will get the following error message:

error getting blind level: Cannot set properties of undefined (setting 'flow.#:(store)::test')

Screenshots

Rule definition:

Bildschirmfoto 2023-08-25 um 08 29 06

Flow context (the screenshot has another value 0.5, sorry, just mentally replace it with 0.15):

Bildschirmfoto 2023-08-25 um 08 31 43

This is how it looks if you enter the value 0.15 statically (via "Level entered – 09"):

Bildschirmfoto 2023-08-25 um 08 33 27

And finally the error message:

Bildschirmfoto 2023-08-25 um 08 29 21

Expected behavior

The blind position should be set to the value of flow.test, viz. 0.15.

System information:

  • Node Version 3.0.0-alpha1
  • Node-Red Version 3.0.2

Additional context

I am actually interested in using the flow context for a minimum override, ideally in a JSONata expression to make the rule generic and divide by 100 to convert from the user input which is denoted in percent. I tried to inject the parameter via a message to read it from msg.test instead of flow.test or JSONata $flowContext("test", "store"), but to no avail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant