Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

(Last Updated: 4 April 2021)

Testing reaction set global expression

R

Hi @toggledbits

Just a quick question. I noticed that I can't test a "set variable" action when the rule is not active. I wanted to set a global expression in a reaction and wanted to test it by pushing the "Run action now" button in the border of the reaction, but it didn't do anything. Only when I activated the rule, the button worked.

Is this a bug or is this by design?

I'm running the latest docker build:
latest-23114-e4060aae

Multi-System Reactor
Can't post screen shots here now?

I wanted to asked a question with some screen shots but I am getting an error when I try to copy and paste an image from paint into this forum post editor.

"Error something went wrong parsing server response" it was saying.

Multi-System Reactor
Home Assistant add-on

M

I've done a bit of repackaging of MSR to make it work as an add-on under Home Assistant mostly for my own purposes but hopefully it makes it a bit easier to install and get going.
GitHub - mrw298/hassio-reactor-addon GitHub - mrw298/hassio-reactor-addon
Contribute to mrw298/hassio-reactor-addon development by creating an account on GitHub.

Multi-System Reactor
DelayLight replicate in MSR

P

Hi Everyone,

I am just starting to move over from Vera to Home Assistant using MSR.

On vera I had been using DelayLight. I have tried to replicate it with help from youtube (https://www.youtube.com/watch?v=fc_ij0D1hXE) Reactor for Vera #006 - Emulating DelayLight in Reactor.

I have created 6 rules that sort of work. but I am just wondering if this is best practice or should can it be built in 1 rule like the old vera way?

Multi-System Reactor
Having an Echo device play mp3?

F

Hi!
I tried to find an answer in both the forum and by myself, without any luck. I'm trying to make my Echo device play a mp3 file. The same mp3 file is easy to play with other smart speakers (Sonos, Google/Nest) - that it no problem. Same approch do not work with Echo devices. The mp3 files I want to use is located on my HA installation (config/www/audio), running on ver. 2023.5.4. I have MSR ver 23114.
Is there a way to do this easily?
Thanks!
/Fanan

Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements

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.

Multi-System Reactor
Sending numbers as payload type in actions enhancement

J

I'm controlling a HVAC device through the MQTTController. While setting up the entity config in reactor.yaml, I started with this on the action block:
set_setpoint: topic: "ezlo_mqtt/set/item/%topic%/set/Tsetpoint" payload: expr: "parameters.setpoint" type: raw
However, as the setpoint is a number in the UI, things were not fully parseable as a number and nothing was outputted to mqtt.

So I've added this code to MQTTController.js at line 1449 to add the payload type 'number':
} else if ( 'number' === act.payload.type ) { payload = String( payload ); } else if (''raw' !== ( act.payload.type || 'raw' ) ) {
After this change, I was able to set the payload type to number:
set_setpoint: topic: "ezlo_mqtt/set/item/%topic%/set/Tsetpoint" payload: expr: "parameters.setpoint" type: number
And things worked as intended, being able to send numbers in the actions bit of a rule set.

Multi-System Reactor
JSON payload in MQTTController entities actions (+ reverse color mapping to RGB)

M

Some background
I'm trying to integrate a Zigbee device into the MSR using zigbee2mqtt bridge and MQTTController. The device in question is a cheap mood light that has following properties that I'd like to control:
switch (on/off) brightness color
I'v already managed to get the switch part working and can toggle the light on/off. Also the brightness value is mapped back to MSR. In zigbee2mqtt it has a value range from 0 to 254, so this the reason for the expression:
expr: 'payload.brightness / 254'
Here's the entity definition (don't know whether the type should be something else than the Switch)
zigbee-lidl-mood-light: name: 'Lidl Mood Light' friendly_name: 'Mood Light' type: Switch uses_template: lidl-moodlight
And the corresponding template (NOTE: rgb_color has not been defined in this example):
lidl-moodlight: init: "zigbee2mqtt/%friendly_name%/get/state" query: "zigbee2mqtt/%friendly_name%/get/state" capabilities: - power_switch - toggle - dimming primary_attribute: power_switch.state events: "zigbee2mqtt/%friendly_name%": "power_switch.state": json_payload: true expr: 'upper(payload.state) == "ON"' "dimming.level": json_payload: true expr: 'payload.brightness / 254' actions: power_switch: "on": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'ON' "off": topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'OFF' set: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: expr: "parameters.state ? 'ON' : 'OFF'" type: raw toggle: topic: "zigbee2mqtt/%friendly_name%/set/state" payload: 'TOGGLE'
The problem
In order to control the brightness or the RGB color values, I would have send a JSON payload in corresponding actions. But I have no idea how to define it in the template. The reason why the switch part is working is that the zigbee2mqtt accepts also plain ON / OFF / TOGGLE string payloads in that case.

