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

Rule set-up to prevent overwrites #137

Closed
jmabad100 opened this issue Apr 10, 2020 · 7 comments
Closed

Rule set-up to prevent overwrites #137

jmabad100 opened this issue Apr 10, 2020 · 7 comments
Assignees
Labels
💡 enhancement New feature or request

Comments

@jmabad100
Copy link

Hi,

Does somebody knows how to set-up a rule with a condition to prevent an overwrites?

Thank you so much.

@Hypnos3
Copy link
Collaborator

Hypnos3 commented Apr 10, 2020

That is not possible. An override is(currenlty) always evaluated with an higer priority than any rule. If an override exists rules will not be evaluated. Multiple overrides can be prioritized against each other.

Maybe a feature request to give the rules also a priority property which works to overrides.

What is currently possible is to work completely without overrides and only use rules. Rules can also access msg properties and go active accordingly or not.
Or to only work with overrides and have the logic which is normally in the rules oudside of the node.

@Hypnos3 Hypnos3 self-assigned this Apr 10, 2020
@Hypnos3 Hypnos3 added the 💡 enhancement New feature or request label Apr 10, 2020
@jmabad100
Copy link
Author

Thank Hypnos3,

I was just asking, because the documentation says:

There are a special configuration for rules with a condition, with which it can be prevented to allow overrides.

And I was not able to find this set-up.

Thanks

@Hypnos3
Copy link
Collaborator

Hypnos3 commented Apr 12, 2020

Sorry that the documentation here is misleading.

Unfortunately I don't know what I wanted to say with this sentence in the documentation. I will change it in the next remease.

@jmabad100
Copy link
Author

jmabad100 commented Apr 12, 2020 via email

Hypnos3 added a commit that referenced this issue Apr 16, 2020
@Hypnos3
Copy link
Collaborator

Hypnos3 commented Apr 23, 2020

In the next release a "importance" (priority is now renamed to importance) for rules is implemented, where can be setup a rule with a higher "importance" than an override.

This is still under test. If you feel brave you can already install it from command line from the node-red directory with (standard Linux):

npm install node-red-contrib-sun-position@1.1.0-alpha

If you are using a Homematic CCU the commands are (to use from ssh login):

source /usr/local/addons/redmatic/home/.profile
cd /usr/local/addons/redmatic/var
npm install --save --no-package-lock --global-style --save-prefix="~" --production node-red-contrib-sun-position@1.1.0-alpha

@Hypnos3 Hypnos3 mentioned this issue Apr 23, 2020
@jmabad100
Copy link
Author

In the next release a "importance" (priority is now renamed to importance) for rules is implemented, where can be setup a rule with a higher "importance" than an override.

This is still under test. If you feel brave you can already install it from command line from the node-red directory with (standard Linux):

npm install node-red-contrib-sun-position@1.1.0-alpha

If you are using a Homematic CCU the commands are (to use from ssh login):

source /usr/local/addons/redmatic/home/.profile
cd /usr/local/addons/redmatic/var
npm install --save --no-package-lock --global-style --save-prefix="~" --production node-red-contrib-sun-position@1.1.0-alpha

Hi hypnos3

I have installed version 1.1.0 alpha using npm, but it is not updating on node red. Version 1.0.17 continues to appear. What should I do to work with version 1.1.0 alpha.

Thanks

@Hypnos3
Copy link
Collaborator

Hypnos3 commented May 20, 2020

Today I have released Version 1.1.0. It should be available in the Standard Node-Red package manager.

@Hypnos3 Hypnos3 closed this as completed May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 enhancement New feature or request
Development

No branches or pull requests

2 participants