Global Moderators group | Smart Home

toggledbits

Reactor build 26174

IF YOU ARE UPGRADING FROM A REACTOR BUILD EARLIER THAN 26116, PLEASE READ THE RELEASE NOTES FOR THAT BUILD. THERE WERE IMPORTANT CHANGES MADE ON THAT BUILD THAT MAY AFFECT HOW YOU BACK UP AND RESTORE REACTOR DATA.

NOTE TO DEVELOPERS: An upcoming build of Reactor will be published after code base conversion to ES modules. Current Reactor core modules are CommonJS (CJS). Many dependent packages are only getting new features in their ESM versions (i.e. the world is moving to ESMs), so Reactor must follow. Instructions for converting your Reactor Controller and Plugin subclasses are published in the Building Controllers page of the Reactor documentation (under Developer Info). If you send me a DM in this community, I can send you an early release of ESM Reactor for your development and testing. This 26174 build is still CJS-based, so your conversion applies only to that future Reactor release and beyond.

Entities list: fix a bug in entity filtering where a group filter would be ignored when an entity's name matched the name filter (both should be enforced).
Hubitat: Fixed a problem where a scene controller button would report tapped at every Reactor startup.
HTTP API: A new endpoint /api/v1/notify has been added so that external applications can use Reactor's configured notifiers to send messages. docs
VirtualEntityController: New ping-driven binary sensor reflects the (ICMP) reachability of a target network host. see docs
VirtualEntityController: Virtual entities may now be added to system room/location groups by including room: <string> in the virtual entity configuration.
HassController: Bless HA to 2026.6.4

toggledbits

If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027.

Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date.

If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.

toggledbits

@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.

toggledbits

Did you read the log entries? Pretty strong starting point there...

The logs are showing that your logging.yaml has an unrecoverable error. First, check to make sure you have only spaces, no tabs, for indenting.

If that's not it, indent the - type: file line two spaces, as well as the keep, level, and recycle lines that follow it.

toggledbits

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

Reactor build 26150

If you are upgrading to this build from 26011 or earlier, please read the cautions for build 26116!

A new Router notification method is now available. This method allows a single notification action to send a message to multiple notification targets. Configurable routes allow the selection and filtering of messages for different destinations. See docs
In support of the new Router notification method, configured Notifier profiles other than default are considered children of default. If a configuration value is not specified in such a profile, the value will be inherited from the default profile. This allows, for example, the default profile for SMTP to contain the host and authentication information, while additional profiles may contain only different recipient addresses — the additional profiles will use the default profile's host/auth info to connect to the same mail server, without the need to repeat that information in each profile. If an additional profile needs to connect to a different mail server, it may specify its own host and authentication parameters as before.
DynamicGroupController: improve response to changes in groups using filter_expression in configuration;
Expressions: fix an error in the runReaction() function that may cause it to crash on an attempted dereference through undefined.
Make the system more resilient to startup failures caused by hard errors in configuration files. When a (syntactically) valid configuration file is successfully loaded, it is copied to a last-known-good shadow file in the config directory. If the YAML configuration is later edited and contains errors that would prevent it being loaded, Reactor will load the last-known-good configuration, log the error, and display an alert in the Current Alerts widget on the Status page. The alert will clear itself when the file is fixed and later successfully loaded. To be clear, "valid" in this context means parseable (syntactically correct YAML). It does not mean that the keys and values given in the configuration will do what you expect/want or contain values or structures that Reactor can't recognize.
Fix a compatibility issue with node version 18. This version of node is only supported in the armv7l docker image (for 32-bit Raspberry Pis).
A new backup script backup_reactor_gfs.sh has been added to the tools directory; this script uses the grandfather-father-son backup strategy. If run daily, it will keep 30 daily backups, monthly backups (i.e. the first daily backup of each month), and quarterly backups (i.e. the first monthly backup of each quarter). Command line options suppress the backups of the logs directory and/or the transient/temporary state data for smaller backup size.

CatmanV2

Today marks another milestone in my Home Automation journey.

After tripping the main breaker once, and shedding more blood than is normally recommended, the underfloor heating (which was the last Z-wave device on my system) has been replaced with a Zigbee one.

Edited reactor.conf
Disabled z-way-server
Disabled Openluup

Z-wave is no more....

C

toggledbits

I'll see what can be done later, but this comes from a package I use, not code of my own creation. Despite the bug discovered, if I abandon the external package, I lose years of testing against myriad servers in the wild, so it's a potentially costly trade-off that makes a lot of future work (and frustration, potentially).

toggledbits

Reactor build 26143

If you are upgrading to this build from 26011 or earlier, please read the cautions for build 26116!

Reaction Editor: fix an issue where non-group actions could not be cloned.
Docker images: add ping command to underlying minimal OS packages.
HTTP Request Action: a bug in an underlying package dependency caused digest authentication to ignore a server's suggested/supported digest algorithm. A workaround has been put in place and tested successfully against servers requiring SHA-256 and SHA-512-256, in addition to the now disfavored MD5.
HassController: Bless HA to 2026.5.4