But the brightness should be controlled with the following payload:
{"brightness": 196}
And the RGB color like:
{"color":{"rgb":"46,102,150"}}
Here's the link for the documentation (the Exposes part defines the messages).

So how should I define the JSON payload for example for the dimming action? It definitely should be some sort of expressions since I have to map the MSR real value (0...1) to (0...254) for the zigbee2mqtt.
actions: dimming: set: topic: "zigbee2mqtt/%friendly_name%/set" payload: expr: ????? type: json
Another problem is the RGB value. I could use the rgb_color capability for the setting but the problem is that the zigbee2mqtt only reports the current color in hue/saturation or xy coordinates.

Here's an example of published message after setting the color:
Topic: zigbee2mqtt/Mood Light QoS: 0 { "brightness":254, "color":{ "hue":240, "saturation":100, "x":0.1355, "y":0.0399 }, "color_mode":"xy", "color_temp":574, "linkquality":96, "state":"ON" }
I would have to map those values back to RGB, but is it even possible with existing constructs in MQTTController's templates?

Help would be appreciated @toggledbits
br,
mgvra

Multi-System Reactor
Home Assistant push notification for Reactor version update possible?

T

Good evening,
I was wondering if it would be possible to send out a push notification when there is a update to MSR to HA users. I know how to set up notifications through Reactor to HA users, but I'm unsure what to look for in regards to updates. I know that MSR itself will tell me there is an update, but unless I'm logged into MSR in a browser, I'm not always going to see that.

Just updated to latest-23114-e4060aae MSR
Home Assistant 2023.4.6
Supervisor 2023.04.1
Operating System 10.0

Multi-System Reactor
Disabled groups in reactions

MSR tooltip says that "disabled groups are ignored, as if they did not exist (conditions don't run)".

Just want to clarify if it's by design that actions beneath disabled groups should run? They do run, but intuitively I was expecting them to be disabled as well.

Running the latest build under Docker.

Multi-System Reactor
MSR Not Actioning

S

I am running MSR on a small windows machine. Earlier this week, the machine restarted and Reactor restarted as well. I am now experiencing an issue in which Reactor doesn't seem to be making any updates or calling any scenes. Reactor is communicating with Vera and all entities seem to be accurate (ie lights on or off) and manually clicking on Actions seems to work just fine. The Status page also seems accurate and displays rules automatically being SET and RESET. But when the Reaction changes from SET to RESET or vice versa, none of the actions are actually invoked.

For example, I manually ran a SET action at 11:29 and my lights turned on. At 11:30, the Status Dashboard shows the rule updating to RESET, but the lights did not turn off.

I have included a screenshot of the rule history below as well as the log for these times as well.

Any ideas on what can be going on? I have tried restarting the Windows machine as well as Reactor multiple times to see if this fixes this behavior but have not had any success. Any information is appreciated.

78f9f75f-d24c-4ff4-a23a-fda0c98cbcbc-image.png

[stable-22274]2023-04-14T03:29:39.161Z VeraController:null VeraController#vera enqueued task for Entity#vera>scene_3 action script.run: task [Object]{ "SceneNum": "3", "DeviceNum": 0, "id": "action", "serviceId": "urn:micasaverde-com:serviceId:HomeAutomationGateway1", "action": "RunScene" }
[stable-22274]2023-04-14T03:29:39.587Z VeraController:INFO VeraController#vera 0 dead entities older than 86400000s purged
[stable-22274]2023-04-14T03:29:45.763Z Rule:NOTICE Evening Lights Rule (Rule#rule-la4gnzmt) configuration changed; reloading
[stable-22274]2023-04-14T03:29:45.766Z Rule:NOTICE Evening Lights Rule (Rule#rule-la4gnzmt) stopping
[stable-22274]2023-04-14T03:29:45.772Z Rule:NOTICE Evening Lights Rule (Rule#rule-la4gnzmt) stopped
[stable-22274]2023-04-14T03:29:45.773Z Rule:NOTICE Rule#rule-la4gnzmt (Evening Lights Rule) starting
[stable-22274]2023-04-14T03:29:45.777Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) starting evaluation; because startup
[stable-22274]2023-04-14T03:29:45.779Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluated; rule state transition from RESET to SET!
[stable-22274]2023-04-14T03:29:45.802Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluation complete
[stable-22274]2023-04-14T03:29:45.809Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) started
[stable-22274]2023-04-14T03:29:45.811Z Engine:INFO Enqueueing "Evening Lights Rule<SET>" (rule-la4gnzmt:S)
[stable-22274]2023-04-14T03:29:45.840Z Engine:NOTICE Starting reaction Evening Lights Rule<SET> (rule-la4gnzmt:S)
[stable-22274]2023-04-14T03:29:45.842Z Engine:INFO Evening Lights Rule<SET> all actions completed.
[stable-22274]2023-04-14T03:30:00.008Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) starting evaluation; because timer-trigger Timer#rule-la4gnzmt
[stable-22274]2023-04-14T03:30:00.024Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluated; rule state transition from SET to RESET!
[stable-22274]2023-04-14T03:30:00.055Z Rule:INFO Evening Lights Rule (Rule#rule-la4gnzmt) evaluation complete
[stable-22274]2023-04-14T03:30:00.062Z Engine:INFO Enqueueing "Evening Lights Rule<RESET>" (rule-la4gnzmt:R)
[stable-22274]2023-04-14T03:30:00.079Z Engine:NOTICE Starting reaction Evening Lights Rule<RESET> (rule-la4gnzmt:R)
[stable-22274]2023-04-14T03:30:00.080Z Engine:INFO Evening Lights Rule<RESET> all actions completed.
[stable-22274]2023-04-14T03:30:01.099Z VeraController:INFO VeraController#vera 0 dead entities older than 86400000s purged

Multi-System Reactor
Forecast attribute in array

T

Good morning,
I'm sorry if this has been asked (I did search, but couldn't find anything), I've run into a bit of a snag in some of my reactions using OpenWeatherMap. I made the assumption (you know what they say about assume), that the Forecast Temperature value was the Daily High, when in fact it's the current Temperature. It turns out you can get that information from OpenWeatherMap, but it's a on paid tier API.

