I have a couple of rules that has group reactions with empty conditions. I notice, in particular on one that's called every 5 secs, that it was not working. I added an empty comment as condition and it started working again.
I don't know if saving was enough to "reset" it, but I'm reporting anyway. No errors in the logs, but the MQTT message was not published, so I had an easy path to check the rule.
I have others like these, but not easy to test. @toggledbits maybe some stuck status data? (I restarted a couple of times after the last update). 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.
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.
In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.
Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.
I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.
A few other things to know:
If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.
This thread is open for any questions or concerns.
Hi,
I'm on Docker/NAs (latest-26011-c621bbc7) with Zwave js ui (last version).
I have set the 'Location' for each device in the Z-Wave JS UI dashboard, I cannot find this information among the Entity Attributes in the Reactor. I tried and the result is an empty array []. It seems the 'Location' metadata from Z-Wave JS is not being mapped to a standard attribute in Reactor. Location is equale to Rooms for me. When comparing this to the Vera or Ezlo Controller, Reactor automatically creates Room Icons also in the Reactor Dashboard and places the various devices under those room categories.
This is a very convenient way to keep the dashboard organized and quickly find lights to turn off with a click (especially when something isn't switched off as expected for me:) ).
Is there a way to map the Z-Wave JS UI 'Location' attribute and a dashboard organization, just like it does with Vera/Ezlo?
Thanks in advance for all the great tips you've shared
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules.
I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds).
Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off?
With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches.
Thanks
Reactor (Multi-hub) latest-26011-c621bbc7
VirtualEntityController v25356
Synology Docker
I've had similar problems before, but now this issue has resurfaced. Using build 26011 on Docker.
As I copied one old rule as a "template" for a similar new rule, where I have multiple conditions using changes operator (from any to any, and with delay reset of 900), these conditions do not detect change in attributes. Even if I manually reset the rule, reset delay timers do not restart.
If I do a new rule from scratch, and do not copy/import anything old, the same conditions work properly. Also, if I modify copied rule's conditions (put a random number to "from" & "to" fields), then save, and after that remove those modifications, rule begins to function normally. Just editing e.g. delay reset value does not do any good in this context.
@toggledbits, I can DM logs & related rule files to you, if you just send me instructions.
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC.
Sounds like Home Assistant OS is linux based using Docker for HA etc.
Would I also be able to install things like MSR as well on their OS ? On the same box?
Thanks.
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration
This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something?
Cheers
C
Using build 25328 and having the following users.yaml configuration:
users:
# This section defines your valid users.
admin: *******
groups:
# This section defines your user groups. Optionally, it defines application
# and API access restrictions (ACLs) for the group. Users may belong to
# more than one group. Again, no required or special groups here.
admin_group:
users:
- admin
applications: true # special form allows access to ALL applications
guests:
users: "*"
applications:
- dashboard
api_acls:
# This ACL allows users in the "admin" group to access the API
- url: "/api"
group: admin_group
allow: true
log: true
# This ACL allows anyone/thing to access the /api/v1/alive API endpoint
- url: "/api/v1/alive"
allow: true
session:
timeout: 7200 # (seconds)
rolling: true # activity extends timeout when true
# If log_acls is true, the selected ACL for every API access is logged.
log_acls: true
# If debug_acls is true, even more information about ACL selection is logged.
debug_acls: true
My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Reactor build 26116: empty group reaction
Multi-System Reactor
15
Posts
3
Posters
319
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.0.126
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HAOS
Core 2026.4.4
w/ HA Connect ZWA-2
FW: v1.1
SDK: v7.23.1*Prod MSR in docker/portainer
MSR: latest-26120-d2e50474
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.0.126
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HAOS
Core 2026.4.4
w/ HA Connect ZWA-2
FW: v1.1
SDK: v7.23.1*Prod MSR in docker/portainer
MSR: latest-26120-d2e50474
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.
