Forum wide moderators
@tunnus said in Reactor-Editor / Reactor-ui-Status Errors:
Just got a runtime error in UI (build 24343) when I deleted a newly created rule. Before deleting this rule, I copied reactions to it from another rule. It also contained local variables (if that matters).
I need a detail of every single step taken up the error popping up. Click by click, key by key. Also need to know what conditions were in the rule, and what actions were in the reactions.
That's... crazy. You know those things programmers say "should never happen"?
It's that.
Digging.
@Snowman said in Reactor-Editor / Reactor-ui-Status Errors:
For example, I'll go to Expressions, click the Add Expression, and when I click the Save Changes button, that is when these errors pop-up.
All of the errors you showed are in the context of the Rule Editor being active. Can you show an error message from using just the Expressions tab as in your example?
@Snowman said in Reactor-Editor / Reactor-ui-Status Errors:
I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
So, this is progressive? Does it ever happen on the first use of the tab/function? Is it not resolved temporarily by simply refreshing the page/UI?
For the Status issue, you might try going to the Tools page and clicking on the Clear Local Storage link.
Also, in each case, I need to know exactly what you were doing, and when/where/how the error was presented. At least one of these errors could be logged completely harmlessly, so it's not clear to me that you are reporting an actual problem that is preventing you from doing any work, or if you are just reporting something you see going by in the log that you noticed by chance.
Yes, this should work. Just be aware that since your second condition spans midnight, the rule will set at midnight on 10/1 and reset at midnight on 4/1.
@gwp1 said in every X days field uneditable:
I want to create a ruleset that is only in effect from October thru March annually
Actually, you want to create a Rule. A RuleSet is a collection of Rules.
Now, I have to read between the lines of your problem description a bit here, but I'm thinking you mean that you want a rule to trigger once per day from October to March? If that's the case, an Interval is not the way to go, IMO. I would use two Date/Time conditions in an AND group. The first condition would constrain the dates (i.e. "between 1 October and 1 April", assuming you want it to trigger throughout March"), and the second "after 00:00" (assuming you keep the default Follow output mode on the condition and its parent group). The second condition will only trigger once per day, whenever it can (i.e. if the system is down at midnight, it will trigger as soon as it comes back up).
If you want the trigger to happen at some other time of day, say 10am, just put that in the Date/Time after condition instead of midnight.
Set hours to zero first.
Build 24343 has fully HTTP actions, so cool things could be created (see docs). I've recently changed a couple of cams because better definition and I've found tha Reolink has a couple of cams that have spotlights. While the spotlights are driven by motion (so the cam could record in color), I wanted to drive them directly, so in case of any "security" event, like alarm on, door open, etc, I could use the lights to have a better video and make - you know - light.
So, if you want to use HTTP actions in VirtualController, just go to config, entities under your VirtualEntityController section in reactor.yaml, and add this:
- id: cams_retro_spotlights
name: "Retro Cam - Spotlights"
template: Binary Switch
# update the status at interval
http_request:
interval: 900 # 15m
url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo"
method: "POST"
force_json: true
headers:
"Content-Type": "application/json"
"Accept": "application/json"
body: '[{"cmd": "GetWhiteLed", "action": 0 , "param": { "channel": 0 }}]'
capabilities:
power_switch:
attributes:
state:
expr: "isnull( response ) ? null : response[0]?.value?.WhiteLed?.state == 1"
default: false
actions:
"on":
http_request:
url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo"
method: "POST"
force_json: true
headers:
"Content-Type": "application/json"
"Accept": "application/json"
body: '[{"cmd": "SetWhiteLed", "param": { "WhiteLed": {"bright" : 100, "channel": 0, "mode": 1, "state": 1}}}]'
target: state
expr: "isnull( response ) ? null: response[0]?.value?.rspCode == '200'"
"off":
http_request:
url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo"
method: "POST"
force_json: true
headers:
"Content-Type": "application/json"
"Accept": "application/json"
body: '[{"cmd": "SetWhiteLed", "param": { "WhiteLed": {"bright" : 100, "channel": 0, "mode": 1, "state": 0}}}]'
target: state
expr: "isnull( response ) ? null : response[0]?.value?.rspCode == '200' ? false : null"
Reolink has API where you have to post a JSON and the response will give you a JSON (in theory). It's not really JSON, so force_json: true will do the trick for you. I'm lefting this as an example of cool things you could do with the new capabilites added/documented in 24343. HTH.
small update to align to 24343. https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