I am looking at alternatives, such as the haas>weather_forcast_home value from Home Assistant, as well as Pirate Weather, however, the value of those Forecast High is in an array.

27f55490-7869-434f-bcac-e1e5398b3aea-image.png

1df1a841-90f0-4dbe-8f73-ff3fc04595e2-image.png

How do I pull the values in that array out and make them useful in MSR?

I'm running latest-23078-d592d400 and HA 2023.3.5 on RPI4

Multi-System Reactor
[Closed] Pushover sounds in MSR

G

To anyone using Pushover who has added Custom sounds to your Pushover account: how did you get them to appear in the sounds dropdown in MSR?

Multi-System Reactor
Home assistant addon: Import Vera/Openluup backup

R

Hi guys,

I want to import my reactor sensors in the MSR addon for Home Assistant, but I can't find the app.js file anywhere. So now I don't know where to put the backup file.

I have not tried to put it in the main directory (config/reactor) yet. Wanted to know if I'm the only one with the problem.

Reactor addon: v0.0.8
MSR: 23063-c464b685
Home Assistant 2023.3.3
Supervisor 2023.03.1
Operating System 9.5
Frontend 20230202.0 - latest

I started with v0.0.7, have just updated everything. Still no file.

Multi-System Reactor
Reactor Ex Machina

G

@toggledbits was looking thru rule sets and updating which (new) lights I wanted REMII to impact and saw that this...

4711b0df-5e98-4992-bb25-d0e53203f0e8-image.png

...is showing as (missing) in the rule Deactivatedand looking in the dropdown of Variables it appears I cannot select that local expression (only Global) as I did when originally building this out back in 2021.

27f7025c-057e-441a-88ea-dc4bdf39614d-image.png

In looking at the rule Active Period I'm seeing:
487074ef-3bfa-4a84-b03d-ed6d920c118c-image.png which appears to be pointing to setting a variable in a rule?

It's admittedly been a couple years since this was built and it's def not fresh in my memory.

Multi-System Reactor
Function sanity check please

3

MSR: latest-23078-d592d400
--Docker image on unRAID
Hubitat C-7: 2.3.5.121

I'm always looking to simplify my rules and reactions and having finally grasped the Array function with a loop of perform.Action, I decided to re-write one of my rules. The kids like to play music on the Echo devices at a high volume, and I also have TTS loud during the night if a door/window are to open. In order to not have her yell at me later, I wrote a rule that resets the volume on each Echo device to a level of 2. However having 7 Echo's, there are many steps in my Reaction. Set the volume on device 1, wait a few seconds, set the volume on the device 2, wait, and so on.

Sample snippet of the set reaction: (This works BTW.)
2f5aafc0-bf97-4622-b41c-60649253590e-image.png

To make it better, I created an array of the devices and want to run a perform.Action command. Less steps with the same results. Or so I thought. The end result is now a volume level of 0 or 1. I think the Echo gets confused. Either way, not a level of 2 like I was expecting. BTW volume 1 across the room is too low, in case you were wondering.

