Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable.
I have a couple of them. ie, this is from ESPHome via HASS.
x_hass.domain="fan"
x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan"
x_hass.floor_id=null
x_hass.services=["fan","esphome"]
x_hass.source="esphome"
x_hass.state="off"
x_hass_attr.friendly_name="Seashell Hood Ventilation Fan"
x_hass_attr.percentage=50
x_hass_attr.percentage_step=25
x_hass_attr.preset_mode=""
x_hass_attr.preset_modes=[]
x_hass_attr.supported_features=49
Thanks.
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
Reactor build 26116: empty group reaction
Multi-System Reactor
18
Posts
3
Posters
1.5k
Views
3
Watching
-
@gwp1 unrelated.
I'll try to find a few minutes to grab logs. I gave a quick look and saw nothing screaming.
*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 -
I'll try to find a few minutes to grab logs. I gave a quick look and saw nothing screaming.
@gwp1 Logs probably long gone if you've already modified the reaction. It would help to see the group in its original form, though.
-
@gwp1 Logs probably long gone if you've already modified the reaction. It would help to see the group in its original form, though.
@toggledbits I still have the ruleset, just disabled. Easy enough to disable the temporary ones and re-enable this one and try to trigger it. (I had a smart moment!)
*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 -
OK. Here's the release note I'm making on this for the next build:
- The behavior of empty "group" conditions was changed in error. As of the next build, the behavior is as follows: group actions may have empty constraints (no conditions), and since this is not explicitly false, the group will be allowed to run; while actions may not have empty constraints (and this will be enforced by the UI/editor going forward), and if a legacy while action is encountered with no conditions, it will not execute (safe behavior). A disabled group or while action will not run.
@toggledbits fair enough. I’ve analyzed more than 100 rules and I fixed a bunch of them manually. I’ll update my second system with next build.
Thanks!
-
@toggledbits so, build 26120 has now a strange side effect: when I try to add a comment to an empty constraint list, the infamous "fix erros before saving" banner appears and I cannot make it to go away, no matter what constraints I add to the group. Thanks.
-
Ugh. So sorry. Working on it now.
-
OK. 26120 rebuilt with a UI fix and pushed. Update your container and let me know how it goes.
-
@toggledbits all good now. no need to apologize, thanks for your hard work!
-
@toggledbits maybe it's related, but right now I have a similar problem.
Given these groups:
in this case, all are called.
Forum extract - Party Mode false but both branches executed Source: .vs/.tmp/logs/reactor.log Date: 2026-05-05 === A) Sunset flow where both Party Mode OFF and Party Mode ON run === [latest-26120]2026-05-05T18:16:00.192Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation (rule-kwulsxqu:S-159bd6va) [latest-26120]2026-05-05T18:16:00.206Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: OFF (rule-kwulsxqu:S-sjf1np7) [latest-26120]2026-05-05T18:16:00.207Z <Engine:INFO> Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: OFF all actions completed. [latest-26120]2026-05-05T18:16:00.207Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-Sunset" (re-kwulrhc7) [latest-26120]2026-05-05T18:16:00.243Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) [latest-26120]2026-05-05T18:16:00.244Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>89-2 with { } by reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) step 2 [latest-26120]2026-05-05T18:16:00.248Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON (rule-kwulsxqu:S-je98j75) [latest-26120]2026-05-05T18:16:00.249Z <Engine:NOTICE> Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON delaying until 1778004965249<5/5/2026, 8:16:05 PM> === B) Party Mode ON continuation triggers PartyMode and On-All scenes === [latest-26120]2026-05-05T18:16:05.250Z <Engine:INFO> Resuming reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON (rule-kwulsxqu:S-je98j75) from step 2 [latest-26120]2026-05-05T18:16:05.251Z <Engine:INFO> Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON all actions completed. [latest-26120]2026-05-05T18:16:05.251Z <Engine:INFO> Enqueueing "Lights-Outdoor-On-PartyMode<SET>" (rule-kwulj21d:S) [latest-26120]2026-05-05T18:16:05.271Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-PartyMode<SET> (rule-kwulj21d:S) [latest-26120]2026-05-05T18:16:05.271Z <Engine:INFO> Lights-Outdoor-On-PartyMode<SET> all actions completed. [latest-26120]2026-05-05T18:16:05.288Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-All" (re-kwueqcud) [latest-26120]2026-05-05T18:16:05.303Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-All (re-kwueqcud) [latest-26120]2026-05-05T18:16:05.304Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>169-1 with { } by reaction G-Lights-Outdoor-On-All (re-kwueqcud) step 2 === C) Same Sunset rule run also enters Vacation branch === [latest-26120]2026-05-05T18:16:05.343Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/Vacation (rule-kwulsxqu:S-159bdlwb) [latest-26120]2026-05-05T18:16:05.343Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>70-1 with { } by reaction Lights-Outdoor-On-Sunset<SET>/Vacation (rule-kwulsxqu:S-159bdlwb) step 1 === D) Later retrigger (18:19) of G-Lights-Outdoor-On-Sunset === [latest-26120]2026-05-05T18:19:27.156Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-Sunset" (re-kwulrhc7) [latest-26120]2026-05-05T18:19:27.160Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) [latest-26120]2026-05-05T18:19:27.161Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>89-2 with { } by reaction G-Lights-Outdoor-On-Sunset (re-kwulrhc7) step 2 [latest-26120]2026-05-05T18:19:27.597Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset/Green Mode (re-kwulrhc7-vxmf6qa) [latest-26120]2026-05-05T18:19:27.598Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>89-1 with { } by reaction G-Lights-Outdoor-On-Sunset/Green Mode (re-kwulrhc7-vxmf6qa) step 1 [latest-26120]2026-05-05T18:19:28.007Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>70-1 with { } by reaction G-Lights-Outdoor-On-Sunset/Green Mode (re-kwulrhc7-vxmf6qa) step 2 [latest-26120]2026-05-05T18:19:28.104Z <Engine:NOTICE> Starting reaction G-Lights-Outdoor-On-Sunset/Terrazzo (re-kwulrhc7-v80fyx6) [latest-26120]2026-05-05T18:19:28.105Z <Engine:INFO> Engine#1 perform power_switch.on on Switch#zwavejs>85-1 with { } by reaction G-Lights-Outdoor-On-Sunset/Terrazzo (re-kwulrhc7-v80fyx6) step 1 === E) MQTT scene-related reevaluations nearby (possible retrigger context) === [latest-26120]2026-05-05T18:19:28.174Z <Rule:INFO> Rule#rule-l20ceesq re-evaluating local variable close for dependency notification from GlobalExpression#scenefrommqtt [latest-26120]2026-05-05T18:19:28.175Z <Rule:INFO> Rule#rule-l3jpxetn re-evaluating local variable allup for dependency notification from GlobalExpression#scenefrommqtt [latest-26120]2026-05-05T18:19:28.270Z <Rule:INFO> Tasks-MQTT-ResetScene (rule-l2vqcz3z in System Tasks) starting rule state evaluation; because predicate-state-changed Predicate#rule-l2vqcz3z/trig [latest-26120]2026-05-05T18:19:28.271Z <Rule:INFO> Tasks-MQTT-ResetScene (rule-l2vqcz3z in System Tasks) evaluated; rule state transition from RESET to 'SET'this rule group is inside another rule group.
-
Build 26127 just posted has a small change that hit the issue responsible for the misbehavior. If not, there's additional logging that may help point me in the right direction.
-
@toggledbits unfortunately, this is still occurring with the new build. here's the log:
Reactor Support Report - Outdoor Lights Sunset Logic
1) Dev instrumentation context before event
[latest-26127]2026-05-07T18:06:07.950Z <Engine:INFO> Engine#1 performing startup eval of global partymode [latest-26127]2026-05-07T18:07:09.232Z <Rule:NOTICE> Lights-Outdoor-On-Sunset (rule-kwulsxqu in Lights-Outdoor) configuration changed; reloading [latest-26127]2026-05-07T18:07:09.232Z <Engine:INFO> Engine#1 rule Rule#rule-kwulsxqu changed; reloading and restarting it2) Sunset rule starts and enters No vacation
[latest-26127]2026-05-07T18:07:37.303Z <Engine:INFO> Enqueueing "Lights-Outdoor-On-Sunset<SET>" (rule-kwulsxqu:S) [latest-26127]2026-05-07T18:07:37.307Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET> (rule-kwulsxqu:S) [latest-26127]2026-05-07T18:07:37.310Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints No vacation (rule-kwulsxqu:S-159bdlwb-cons) [latest-26127]2026-05-07T18:07:37.319Z <Rule:INFO> Rule#rule-kwulsxqu reaction group No vacation (rule-kwulsxqu:S-159bdlwb-cons) constraints result=true3) Party Mode OFF evaluated true and executed
[latest-26127]2026-05-07T18:07:37.334Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints Party Mode: OFF (rule-kwulsxqu:S-sjf1np7-cons) [latest-26127]2026-05-07T18:07:37.337Z <Rule:INFO> Rule#rule-kwulsxqu reaction group Party Mode: OFF (rule-kwulsxqu:S-sjf1np7-cons) constraints result=true [latest-26127]2026-05-07T18:07:37.353Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: OFF (rule-kwulsxqu:S-sjf1np7)4) Party Mode ON also evaluated true in same flow
[latest-26127]2026-05-07T18:08:17.332Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints Party Mode: ON (rule-kwulsxqu:S-sjf1np7-cons) [latest-26127]2026-05-07T18:08:17.334Z <Rule:INFO> Rule#rule-kwulsxqu reaction group Party Mode: ON (rule-kwulsxqu:S-sjf1np7-cons) constraints result=true [latest-26127]2026-05-07T18:08:17.358Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/No vacation/Party Mode: ON (rule-kwulsxqu:S-je98j75)5) Follow-up party path triggers On-All scene
[latest-26127]2026-05-07T18:08:22.377Z <Engine:INFO> Enqueueing "Lights-Outdoor-On-PartyMode<SET>" (rule-kwulj21d:S) [latest-26127]2026-05-07T18:08:22.508Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-PartyMode<SET> (rule-kwulj21d:S) [latest-26127]2026-05-07T18:08:22.525Z <Engine:INFO> Enqueueing "G-Lights-Outdoor-On-All" (re-kwueqcud)6) Same top-level run also executes Vacation branch
[latest-26127]2026-05-07T18:08:22.585Z <Rule:INFO> Rule#rule-kwulsxqu evaluating reaction group constraints Vacation (rule-kwulsxqu:S-159bdlwb-cons) [latest-26127]2026-05-07T18:08:22.586Z <Rule:INFO> Rule#rule-kwulsxqu reaction group Vacation (rule-kwulsxqu:S-159bdlwb-cons) constraints result=true [latest-26127]2026-05-07T18:08:22.603Z <Engine:NOTICE> Starting reaction Lights-Outdoor-On-Sunset<SET>/Vacation (rule-kwulsxqu:S-159bdlwb)Dev Instrumentation Lines (Most Relevant)
These are the strongest lines showing the engine handling multiple conflicting groups as
true:[latest-26127]2026-05-07T18:07:37.320Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S handling group No vacation (rule-kwulsxqu:S-159bd6va) constraints result state true [latest-26127]2026-05-07T18:07:37.339Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S-159bd6va handling group Party Mode: OFF (rule-kwulsxqu:S-sjf1np7) constraints result state true [latest-26127]2026-05-07T18:08:17.334Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S-159bd6va handling group Party Mode: ON (rule-kwulsxqu:S-je98j75) constraints result state true [latest-26127]2026-05-07T18:08:22.587Z <Engine:INFO> Engine#1 reaction rule-kwulsxqu:S handling group Vacation (rule-kwulsxqu:S-159bdlwb) constraints result state trueAdditional Context
[latest-26127]2026-05-07T18:08:22.553Z <Engine:INFO> Engine#1 perform x_mqtt.publish ... topic "dbdomoticz/cmd/sceniclightsprogram" ... by reaction Lights-Outdoor-On-Sunset<SET>/No vacation [latest-26127]2026-05-07T18:08:22.372Z <Rule:INFO> Rule#rule-l20ceesq re-evaluating local variable close for dependency notification from GlobalExpression#scenefrommqtt [latest-26127]2026-05-07T18:08:22.374Z <Rule:INFO> Rule#rule-l3jpxetn re-evaluating local variable allup for dependency notification from GlobalExpression#scenefrommqtt -
OK. Please turn on log level 5 for that rule only. Run the rule to show the issue, and upload the entire Rule log file as well as reactor.log, the rule storage files (dval and json). Link for upload in your DMs
