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.
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted.
reactor.yaml:
baseurl: "http://192.168.1.12:8111"
proxy_baseurl: "https://external.com:30000"
trusted_proxy: "192.168.1.12"
Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8
users.yaml:
- url: "/api/v1/log"
method: "GET"
source_ip: 172.18.0.0/24
allow: true
Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario:
I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices.
In EchoSpeaks I could create groups. Sweet.
In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?"
Is this an effective scenario that Dynamic Group Controller can be used for?
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load
https://<public ip>:30000/reactor/en-US/
At the same time logging page loads normally
https://<public ip>:30000/api/v1/log
I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case).
Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
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!
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.
[Solved] build 26150 - engine not starting
Multi-System Reactor
8
Posts
2
Posters
864
Views
2
Watching
-
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline.
The log looks like it ends with 26143.
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing logI can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
-
Huh. I'm running the 26150 amd64 container with no issue... sure would be nice to have logs. If you go for them, startup is where it's at, and you may need to look at the container syslog if an error is being thrown before the logger is up and running. Some early message get written to the console, and that usually ends up directed to the system logs.
-
Huh. I'm running the 26150 amd64 container with no issue... sure would be nice to have logs. If you go for them, startup is where it's at, and you may need to look at the container syslog if an error is being thrown before the logger is up and running. Some early message get written to the console, and that usually ends up directed to the system logs.
@toggledbits if I have time here I'll try to pull the image again and capture logging.
-
Huh. I'm running the 26150 amd64 container with no issue... sure would be nice to have logs. If you go for them, startup is where it's at, and you may need to look at the container syslog if an error is being thrown before the logger is up and running. Some early message get written to the console, and that usually ends up directed to the system logs.
@toggledbits Repulled, same thing happened: unreachable.
2026-05-31T19:33:04.533976919Z at wrapModuleLoad (node:internal/modules/cjs/loader:255:19) 2026-05-31T19:33:04.533978974Z at Module.require (node:internal/modules/cjs/loader:1600:12) 2026-05-31T19:33:04.533980967Z at require (node:internal/modules/helpers:153:16) 2026-05-31T19:33:04.533983008Z 2026-05-31T19:33:04.533984917Z Node.js v24.16.0 2026-05-31T19:33:56.035775922Z Reactor latest-26150-7b86db04 app 26150 configuration from /var/reactor/config 2026-05-31T19:33:56.053129729Z NODE_PATH /opt/reactor:/opt/reactor/node_modules 2026-05-31T19:33:56.054371749Z Failed to parse /var/reactor/config/logging.yaml YAMLException: bad indentation of a mapping entry in "/var/reactor/config/logging.yaml" (56:34) 2026-05-31T19:33:56.054391711Z 2026-05-31T19:33:56.054396228Z 53 | - type: file # filename is derived from rule ID 2026-05-31T19:33:56.054399741Z 54 | keep: 2 2026-05-31T19:33:56.054402822Z 55 | level: 999 2026-05-31T19:33:56.054405736Z 56 | recycle: true# recycle: true 2026-05-31T19:33:56.054408789Z ---------------------------------------^ 2026-05-31T19:33:56.054456413Z At about line 55; near 2026-05-31T19:33:56.054461049Z > level: 5 2026-05-31T19:33:56.054464372Z > streams: 2026-05-31T19:33:56.054509289Z > - type: file # filename is derived from rule ID 2026-05-31T19:33:56.054513314Z > keep: 2 2026-05-31T19:33:56.054515586Z > level: 999 2026-05-31T19:33:56.054517599Z > recycle: true# recycle: true 2026-05-31T19:33:56.054478049Z Use https://yamlvalidator.com/ and correct all indicated errors. 2026-05-31T19:33:56.054522741Z failed to read configuration file /var/reactor/config/logging.yaml; attemping last-known-good 2026-05-31T19:33:56.054619109Z unable to load configuration data for logging 2026-05-31T19:33:56.056778406Z /opt/reactor/server/lib/Logger.js:429 2026-05-31T19:33:56.056793267Z const _0x98a8e2 = a22_0xf250f4, _0x36af7e = log_config['getConfig'](_0x98a8e2(0x14d), _0x98a8e2(0xfd), {}); 2026-05-31T19:33:56.056795940Z ^ 2026-05-31T19:33:56.056798247Z 2026-05-31T19:33:56.056800114Z TypeError: Cannot read properties of undefined (reading 'getConfig') 2026-05-31T19:33:56.056801991Z at Logger.getLogger (/opt/reactor/server/lib/Logger.js:429:63) 2026-05-31T19:33:56.056803906Z at Logger.getDefaultLogger (/opt/reactor/server/lib/Logger.js:460:40) 2026-05-31T19:33:56.056805752Z at Object.<anonymous> (/opt/reactor/server/lib/Logger.js:761:619) 2026-05-31T19:33:56.056807789Z at Module._compile (node:internal/modules/cjs/loader:1854:14) 2026-05-31T19:33:56.056809659Z at Object..js (node:internal/modules/cjs/loader:1985:10) 2026-05-31T19:33:56.056811482Z at Module.load (node:internal/modules/cjs/loader:1577:32) 2026-05-31T19:33:56.056813567Z at Module._load (node:internal/modules/cjs/loader:1379:12) 2026-05-31T19:33:56.056815388Z at wrapModuleLoad (node:internal/modules/cjs/loader:255:19) 2026-05-31T19:33:56.056817221Z at Module.require (node:internal/modules/cjs/loader:1600:12) 2026-05-31T19:33:56.056819018Z at require (node:internal/modules/helpers:153:16) 2026-05-31T19:33:56.056820871Z 2026-05-31T19:33:56.056822616Z Node.js v24.16.0This is what the container logs show.
-
Did you read the log entries? Pretty strong starting point there...
The logs are showing that your
logging.yamlhas an unrecoverable error. First, check to make sure you have only spaces, no tabs, for indenting.If that's not it, indent the
- type: fileline two spaces, as well as thekeep,level, andrecyclelines that follow it. -
Did you read the log entries? Pretty strong starting point there...
The logs are showing that your
logging.yamlhas an unrecoverable error. First, check to make sure you have only spaces, no tabs, for indenting.If that's not it, indent the
- type: fileline two spaces, as well as thekeep,level, andrecyclelines that follow it.@toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.
That being said, I completely removed the extra rule logging I had added and restarted. Brought down the new image and everything is fine.
So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.
*Hubitat C-7 2.5.2.139
*Proxmox VE v8, Beelink MiniPC 12GBs, SSD*HAOS
Core 2026.10.4
w/ HA Connect ZWA-2 & ZBT-2
FW: v1.1
SDK: v7.23.1*Prod MSR in docker/portainer
MSR: latest-26298-fbb75fb8
MQTTController: 25139
ZWave Controller: 25139 -
@toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.
That being said, I completely removed the extra rule logging I had added and restarted. Brought down the new image and everything is fine.
So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.
@gwp1 said in [Solved] build 26150 - engine not starting:
@toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.
Upload it to me, I'd like to take a look.
@gwp1 said in [Solved] build 26150 - engine not starting:
So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.
No idea. But, having once gotten a clean startup, it now has a last known good version of that config file, so whatever it's not happy with won't prevent startup in future.