New set reaction:
da62dfb0-f433-4fc6-897f-d38c190f8c9a-image.png
${{ each device in Echo_devices: performAction( device, 'volume.set', { level:0.20 } ); 0 }}
The av_transport.stop works as expected. The issue is with the volume.set, {level:0.20}. Do I have something wrong in my command?

Global expressions used:
8d054dca-20dc-4e97-aa6d-4537c9da4ea9-image.png

e3e388d3-f18e-4744-8eee-432234161739-image.png

Multi-System Reactor
Can I use Dynamic Group Control for Triggers and Reactions?

T

Good evening all,
I've run across a quirk with my iBlinds motors in Home Assistant. Each iBlinds zwave motor has two controls that I can use. One is a switch, and one is a cover control.

ee654e5d-d191-4082-a7f2-6b161923de75-image.png cid:A1190F3F-FB02-4332-93DE-9A15A490D9AB

The switch control is a binary on/off switch. On, the blind goes to the "open" position (v2 controllers, 50%, v3 controllers user definable parameter)

If you click on the cover icon, it moves between two positions. Essentially, it's closed in both positions, just 180 degrees apart. The cover control does give you the granularity to move to any position between 0 and 100, which is sometimes useful, when you just don't want it open or closed, such as letting some light in, but closing it enough when the sun is shining directly into the window and blinding everyone.

Here's the problem, which I've brought up with iBlinds support, and they're singing Simon and Garfunkel (Sound of Silence). The two controls don't update each other. If I open or close using the switch, the cover position value doesn't change. If I open or close using the cover control, the switch doesn't change to on or off. I've verified that this isn't just an issue with the dashboard/templates I'm using by going into the developer tools on HA and the values do not change. I've also checked those values in Reactor (Entities tab) and they do not update properly.

I've come up with a Reactor work around which sort of forces the controls to update. If anyone knows of a better way, please tell me. I have two rules set up that monitor for changes in the switch state, that then performs a x_haas_cover.set_cover_position to either 0 or 50 for either to off or to on respectively.

40b352f9-c599-4768-ac02-cd7bcb4b3b33-image.png

db1d73d4-1fc9-4785-a75a-068c42e63b48-image.png

This is sort of a one way street at the moment. I don't have a reverse rule set up to change the switch value, but the current rule seems more of an issue.

All that being said. I have 14 iBlinds motors in my home. That would mean 28 rules in Reactor. I know how to set up a Dynamic Group Control for Triggers. I put all 14 switches in the reactor.yaml file, and I can use those for triggers. How would I go about using 14 corresponding cover controls for the reactions?

It may be a simple matter, but I'm not sure. One thing i can say is the name of the switch and cover entities are the same, except for the control type:

0bbf3cb0-ab71-4c9c-b254-d3009f5b092c-image.png

Edit:

Running:
Reactor: latest-23078-d592d400
Home Assistant 2023.3.5
Supervisor 2023.03.3
Operating System 9.5
Frontend 20230309.1 - latest

Multi-System Reactor
What does [Error] terminated [-] mean?

Post has been updated.

Need some guidance in determining what this error means.

Running Reactor latest-23078-d592d400; ZWaveJSController; Docker on Synology; Home Assistant 2023.3.6; Z-Wave JS UI 8.11.1

I have searched the site and could not find anything related to my question.

I know what the rule does. Yet, I cannot find the relationship with this error.

If someone could point me in the right direction, it would be appreciated.

Thanks in advance

Rule is as follow:

If the garage side door opens when the alarm is not armed and that both my spouse and I are at home:

Set Reaction: turn on the Siren_8 (basically a two seconds beep that was configured with the Aeotec Siren to warn us that the door is open)

Reset Reaction: turn off the Siren_8 in case it wants to keep beeping

Error terminated.jpg

