Build: latest-26221-b25bb3e3, Docker on Synology.
Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing.
Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries.
Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart.
Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either.
Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart?
Thanks in advance
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group.
First of all, I think I found a typo in the doc:
primary_attribute: "binary_sensor.state"
primary_attribute_value: |
d = false;
each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d,
d
I think the correct code snippet is d = false,
All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
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.
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well.
As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API.
Updates: (the latest versions first in the list)
OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Edit: Solved in latest-26221.
Bare-metal latest-26193
I have this group:
"OKforLarm":
name: OK för Larm
select:
- include_controller: vera
- include_capability: door_sensor
filter_expression: entity.attributes.door_sensor.state
It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Hey @toggledbits
One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets.
#1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth.
Both will be appreciated, but I understand the technical challenges. Thanks!
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch.
# Multi-System Reactor template docker-compose.yml (version 22160)
#
# Change the lines indicated by "DO"...
#
services:
reactor:
container_name: reactor
environment:
# DO change the TZ: line to set your local time zone.
# See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
TZ: GB
#
# DO NOT change this path. Your directory location is in "source" below.
REACTOR_DATA_PREFIX: /var/reactor
# DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4)
image: toggledbits/reactor:latest-aarch64
restart: "always"
expose:
- 8111
ports:
- 8111:8111
volumes:
# DO change the /home/username/reactor below to the directory you created for
# your local data; DO NOT change the /var/reactor part
- /home/pi/docker/reactor:/var/reactor
- /etc/localtime:/etc/localtime:ro
tmpfs: /tmp
Up and running
Multi-System Reactor
9
Posts
3
Posters
1.9k
Views
3
Watching
-
Ummm, ok this is embarrassing....
I'm actually stuck on creating the simplest rule set / reaction. I can't see anything in the manual that indicates my stupidity, and it's surely not a bug so here goes.
Bare metal install on Debian 10
Simple 'AND' test rule which I can see setting and resetting as the conditions change.I have tried putting a reaction in that rule set to turn on a light. So literally
Entity action > Table Lamp > power_switch.onIf I press the 'Try this action' button from within the reaction, the light goes on.
If I press the 'Run Now' button from the Global reactions list:1.0.2-21350]2022-05-26T16:20:45.257Z <Engine:NOTICE> Starting reaction Test motion lights<SET> (rule-l3n662g0:S) [1.0.2-21350]2022-05-26T16:20:45.257Z <Engine:INFO> Test motion lights<SET> all actions completed. [1.0.2-21350]2022-05-26T16:20:59.510Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.70.64 [1.0.2-21350]2022-05-26T16:21:13.051Z <wsapi:INFO> client "192.168.70.64#4" closed, code=1001, reason= [1.0.2-21350]2022-05-26T16:21:15.726Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) RESET! [1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe lay=50&output_format=json&_r=1653582285543 [1.0.2-21350]2022-05-26T16:26:17.531Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:26:17.536Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:26:17.537Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:26:45.444Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn :upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:26:49.094Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:26:59.543Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:26:59.543Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:03.286Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:03.287Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:20.861Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:20.861Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:23.575Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:23.576Z <Engine:NOTICE> Reaction re-l3n7rrij (Simple Test Reaction) is disabled; run aborted. [1.0.2-21350]2022-05-26T16:27:47.538Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:47.542Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:27:47.543Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:28:14.393Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:14.397Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:14.397Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:28:24.225Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:24.228Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:28:24.229Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:28:35.395Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20200 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20200, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:29:12.974Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20160 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20160, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:29:25.885Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:25.889Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:25.889Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:29:50.139Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:50.143Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:29:50.143Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:33:05.815Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:33:05.825Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:33:05.826Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:35:15.688Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:35:15.692Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:35:15.692Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:37:17.185Z <VeraController:null> VeraController#vera enqueued task for Entity#vera>device_20160 action power_switch.on: task [Object]{ "newTargetValue": "1", "DeviceNum": 20160, "id": "action", "serviceId": "urn:upnp-org:serviceId:SwitchPower1", "action": "SetTarget" } [1.0.2-21350]2022-05-26T16:37:44.912Z <Engine:INFO> Enqueueing "Simple Test Reaction" (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:37:44.916Z <Engine:NOTICE> Starting reaction Simple Test Reaction (re-l3n7rrij) [1.0.2-21350]2022-05-26T16:37:44.917Z <Engine:INFO> Simple Test Reaction all actions completed. [1.0.2-21350]2022-05-26T16:38:39.696Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) SET! [1.0.2-21350]2022-05-26T16:38:39.703Z <Engine:INFO> Enqueueing "Test motion lights<SET>" (rule-l3n662g0:S) [1.0.2-21350]2022-05-26T16:38:39.717Z <Engine:NOTICE> Starting reaction Test motion lights<SET> (rule-l3n662g0:S) [1.0.2-21350]2022-05-26T16:38:39.717Z <Engine:INFO> Test motion lights<SET> all actions completed. [1.0.2-21350]2022-05-26T16:39:10.418Z <Rule:INFO> Test motion lights (Rule#rule-l3n662g0) RESET! [1.0.2-21350]2022-05-26T16:41:56.241Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938494294&Timeout=15&MinimumDelay=50&output_format=json&_r=1653583298238But the light never comes on
Similarly although the test Rule set is supposed to trigger 'Simple Test Reaction', the light never turns on.
The reaction is enabled. The rule set is enabled.
Time zone is BST (trying to conform to the log requests in the manual!)
I'm sorry! It's going to be something really dumb but I've spent about an hour so far
C
-
Screenshot of the ruleset?
*Hubitat C-7 2.5.1.142
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HAOS
Core 2026.7.4
w/ HA Connect ZWA-2
FW: v1.1
SDK: v7.23.1*Prod MSR in docker/portainer
MSR: latest-26193-8dd8f854
MQTTController: 25139
ZWave Controller: 25139 -
@gwp1 said in Up and running:
Screenshot of the ruleset?
Of course, but given the Reaction doesn't do anything...
It's crazy simple. Obviously the rule won't trigger under these circumstances as the motion sensor is not tripped, but even when it does....no reaction
Cheers
C
-
Well, first, you're on an ancient build. I would start by getting on
latest.After that, the log messages are telling you it can't talk to the Vera. Do you see those?
[1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe lay=50&output_format=json&_r=1653582285543Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Well, first, you're on an ancient build. I would start by getting on
latest.After that, the log messages are telling you it can't talk to the Vera. Do you see those?
[1.0.2-21350]2022-05-26T16:25:03.556Z <VeraController:ERR> VeraController#vera update request failed: [FetchError]FetchError: network timeout at: http://192.168.70.249:3480/data_request?id=status&DataVersion=938493960&Timeout=15&MinimumDe lay=50&output_format=json&_r=1653582285543@toggledbits Ahh, OK. I didn't check the version. I'll upgrade.
Yes I did see it can't talk to Vera but given that I can run the action directly I figured that was looking at something else it was trying to do.....
Clearly all the entities are in place, and updating in real time, as is the rule set so my takeaway was that it can talk to Vera (at least for these functions.
Cheers
C
-
OK, updated and working.
Told you it would be something stupid, although it was only 2 months old
Thanks, as ever
C
@catmanv2 said in Up and running:
although it was only 2 months old
If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@catmanv2 said in Up and running:
although it was only 2 months old
If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!
@toggledbits said in Up and running:
@catmanv2 said in Up and running:
although it was only 2 months old
If you mean the release, the stamp 21350 means December 16, 2021, so that's more than five months ago. Things change fast around here!
Ahh I was looking at the date stamp on the download. Thanks, as ever
C
