-
@toggledbits Master, following the discussion of this thread, the variable FaultMSG is composed with the list of devices that will be displayed, example below.
07849e24-9a19-4957-a585-cfcd12088620-image.png
As you can see, the final string of devices, not sorted by name, follows the array generated by the device ID, composed one step earlier.
07fec184-0814-45e4-b689-533372af1fb4-image.png
Is it possible to sort by device name? Before generating the string? I think when generating the array?
Thanks.
-
Just updated to latest 21294, ran usual update, It appears to start ok in console, but will not load in browser. The NODE_path looks correct but the console log show the below error.
log
NODE_PATH /data/data/com.termux/files/home/reactor: [latest-21294]2021-10-23T15:55:41.542Z <app:null> Reactor latest-21294-c13ea5d starting on v14.15.4 [latest-21294]2021-10-23T15:55:41.546Z <app:INFO> Process ID 14540; platform android/arm #1 SMP PREEMPT Wed Jan 16 09:21:08 CST 2019; locale en_US.UTF-8 [latest-21294]2021-10-23T15:55:41.547Z <app:INFO> Basedir /data/data/com.termux/files/home/reactor; data in /data/data/com.termux/files/home/reactor/storage [latest-21294]2021-10-23T15:55:41.548Z <app:INFO> NODE_PATH /data/data/com.termux/files/home/reactor: /data/data/com.termux/files/home/reactor/app.js:231 throw new Error(a0_0x4c6635(0xd9) + process[a0_0x4c6635(0xdb)][a0_0x4c6635(0x107)] + '\x20does\x20not\x20point\x20to\x20the\x20Reactor\x20install\x20directory'); ^ Error: Environment NODE_PATH=/data/data/com.termux/files/home/reactor: does not point to the Reactor install directory at Object.<anonymous> (/data/data/com.termux/files/home/reactor/app.js:231:15) at Module._compile (internal/modules/cjs/loader.js:1063:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10) at Module.load (internal/modules/cjs/loader.js:928:32) at Function.Module._load (internal/modules/cjs/loader.js:769:14) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12) at internal/main/run_main_module.js:17:47 NODE_PATH /data/data/com.termux/files/home/reactor: [latest-21294]2021-10-23T15:55:41.796Z <app:null> Reactor latest-21294-c13ea5d starting on v14.15.4 [latest-21294]2021-10-23T15:55:41.800Z <app:INFO> Process ID 14547; platform android/arm #1 SMP PREEMPT Wed Jan 16 09:21:08 CST 2019; locale en_US.UTF-8 [latest-21294]2021-10-23T15:55:41.801Z <app:INFO> Basedir /data/data/com.termux/files/home/reactor; data in /data/data/com.termux/files/home/reactor/storage [latest-21294]2021-10-23T15:55:41.801Z <app:INFO> NODE_PATH /data/data/com.termux/files/home/reactor: /data/data/com.termux/files/home/reactor/app.js:231 throw new Error(a0_0x4c6635(0xd9) + process[a0_0x4c6635(0xdb)][a0_0x4c6635(0x107)] + '\x20does\x20not\x20point\x20to\x20the\x20Reactor\x20install\x20directory'); ^ ```===group ```java===
-
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed. -
A few new functions have worked their way into Reactor's expression language over the last couple of months, and while they are documented in the change logs and documentation, it seems some of you are not aware of them, so I'm going to pick one out and highlight it, maybe do others later...
A lot of you build strings in expressions by simple concatenation, and there's nothing wrong with that, but there's a new function in the expression language that can help you clean things up, in particular when handling numeric values.
I've noticed many of you will round your results either on the calculation, or in some cases, in a separate variable. For example, say we have a pair of expressions that retrieves the indoor and outdoor temperature from a sensor and the weather service:
indoor = getEntity( 'hubitat>144' ).attributes.temperature_sensor.value' ) outdoor = getEntity( 'weather>home' ).attributes.wx.temperatureThe weather service, since it converts from degrees K in its reporting to degrees C, may have an irrational or repeating value (e.g. 8.233333333...). As a result, when you compute the difference, it, too, may have an irrational or repeating result, so you decide to round it to one decimal:
tempDiff = round( outdoor - indoor, 1 )Then, perhaps you have a rule that if the differential is greater than 10 degrees, you send a notification, and the notification uses all three variables in the message string:
${{ 'The outdoor temperature is ' + outdoor + 'C and the indoor temperature is ' + indoor + 'C; the difference is ' + tempDiff + 'C' }}This is fine, except that the outdoor temperature isn't rounded, so you decide to fix that. There are at least three ways: add a round() to the outdoor variable expression, or create a third variable like outdoorRounded = round( outdoor, 1 ), or, use the round() function into the substitution expression
${{ 'The outdoor temperature is ' + round( outdoor, 1 ) + 'C and the indoor temperature is ' + indoor + 'C; the difference is ' + tempDiff + 'C' }}It's all getting very messy... Let's use format() instead of string concatenation, and not worry about rounding the difference, so we keep the maximum precision possible for any calcs or tests that use it. We go back to:
indoor = getEntity( 'hubitat>144' ).attributes.temperature_sensor.value' ) outdoor = getEntity( 'weather>home' ).attributes.wx.temperature tempDiff = outdoor - indoorNow our string substitution:
${{ format( "The outdoor temperature is {0:.1f}C and the indoor temperature is {1:.1f}C; the difference is {2:.1f}C", outdoor, indoor, tempDiff ) }}Here, format() is building the message string. Each {} (curly-brace) pair denotes the substitution of a parameter to follow. The number first inside the opening curly brace is the parameter number, starting from 0 as the first parameter. So parameter 0 in this example refers to the variable outdoor, and 1 is indoor, and 2 is tempDiff. Using the numbers, parameters can be inserted in any order.
Each of these substitutions in the example includes an optional format specification. If no format specification is given (e.g. {0}), then the parameter is converted to a string with no special formatting, but since we can get numbers like 8.233333... it's desirable to use some formatting to make it pretty. The format is separated from the parameter number by the : (colon) in the substitution. The format we're using for all three parameters is .1f, which is <width>.<precision>f. Any number before the dot is a fixed field width, but since we want no extra spaces, we just don't specify a width (it's blank for our example), and the value will take as much space as it needs. The f at the end tells format() that the value is going to be formatted as a floating point number, and the .1 before the f tells the formatter to display a single decimal digit. So our 8.23333333 value would be displayed as 8.2, without using extra functions or variables, or dropping precision in a calculation. For clarity, 10.875 would be displayed/inserted as 10.9 in this example, because the formatter will round the displayed result to the specified number of decimal digits.
Tip: for simple string insertions that require no special formatting, format() will let you skip the parameter numbers if the parameters are in the same order as the substitutions, and the default format is (generic) string (s), so format( "{} x {} = {}", "alpha", "beta", "gamma" ) produces the string alpha x beta = gamma.
Docs for format are in the Reactor documentation under the heading Special Reactor Functions.
-
Just noticed that when trying to reorder some expressions, e.g. move the most recent one from the bottom of the list to the first, this new order didn't "stick".
At first yes, but when visiting some other menus (obviously saving before that) and then coming back, the moved item was in its original position (in the end of the list).
I currently have 29 global expressions (which may or may not have some relevance to this problem). Using build 21281 on linux.
Can log a PR with logs, if this seems hard to reproduce.
-
Is there a way to back-up MSR Rule Sets and Configuration. I need to update my QNAP Container Station MSR install which I understand is not straight forward. If it all goes pear-shaped, and I loose my Rule Sets and Configuration, I wondered if it could be restored from a previous back-up?
Also, can someone possibly point me to the best method to update the MSR install on my QNAP?
-
Hi
I have some devices on my Vera Plus controller that sometimes change to say "Can't detect device".
I can clear those red banners that show up in the Vera UI7 web GUI, for a device by running some LUA code like this:
luup.set_failure(0, 331)Maybe I can use the new MSR matchEntities to find and detect any devices on Vera that have developed the "Can't detect device" error and then reset them. ?
I can currently manually specify a particular problem device in a ruleset trigger like this:
6f789006-ce19-4776-b3dd-290e28e84c8b-image.png
But if I could have a rule that automatically detects any device that develops this problem that would be better.
Thanks
-
@toggledbits I added an IP camera to my Ezlo for testing and my global variable for Ezlo devices that are not responding randomly do a quick toggle from empty to "IP camera" then back to empty.
[latest-21292]2021-10-19T23:10:00.043Z <Engine:NOTICE> Resuming reaction Schema - Dräneringspump<SET> (rule-ktd8obiy:S) from step 2 [latest-21292]2021-10-19T23:10:00.043Z <Engine:5:Engine.js:1504> Engine#1 reaction rule-ktd8obiy:S step 2 perform { "entity": "vera>device_53", "action": "power_switch.off" } [latest-21292]2021-10-19T23:10:00.043Z <Engine:5:Engine.js:1407> _process_reaction_queue() task returned, new status 3; task 29 [latest-21292]2021-10-19T23:10:00.044Z <VeraController:null> VeraController#vera enqueue task for Entity#vera>device_53 action power_switch.off: task { "newTargetValue": "0", "DeviceNum": 53, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [latest-21292]2021-10-19T23:10:00.044Z <Engine:5:Engine.js:1442> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting [latest-21292]2021-10-19T23:10:00.048Z <Engine:5:Engine.js:1442> _process_reaction_queue() wake-up! [latest-21292]2021-10-19T23:10:00.049Z <Engine:5:Engine.js:1403> _process_reaction_queue() running task 29 { "tid": 29, "id": "rule-ktd8obiy:S", "rule": "rule-ktd8obiy", "__reaction": [RuleReaction#rule-ktd8obiy:S], "next_step": 3, "status": 1, "ts": 1634684400015, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 3 } [latest-21292]2021-10-19T23:10:00.049Z <Engine:NOTICE> Resuming reaction Schema - Dräneringspump<SET> (rule-ktd8obiy:S) from step 3 [latest-21292]2021-10-19T23:10:00.049Z <Engine:INFO> Schema - Dräneringspump<SET> all actions completed. [latest-21292]2021-10-19T23:10:00.049Z <Engine:5:Engine.js:1407> _process_reaction_queue() task returned, new status -1; task 29 [latest-21292]2021-10-19T23:10:00.050Z <Engine:5:Engine.js:1442> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting [latest-21292]2021-10-19T23:17:00.724Z <VeraController:ERR> VeraController#vera update request failed: FetchError: network timeout at: http://127.0.0.1:3480/data_request?id=status&DataVersion=574966431&Timeout=15&MinimumDelay=100&output_format=json&_r=1634685402721 [latest-21292]2021-10-19T23:24:07.826Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_615e11a7129e071220cb5f8d not previously defined! (value now (boolean)false) [latest-21292]2021-10-19T23:24:07.826Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_615e11a7129e071220cb5f8d not previously defined! (value now (boolean)false) [latest-21292]2021-10-19T23:24:07.828Z <Rule:INFO> Rule#rule-ku32xyj5 evaluation in progress; waiting for completion [latest-21292]2021-10-19T23:24:07.828Z <Rule:INFO> Rule#rule-kue8adhf evaluation in progress; waiting for completion [latest-21292]2021-10-19T23:24:07.828Z <Engine:5:Engine.js:981> Engine#1 set global EzloDevicesNotResponding; value=(string)IP Camera [latest-21292]2021-10-19T23:24:12.474Z <Rule:INFO> Rule#rule-ku32xyj5 evaluation in progress; waiting for completion [latest-21292]2021-10-19T23:24:12.475Z <Rule:INFO> Rule#rule-kue8adhf evaluation in progress; waiting for completion [latest-21292]2021-10-19T23:24:12.476Z <Engine:5:Engine.js:981> Engine#1 set global EzloDevicesNotResponding; value=(string) [latest-21292]2021-10-19T23:24:12.482Z <Rule:INFO> Notifiering - Ezlo devices OK (Rule#rule-kue8adhf) SET! [latest-21292]2021-10-19T23:24:12.483Z <Engine:5:Engine.js:1442> _process_reaction_queue() wake-up! [latest-21292]2021-10-19T23:24:12.487Z <Rule:INFO> Notifiering - Ezlo devices OK (Rule#rule-kue8adhf) RESET!
Is it the controller interface not supporting IP cameras or something else causing this?
@2021-10-19T23:24:07.826Z -
I am trying to display the primary attribute on this device like all my other Hubitat devices. The attribute is x_hubitat_extra_attributes.Status. This gives an error in the log. I can't see what I am doing wrong with this one. Do I need to to something different to display this?
[latest-21286]2021-10-16T14:42:23.141Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-21286]2021-10-16T14:42:23.166Z <HassController:NOTICE> HassController#hass attempting reconnection to ws://192.168.1.21:8123/api/websocket [latest-21286]2021-10-16T14:42:23.168Z <HassController:NOTICE> HassController#hass connecting via WS to ws://192.168.1.21:8123/api/websocket [latest-21286]2021-10-16T14:42:23.246Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-21286]2021-10-16T14:42:23.269Z <app:INFO> Structure running; pausing for controllers' initial ready [latest-21286]2021-10-16T14:42:23.273Z <HubitatController:NOTICE> HubitatController#hubitat not ready; performing initial connect/query [latest-21286]2021-10-16T14:42:23.290Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-21286]2021-10-16T14:42:23.296Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.1.21:8123; fetching initial data... [latest-21286]2021-10-16T14:42:23.300Z <HassController:INFO> HassController#hass Hass reports version "2021.10.5" location Home timezone America/Chicago state RUNNING safe_mode false [latest-21286]2021-10-16T14:42:23.303Z <HassController:ERR> HassController#hass reported Hass version "2021.10.5" is not supported! [latest-21286]2021-10-16T14:42:23.379Z <HassController:NOTICE> Controller HassController#hass is now online. [latest-21286]2021-10-16T14:42:23.563Z <default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to x_hubitat_extra_attributes.Status invalid, not in { "x_hubitat": { "id": "568", "name": "BlinkAPI", "commands": [ "ArmSystem", "Authorize", "CheckSyncModule", "DisableMotionDetection", "DisarmSystem", "EnableMotionDetection", "GetCameraInfo", "GetCameraLiveView", "GetCameraSensors", "GetCameraStatus", "GetCameraUsage", "GetHomescreen", "GetNetworkStatus", "GetNetworks", "GetNewThumbnail", "GetNotifications", "GetVideoEvents", "ListSchedules", "VerifyPIN", "refresh" ], "capabilities": [ "Actuator", "Refresh", "Sensor" ] }, "x_hubitat_Actuator": { }, "x_hubitat_Refresh": { }, "x_hubitat_Sensor": { }, "x_hubitat_extra_commands": { } } [latest-21286]2021-10-16T14:42:23.566Z <HubitatController:ERR> HubitatController#hubitat failed to connect/query http://192.168.1.70/apps/api/416: Error: Entity#hubitat>568:setPrimaryAttribute() can't set x_hubitat_extra_attributes.Status, not defined for entity [latest-21286]2021-10-16T14:42:23.567Z <HubitatController:CRIT> Error: Entity#hubitat>568:setPrimaryAttribute() can't set x_hubitat_extra_attributes.Status, not defined for entity Error: Entity#hubitat>568:setPrimaryAttribute() can't set x_hubitat_extra_attributes.Status, not defined for entity at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:403:19) at /opt/reactor/server/lib/HubitatController.js:865:183 at Array.forEach (<anonymous>) at /opt/reactor/server/lib/HubitatController.js:805:76 at processTicksAndRejections (internal/process/task_queues.js:95:5) [latest-21286]2021-10-16T14:42:23.713Z <OWMWeatherController:INFO> OWMWeatherController#weather done; 1 locations, 0 failed [latest-21286]2021-10-16T14:42:23.714Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. [latest-21286]2021-10-16T14:42:48.577Z <HubitatController:NOTICE> HubitatController#hubitat not ready; performing initial connect/query [latest-21286]2021-10-16T14:42:48.779Z <HubitatController:INFO> HubitatController#hubitat connecting to hub's eventsocket WebSocket API at ws://192.168.1.70/eventsocket [latest-21286]2021-10-16T14:42:48.781Z <HubitatController:NOTICE> Controller HubitatController#hubitat is now online. [latest-21286]2021-10-16T14:42:48.786Z <app:NOTICE> Starting HTTP server and API... [latest-21286]2021-10-16T14:42:48.791Z <app:NOTICE> Starting Reaction Engine... [latest-21286]2021-10-16T14:42:48.792Z <Engine:INFO> Reaction Engine starting [latest-21286]2021-10-16T14:42:48.792Z <Engine:INFO> Checking rule sets... [latest-21286]2021-10-16T14:42:48.798Z <Engine:INFO> Checking rules...
Log:Screen Shot 2021-10-16 at 10.11.12 AM.png
local_hubitat_devices.yaml:
-
Hi,
I feel a bit stupid with this issue since I know it is working and that it worked before.
I just can't seem to have a date range (between) going past dec 31 to work. In the interim, I manage to acheive what I want by using the "not between" equivalent.
I am using MSR on a raspberry Pi and I do have the latest development version (21286).
Here is a screen capture on which I have both the "between" and its equivalent "not Between" just so that you could see it.
I is probably something stupid and apologise in advance.
Thanks
-
In the background of other work, I've been putting together a build system for the OpenWrt version that Ezlo is using on the Plus. Job done. I can build pretty much any package, which may come in handy some day.
As a test of that, I thought, why not build nodejs... and you know where that leads, right?
It took some doing. There are a lot of dependencies, and the errors you get when the dependencies aren't met correctly can be cryptic and took quite a bit of research and experimentation to resolve... weeks, in fact, over a couple of hours here, a couple there.
But it's done and I now have Reactor running on an Ezlo Plus.
I'm not sure what the long term utility of this might be. Since the new Ezlo philosophy is to upgrade your system automatically on reboots, and so far the upgrades have wiped substantial parts of the file system in my experience, this could be a non-starter as a platform — you wouldn't want your automations to get blown off the machine every time Ezlo upgrades firmware (because you don't know when that's going to be, and Murphy says it will be while you are on vacation with no remote access). But, if there is some place it can be tucked away safely, or if, as probably should be demanded by the user community, updates become elective and user-driven, it actually makes a nice Pi-ish platform to run on.
On to the next skunkworks project...
-
Timestamps do not match the UI time or the system time:
[latest-21286]2021-10-16T03:10:43.922Z <Engine:INFO> Engine#1 master timer tick, local time "10/15/2021, 8:10:43 PM" (TZ offset -420 mins from UTC)I tried adding TZ to the docker container with "docker exec reactor apk add tzdata" but there was no change in log timestamps. I have the TZ in the compose file as:
environment: REACTOR_DATA_PREFIX: /var/reactor TZ: America/Los_AngelesThis does set the UI time correctly. The Reactor config is also set correctly:
location: city: "Los Angeles" -
I'd like to invoke in Reactor a Home Assistant service through the HA API. I use the following code in a vera plugin I wrote to send an HTTP request to Home Assistant to trigger an announcement on Alexa--using a Home Assistant Alexa integration that you can install through HACS.
myEchoDevice = "alexa_media_".. myEchoDevice myEchoMessage = table.concat(myEchoMessage) local request_body = json.encode {message = myEchoMessage, data = {["type"] = "announce",method = "all"}} local response_body = {} local theURL = 'http://'..HomeAssistantIP..':'..HomeAssistantPort..'/api/services/notify/'..myEchoDevice r, c, h = http.request { url = theURL, method = "POST", headers = { ["Content-Type"] = "application/json", ["Authorization"] = "Bearer ".. HomeAssistantToken, ["Content-Length"] = request_body:len() }, source = ltn12.source.string(request_body), sink = ltn12.sink.table(response_body) }I don't see the "notify" service in the HA attributes revealed by reactor. Is there a way to access the Home Assistant API through reactor, or do I need to use HTTP requests to initiate services.
-
Hi Patrick! @toggledbits
I don't remember before version 21277 receiving this kind of message.
dbea16f0-39f8-475a-bee8-8899069f2db3-image.png
This is in the log, this warning appears hundreds of times, every 1 second it repeats.
[latest-21281]2021-10-10T16:13:46.107Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...
[latest-21281]2021-10-10T16:13:46.482Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...
[latest-21281]2021-10-10T16:13:46.835Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...As you can see, the rule that has generated this warning is run on demand at 10am, where the information is loaded into local variables, and then I use it to send the information by Telegram, only once a day.
5d55901a-bcbe-4cd6-8989-01d7a0ff9c67-image.png
I started using this matchEntities() instruction recently when it was made available, and I see you have been making recent adjustments. Wouldn't this situation of continuing to evaluate be related?
I will turn the rule off, so as not to generate this situation that surely damages the functioning of the MSR, and I look forward to your comments please.
Thanks
-
Hi!
- id: reactor_system enable: true implementation: SystemController name: Reactor System config: # # The update_interval can be set lower for more frequent updates. The default is 60 # seconds, which is probably fine for most cases, but causes the 15-second load av- # erage to be inaccurate (the first value in reactor_system.system_load). If you # don't care about the 15-second load average, then the default 60 seconds is fine. # This value is expressed in milliseconds. update_interval: 60000 locale: sv-SE #
I would like to try out the swedish translation (thanks @Crille ). I have tried to edit my reactor.yaml file in many ways, but the translation don't show up. I have done a browser hard refresh every time. Where do I go wrong? Here's my latest try:What's the correct syntax, placement and intendention?
Thanks!
/Fanan -
Got a warning that "Rule is being throttled because its update rate exceeds 60 updates per minute. Check for logic errors that may be causing an evaluation loop, or devices that are "flapping".
Device in question here is Aeotec Smart Switch 6 connected to Vera Plus, and its configuration is below:
Screenshot 2021-08-31 at 13.13.22.png
Shouldn't be an evaluation loop as the rule is very simple (two AND'ed conditions where the first checks whether alarm state is "disarmed" and the second if smart switch power switch state is false).
Noticed though at the time of warning that wattage measured/reported was changing quite rapidly, so even though wattage was not used in the rule, could that be the reason for throttling? If so, is there anything else that could be done other than raising minimum change values in device configuration? Would like to retain sensitivity for other purposes.
-
Hey crew, I followed the tutorial to get MSR installed on Rasbperry Pi (bare metal). Just having a little trouble getting Vera to connect to it.
I'm getting error messages-- I searched in the forum and didn't see other people running into these messages. Here are the two main errors I've been getting...
2021-09-21T01:30:36.477Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187836460 failed, reason: socket hang upand
2021-09-21T01:26:08.296Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187568275 failed, reason: connect ECONNREFUSED 10.0.0.141:3480I'm sure it'll be an easy fix, but truthfully I'm stumped here and would love any advice. Thank you!
-
@toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
If so, do you want feedback here or in mantis? -
Let's say I have an array like the one below:
["vera>device_216","vera>device_235","vera>device_241"]How do I remove "vera>device_235" out of it?
Alternatively, when filtering entities:
each id in dynamic_array: getEntity( id ).attributes.x_vera_svc_micasaverde_com_HaDevice1?.CommFailure == 1 ? id : nullHow could I exclude certain id from the array that is produced?
-
I have some battery powered sensors that doesn't report battery level and thought it would be nice if can make MSR to send me a notification if a sensor value doesn't change for 24h.
I tried to make a rule that monitored if a temperature value NOT changes, but in this setup I couldn't choose Sustained For as I expected.
Any way around this?
Any reason that Sustained For can't be used when monitoring a value Change?
Contact Sensor Opened > 1 minute ago how ?
-
Hi
I'm stuck migrating one of my PLEG conditions.
tFrontDoorOpened;NOW>1:00
Which means the trigger "Front Door Opened" happened more than 1 minute ago.
How do I do this in MSR ? An expression I assume ?
I want to use it as part of a Constraint.
Any help please.
Thanks.
-
If you use sustain for 60 seconds, then the sensor would need to be tripped for a minute before going true.
-
I'm not sure that will work for what I am trying to setup.
In fact I don't think I can even replicate the set of conditions I had setup in PLEG for this same rule.
Let me back up and start again, as I am sure there will be a better way of doing this.
Doorbell Camera Motion detected is the trigger for this rule.
The actions "Set Reaction" is to do some TTS and bring up the camera feed on some tablets / TVs etc.
The conditions "Constraints" I only want this rule to run its actions, If the front door hasn't been recently opened or closed for that matter.
e.g. when I come back in to the house and open / close the door to get in, I don't want this rule to run.
But if I am already in the house and its someone else outside mooching about near the doorbell cam, then I do want the rule to run its actions.
-
@cw-kid Try this:
Ignore my device names. They should be at least close enough to express the relationships.
The trigger is the motion sensor. Easy enough.
The constraints have been set to NOT AND, which inverts the output of its logic. The only condition in the constraints is a check to see if the door sensor has changed state, and it delays reset for 60 seconds. When the door changes state to either open or closed, the changes operator will start the 60-second clock and be true that entire period, which means the Constraints will be false (because of the not). When the time expires, the condition will go false, which means the Constraint group is then true, and reactions can run.
In English: run the reactions when the motions sensor trips and the door hasn't changed state in the last 60 seconds.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits said in Contact Sensor Opened > 1 minute ago how ?:
In English: run the reactions when the motions sensor trips and the door hasn't changed state in the last 60 seconds.
Yes that's what I want.
I will give it a try.
Thank you.
-
No worries. FYI, watch out for a small UI bug (fixing, of course): if you edit an existing condition with the changes operator in it, it will put "null" in the operands where they were previously blank before, and when you save that, the condition will stop working. Will fix for today's build, but be on the lookout. Just blank those fields back out before saving. You don't care what the change is (open to close or close to open isn't relevant -- it's either).
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
OK this is what I've got. I also added a check for a virtual switch in the constraints, hope that works.
I haven't tested anything yet.
-
You don't have the delay reset on, it appears (the three dots would appear yellow if you did).
And you're bringing in a group and another device, so that changes the logic. You didn't mention that before, so you need to work it into the logic correctly given that the entire Constraints group is now inverted (false means true and true means false). Have you accounted for that in the test of the switch state? And... why wrapped in a group? Are you going to add more conditions there?
-
I've changed the constraints to this:
I think this is working. If in Vera I trip the front door opened then closed and then trip the doorbell camera motion sensor, the rules reaction is not run as expected.
If I wait over the 60 seconds and trip the doorbell camera motion sensor again, then the rules reaction does run as expected.
I need to test it actually approaching the front door from outside and really opening / closing it, to then hear if it does the TTS announcement or not, that is in the reaction. I shouldn't hear the TTS if I have just changed the doors state etc.
-
Another thing that's been annoying, is when my garden lights via a schedule turn on or off in the back garden, the Hikvision IP camera triggers motion being detected as a result.
I could maybe use this method to stop that happening and stop MSR running the actions "Set Reaction", by checking that the state of the lights hasn't changed within the last X seconds.
Seems to be working, checking if the patio door has changed state in the last 60 seconds OR if the Festoon Lights in the garden have changed state in the last 10 seconds.