Here's the updated error.
[latest-23078]2023-03-26T22:31:36.772Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:36.772Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:36.773Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.773Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.782Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.783Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.790Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.791Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.799Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:36.799Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:36.800Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:36.800Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:36.800Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:36.801Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.802Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (false), but rule state remains RESET [latest-23078]2023-03-26T22:31:36.804Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:36.804Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:36.812Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:36.812Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:36.814Z <Engine:INFO> Enqueueing "Door Sensors State<RESET>" (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:36.815Z <Engine:INFO> Enqueueing "Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET>" (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:36.817Z <Engine:INFO> Enqueueing "Toggle Vestibule scene 003 LED color state between green/blue<RESET>" (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:36.819Z <Engine:NOTICE> Starting reaction Door Sensors State<RESET> (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:36.820Z <Engine:NOTICE> Starting reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:36.822Z <Engine:NOTICE> Starting reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:36.823Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Switch#zwavejs>128-0 with [Object]{ "parameter": "9", "size": 1, "value": 2, "bitmask": 0 } [latest-23078]2023-03-26T22:31:36.830Z <HassController:INFO> HassController#hass action x_hass_input_text.set_value([Object]{ "value": "Closed" }) on Entity#hass>input_text_h_door_sensors_state succeeded [latest-23078]2023-03-26T22:31:36.831Z <Engine:INFO> Resuming reaction Door Sensors State<RESET> (rule-lerjv6if:R) from step 1 [latest-23078]2023-03-26T22:31:36.832Z <Engine:INFO> Door Sensors State<RESET> all actions completed. [latest-23078]2023-03-26T22:31:37.043Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) starting evaluation; because entity-changed ValueSensor#hass>sensor_garage_side_door_openclose_battery_level [latest-23078]2023-03-26T22:31:37.044Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_garage_side_door_openclose_battery_level [latest-23078]2023-03-26T22:31:37.045Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) trigger evaluation result is true (previously true) [latest-23078]2023-03-26T22:31:37.046Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) evaluated; trigger state unchanged (true); rule state remains SET [latest-23078]2023-03-26T22:31:37.060Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) trigger evaluation result is true (previously true) [latest-23078]2023-03-26T22:31:37.060Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluated; trigger state unchanged (true); rule state remains SET [latest-23078]2023-03-26T22:31:37.062Z <Rule:INFO> Batteries State (rule-leucn9pp in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:37.062Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:37.146Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) starting evaluation; because entity-changed Group#groups>low_battery [latest-23078]2023-03-26T22:31:37.156Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) trigger evaluation result is true (previously true) [latest-23078]2023-03-26T22:31:37.157Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluated; trigger state unchanged (true); rule state remains SET [latest-23078]2023-03-26T22:31:37.157Z <Rule:INFO> Notification: Battery - Low level warning (rule-lbh1vt4k in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:37.161Z <Engine:INFO> Resuming reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) from step 2 [latest-23078]2023-03-26T22:31:37.162Z <Engine:INFO> Toggle Vestibule scene 003 LED color state between green/blue<RESET> all actions completed. [latest-23078]2023-03-26T22:31:37.316Z <HassController:INFO> HassController#hass action x_hass_siren.turn_off([Object]{ }) on Entity#hass>siren_siren_8 succeeded [latest-23078]2023-03-26T22:31:37.317Z <Engine:INFO> Resuming reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> (rule-lbmoup28:R) from step 2 [latest-23078]2023-03-26T22:31:37.317Z <Engine:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> all actions completed. [latest-23078]2023-03-26T22:31:38.892Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:38.892Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:38.893Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:38.894Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.894Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.907Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.907Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.916Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.917Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.925Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:38.925Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:38.926Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:38.926Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:38.926Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:38.927Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.930Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) constraints not met! [latest-23078]2023-03-26T22:31:38.930Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (true), but rule state remains RESET [latest-23078]2023-03-26T22:31:38.931Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:38.932Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:38.939Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:38.939Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:38.941Z <Engine:INFO> Enqueueing "Door Sensors State<SET>" (rule-lerjv6if:S) [latest-23078]2023-03-26T22:31:38.942Z <Engine:INFO> Enqueueing "Notification: Home Security - Garage side door just opened (Disarmed Only)<SET>" (rule-lbmoup28:S) [latest-23078]2023-03-26T22:31:38.943Z <Engine:INFO> Enqueueing "Toggle Vestibule scene 003 LED color state between green/blue<SET>" (rule-lfn441bq:S) [latest-23078]2023-03-26T22:31:38.945Z <Engine:NOTICE> Starting reaction Door Sensors State<SET> (rule-lerjv6if:S) [latest-23078]2023-03-26T22:31:38.946Z <Engine:NOTICE> Starting reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<SET> (rule-lbmoup28:S) [latest-23078]2023-03-26T22:31:38.948Z <Engine:NOTICE> Starting reaction Toggle Vestibule scene 003 LED color state between green/blue<SET> (rule-lfn441bq:S) [latest-23078]2023-03-26T22:31:38.949Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Switch#zwavejs>128-0 with [Object]{ "parameter": "9", "size": 1, "value": 1, "bitmask": 0 } [latest-23078]2023-03-26T22:31:38.956Z <HassController:INFO> HassController#hass action x_hass_input_text.set_value([Object]{ "value": "Open" }) on Entity#hass>input_text_h_door_sensors_state succeeded [latest-23078]2023-03-26T22:31:38.957Z <Engine:INFO> Resuming reaction Door Sensors State<SET> (rule-lerjv6if:S) from step 1 [latest-23078]2023-03-26T22:31:38.958Z <Engine:INFO> Door Sensors State<SET> all actions completed. [latest-23078]2023-03-26T22:31:39.284Z <Engine:INFO> Resuming reaction Toggle Vestibule scene 003 LED color state between green/blue<SET> (rule-lfn441bq:S) from step 2 [latest-23078]2023-03-26T22:31:39.284Z <Engine:INFO> Toggle Vestibule scene 003 LED color state between green/blue<SET> all actions completed. [latest-23078]2023-03-26T22:31:39.530Z <HassController:INFO> HassController#hass action x_hass_siren.turn_on([Object]{ "tone": "30" }) on Entity#hass>siren_siren_8 succeeded [latest-23078]2023-03-26T22:31:39.531Z <Engine:INFO> Resuming reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<SET> (rule-lbmoup28:S) from step 2 [latest-23078]2023-03-26T22:31:39.531Z <Engine:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only)<SET> all actions completed. [latest-23078]2023-03-26T22:31:40.341Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_siren_siren_active_8 [latest-23078]2023-03-26T22:31:40.351Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:40.352Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:40.353Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:40.645Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) starting evaluation; because entity-changed Group#groups>water_leak_detected [latest-23078]2023-03-26T22:31:40.654Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:40.654Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:40.655Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.311Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:41.312Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:41.313Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:41.315Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.315Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.327Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.327Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.335Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.336Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.343Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:41.343Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:41.344Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:41.344Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:41.344Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.345Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.346Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (false), but rule state remains RESET [latest-23078]2023-03-26T22:31:41.347Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is false (previously true) [latest-23078]2023-03-26T22:31:41.348Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from SET to RESET! [latest-23078]2023-03-26T22:31:41.354Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:41.355Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:41.356Z <Engine:INFO> Enqueueing "Door Sensors State<RESET>" (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:41.357Z <Engine:INFO> Enqueueing "Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET>" (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:41.360Z <Engine:INFO> Enqueueing "Toggle Vestibule scene 003 LED color state between green/blue<RESET>" (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:41.361Z <Engine:NOTICE> Starting reaction Door Sensors State<RESET> (rule-lerjv6if:R) [latest-23078]2023-03-26T22:31:41.363Z <Engine:NOTICE> Starting reaction Notification: Home Security - Garage side door just opened (Disarmed Only)<RESET> (rule-lbmoup28:R) [latest-23078]2023-03-26T22:31:41.365Z <Engine:NOTICE> Starting reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) [latest-23078]2023-03-26T22:31:41.366Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing zwave_device.set_config on Switch#zwavejs>128-0 with [Object]{ "parameter": "9", "size": 1, "value": 2, "bitmask": 0 } [latest-23078]2023-03-26T22:31:41.374Z <HassController:INFO> HassController#hass action x_hass_input_text.set_value([Object]{ "value": "Closed" }) on Entity#hass>input_text_h_door_sensors_state succeeded [latest-23078]2023-03-26T22:31:41.375Z <Engine:INFO> Resuming reaction Door Sensors State<RESET> (rule-lerjv6if:R) from step 1 [latest-23078]2023-03-26T22:31:41.375Z <Engine:INFO> Door Sensors State<RESET> all actions completed. [latest-23078]2023-03-26T22:31:41.497Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) starting evaluation; because entity-changed ValueSensor#hass>sensor_docker_hub [latest-23078]2023-03-26T22:31:41.498Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:41.498Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:41.499Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.501Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_docker_hub_update_available [latest-23078]2023-03-26T22:31:41.502Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:41.502Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:41.503Z <Rule:INFO> Notification: Update Available - Home Assistant (rule-lbmnmfds in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:41.709Z <Engine:INFO> Resuming reaction Toggle Vestibule scene 003 LED color state between green/blue<RESET> (rule-lfn441bq:R) from step 2 [latest-23078]2023-03-26T22:31:41.709Z <Engine:INFO> Toggle Vestibule scene 003 LED color state between green/blue<RESET> all actions completed. [latest-23078]2023-03-26T22:31:49.669Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.670Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.670Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.670Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:49.675Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.675Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.676Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.676Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:49.678Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.679Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.679Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.680Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:49.682Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) starting evaluation; because entity-changed System#reactor_system>system [latest-23078]2023-03-26T22:31:49.683Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:49.683Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:49.683Z <Rule:INFO> Notification: Update Available - Reactor (rule-laeg075n in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:52.484Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_siren_siren_active_8 [latest-23078]2023-03-26T22:31:52.485Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:52.485Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:52.486Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) starting evaluation; because entity-changed BinarySensor#hass>binary_sensor_garage_side_door_openclose_window_door_is_open [latest-23078]2023-03-26T22:31:52.502Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) trigger evaluation result is false (previously false) [latest-23078]2023-03-26T22:31:52.502Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23078]2023-03-26T22:31:52.505Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.505Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.515Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.515Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.524Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.525Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.537Z <Rule:INFO> Notification: Home Security - Open/close water main shut-off valve (rule-kvo8us5v in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) starting evaluation; because data-changed Data#states:cs-rule-lfn41thm [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Any door open? (rule-lfn41thm in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:52.538Z <Rule:INFO> Door Sensors State (rule-lerjv6if in Control Room) evaluation complete [latest-23078]2023-03-26T22:31:52.539Z <Rule:INFO> Notification: Home Security - Garage side door just opened (Disarmed Only) (rule-lbmoup28 in Notifications) evaluation complete [latest-23078]2023-03-26T22:31:52.540Z <HassController:INFO> HassController#hass action x_hass_siren.turn_off([Object]{ }) on Entity#hass>siren_siren_8 succeeded [latest-23078]2023-03-26T22:31:52.541Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.542Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) constraints not met! [latest-23078]2023-03-26T22:31:52.542Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluated; trigger state changed (true), but rule state remains RESET [latest-23078]2023-03-26T22:31:52.544Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) trigger evaluation result is true (previously false) [latest-23078]2023-03-26T22:31:52.544Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluated; rule state transition from RESET to SET! [latest-23078]2023-03-26T22:31:52.551Z <Rule:INFO> Alarm triggered (rule-lbqu752y in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:52.552Z <Rule:INFO> Toggle Vestibule scene 003 LED color state between green/blue (rule-lfn441bq in Home Security) evaluation complete [latest-23078]2023-03-26T22:31:52.565Z <Engine:NOTICE> [Engine]Engine#1 entry 171 reaction rule-lbmoup28:R: [Error] terminated [-] [latest-23078]2023-03-26T22:31:52.565Z <Engine:CRIT> Error: terminated [-] Error: terminated at Engine._process_reaction_queue (/opt/reactor/server/lib/Engine.js:1555:47) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5)

Multi-System Reactor
[RESOLVED] How quickly should logs rotate?

3

MSR: latest-23078-d592d400
--Docker image on unRAID
Hubitat: 2.3.5.121

I was having an issue this morning where MSR wasn't seeing any hub updates from my Hubitat. In looking at the logs I was seeing pages of "reactor.log size hit rotation limit, rotating" messages. I purged these logs and restarted MSR thinking the logs were the cause of being stuck or something. I also changed the default from 2 MB and 5 logs to 3 MB and 9 logs. Long story short, that wasn't the issue and my HE needed a reboot. I had just rebooted a couple of days ago, so I didn't think that was the problem.

Back on topic here. Everything seems to be communicating and MSR is seeing the updates now, however I feel that my logs filled up way too fast. Granted 3 MB isn't very large these days. Is it normal to take about 45 minutes to fill up nine 3 MB log files? Or does this seem excessive? I only changed the size and qty in my logging.yaml file.

cedba928-6adc-4f24-be57-4fa4184e9128-image.png aa2c5edf-629f-45a3-8083-6f3dece48e05-image.png

Multi-System Reactor
ZWaveJSController won't connect to ZWaveJS under Home Assistant/HACS

T

@toggledbits said in Can I use Dynamic Group Control for Triggers and Reactions?:

Note that @gwp1 is using ZWaveJSController to interface with iBlinds, not HassController. So this is more direct control that circumvents HA's interpretation.

I saw that, but ZWaveJSController doesn't seem to be an option in my instance. I do use ZWaveJS UI on HA. What's the difference here?

Edit. I found it in your documentation. I tried installing it, but Reactor is telling me that the zwavejs controller is down. Do I need to do anything on Home Assistant to make it available?

d4f165eb-ba31-49e3-9f0c-ff49e4710f4e-image.png

The WS Server is enabled and set to port 3000. That's what I set up in my reactor.yaml file.
- id: zwavejs implementation: ZWaveJSController enabled: true config: source: ws://192.168.1.141:3000 # modify the IP address as needed;

Multi-System Reactor

For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

Status Tab Preview

Multi-System Reactor

229

toggledbits last edited by toggledbits

The status tab is starting to come together, and is supported in part by a new Alerts mechanism.

This is the place for discussion about that. Please don't open PRs at this point, as I'm not finished with the work. I estimate I'm about half done with what I know I have to do so far, and I imagine more to come later. If you have bugs to report, I'll take them here in this thread.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
1 Reply Last reply
Reply Quote 2
LibraSun last edited by

It's lookin' mighty good. Props to you, sir!
1 Reply Last reply
Reply Quote 0
PerH last edited by

Nice! is a "Changed by" (rule/expression) column in that lower table in the works as well?
1 Reply Last reply
Reply Quote 0
toggledbits last edited by

In the Entities? Probably not. How would I know what changed it?
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
1 Reply Last reply
Reply Quote 0
Matohl last edited by

Nice, good work! I wait with my suggestions until I see what you have in mind.
1 Reply Last reply
Reply Quote 0
LibraSun last edited by LibraSun
The ALARM BELL already saved my bacon. A couple of otherwise "proven good" Rules evidently went rogue after I switched from detecting House Mode with Reactor (which yielded numbers 1, 2, 3, 4) to MSR's Vera > HouseMode feature (which yields strings "home", "away", "night" and "vacation"). This meant rewiring my logic flow, which got a bit out of kilter.

Anyway, MSR's "Status" report caught some unexpected "NULL" evaluations in the Trigger conditions, which led me down the proper rabbit hole to fix those and get both Rules back on track.

TIP: To account for the "NULL" condition (coming from a failed lookup in a "table" object I created -- see the ecobee plug-in is notorious for throwing an empty value back for Thermostat Mode in certain not-so-rare circumstances), I simply moved from:
```
[ Expression Value ] [ modesMatch ] [ is FALSE ]  // was bombing when NULL
```
to
```
[ Expression Value ] [ modesMatch ] [ <> ] [ TRUE ]  // works when FALSE or NULL
```
P.S. Oddly, the "Alarm Bell" icon remains red even after resolving the alerted conditions. (Solved with browser refresh)
1 Reply Last reply
Reply Quote 1
cw-kid last edited by cw-kid

The new version with alert bell seems to have messed up the menu when viewing on my phone, even in desktop mode. I can't get to the top of the menu and rule sets etc.

EDIT: MSR version 21091 fixes this issue
1 Reply Last reply
Reply Quote 0
cw-kid last edited by

I also have this alert and cannot get rid of it when pressing the X
1 Reply Last reply
Reply Quote 0
cw-kid last edited by cw-kid

Vera "Rooms" are appearing in Recently Changed Entities for some reason ?

EDIT: MSR version 21091 fixes this issue
1 Reply Last reply
Reply Quote 0
PerH @toggledbits last edited by

@toggledbits i'm thinking if some rule in reactor changed the state of the entity, it could be a column to identify that rule. changes done by others could simply state "other" or similar.

This is related to the other inquiry i had about entity change history..
1 Reply Last reply
Reply Quote 0
toggledbits last edited by

Yeah, but there's no way to determine that.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
1 Reply Last reply
Reply Quote 0
Matohl @cw-kid last edited by

@cw-kid Same here. It is flooded by changes from the rooms
1 Reply Last reply
Reply Quote 0
LibraSun last edited by

One of my Alerts says "
Unable to resolve global expression "timeStamp"
Last 22:23:06; this alert has repeated 3 times." ... yet I have no such variable. Perhaps I once did but not now that I can tell.
1 Reply Last reply
Reply Quote 0
toggledbits last edited by toggledbits

Something is referring to it...

...and yes I realize I need to make finding that something easier but, steps... one thing at a time...
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
1 Reply Last reply
Reply Quote 1
LibraSun last edited by LibraSun
Just as:
```
Reaction task "66" failed due to an exception
TypeError: Cannot read property 'length' of undefined
Last 09:21:10
```
must point to /something/ but I stand to be educated on where to look. The reactor Log, perhaps?

EDIT: Found line by searching for "length" in reactor.log.1 (downloaded from Synology NAS). Doesn't specify exactly what component the problem is with, but it did name the affected Rule. I suspect it's to do with a long JSON string in one of its variables that happened to contain an empty array as a 'value'.
1 Reply Last reply
Reply Quote 1
toggledbits last edited by

Yes, log. All kids love log.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
1 Reply Last reply
Reply Quote 0
LibraSun last edited by

Do we really want disabled rules to appear among the list of Set Rules in status?
1 Reply Last reply
Reply Quote 0
cw-kid last edited by

Can confirm the new Alert notification is working in a Reaction and puts an alert right on to this Status page under Current Alerts.
1 Reply Last reply
Reply Quote 1
LibraSun last edited by

Neat! Will "clicking the red bell" eventually take us directly to the Alerts panel?
1 Reply Last reply
Reply Quote 0
LibraSun last edited by
Also, so as to minimize the number of "SET" (but otherwise inactive) Rules, I decided to change all of my
```
[ Entity Attribute ]  [ X ]  [ is FALSE] // remains true indefinitely when OFF
```
to
```
[ Entity Attribute ]  [ X ]  [ changes ]  [ (any) ] to  [ FALSE ] // only true briefly when turned OFF
```
Dunno if I'm OCD or just didn't want Status implying that something was "going on" when it's not.
1 Reply Last reply
Reply Quote 0
Locked by toggledbits

1 / 1