Reactor (Multi-Hub/System, aka MSR) Latest Builds

WARNING: This directory contains development builds that may not be fully verified/validated.

DOCKER USERS ON RASPBIAN BUSTER (ONLY) FOR RPi: Reactor docker images since 22021 require that you install an OS patch to run the Reactor image in a container. See the install instructions for the steps to install it.

BARE-METAL USERS: It is recommended that you update package dependencies when installing all Reactor updates. After unpacking the Reactor archive, remove any existing package-lock.json file from your Reactor install directory, and then run npm i --no-save --no-package-lock --omit dev to update package dependencies.

ALL USERS: A hard refresh of your browser is necessary after upgrading (always).

24057

NOTE (BARE-METAL ONLY): If you are upgrading to this build from a build earlier than 24052, please update your package dependencies. After unpacking the Reactor archive, remove any existing package-lock.json file from your Reactor install directory, and then run npm i --no-save --no-package-lock --omit dev to update package dependencies.

24052

BREAKING CHANGE: The valve capability's state attribute value is now boolean, to match similar system capabilities (was previously/erroneously string). If you are using an entity with the valve capability in conditions or actions, make sure the type for the current or target state is boolean now.

23344

23338

DEPRECATION WARNING (bare-metal installs only): all nodejs versions earlier than 18 are now end-of-life; these versions will not be supported for Reactor after 1-Mar-2024. You should upgrade nodejs as soon as possible. The minimum supported version is now 18.18, but for longevity, upgrading to the current LTS version is recommended. Users of Reactor running in docker containers are not affected, as the image always embeds a supported LTS version of nodejs (that is, no action is required for docker users).

23302

23242

23218

23196

NOTICE: As announced in the release note for the previous build (23171), Home Assistant versions earlier than 2022.5.3 are no longer supported.

23171

DEPRECATION NOTICE: Support for versions of Home Assistant prior to 2022.5.3 will be removed on the next build. These older versions may continue to operate successfully with HassController going forward, but I will not address/fix issues for them.

23139 (Silent Update)

Note: This is an interim release to get a couple of fixes out before I go on vacation; I haven't completely tested this version. Only upgrade to this release if you are having one of the issues (PRs) noted below and need the fix.

23114

23078

23063

23049

23028

23010

22349

NOTE: If you get missing entity errors from your rules when you first start this version, don't panic. Just wait a few seconds and then restart Reactor; it should then start clean.

IMPORTANT: The bare-metal distributions no longer include package dependencies pre-installed. It is therefore critical that you install/update dependencies every time you upgrade by running npm run deps in the Reactor install directory (for Linux users; Windows users please refer to the installation documentation. This advisory does not apply to docker-based installs — Reactor docker images always include package dependencies pre-installed.

22343

This was a silent release to fix one specific issue in EzloController. The other items came along for the ride.

22337

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22328

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22310

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22308

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22305

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22302

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22293

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22291

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22274

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22266

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22264

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22258

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22257

ALL USERS -- IMPORTANT: If you are upgrading from any version earlier than 22256, please read the advisories and prerequisites for that build, below.

22256

ALL USERS -- IMPORTANT: As a result of entity storage changes in this build, existing entity storage (cache) is invalidated and rebuilt when this build is first run. That will cause all entities to be reported as newly-discovered, even though they were known before. However, this should be minimally disruptive to your logic, if at all. You may also safely ignore any warnings you see in the logs about "incompatible serialization data" on that first run; those are expected.

22252

22251

22248

22240

22233

BARE-METAL INSTALL USERS: When upgrading to this version, you must upgrade package dependencies after unpacking the archive file (delete any existing package-lock.json file and then run npm install --no-save --omit dev). The UI will not function properly if you fail to perform this upgrade.

22203

22179

22178

22168

REMINDER: As previously announced, all docker images are now named with the release branch and target architecture only. The latest branch docker image for all x86_64/amd64 systems is now named latest-amd64 (was previously latest-generic-amd64). The latest branch image for armv7l, which includes Raspberry Pi systems on Raspbian Buster, is now named latest-armv7l (was previously latest-raspbian-armv7l). Please adjust your upgrade procedures and, if used, docker-compose or Portainer configurations accordingly.

22149

22142

22140

22136

NEW DOCKER IMAGE: A new docker image, or more correctly, architecture, has been added to the builds: aarch64. This is for 64-bit Arm (v8) systems, including the Raspberry Pi 4 on Raspbian Bullseye, and the NVIDIA Jetson Nano (2GB and 4GB versions).

22123

22118

Note: this release includes changes to package dependencies. Bare-metal users please run npm install --no-save --omit dev to resolve.

IMPORTANT: This update includes some significant enhancements for entity tracking. On your first startup after upgrading, you may get a lot of alerts about new devices being discovered (i.e. existing devices are being noted as new) as the enhanced tracking learns what is "normal" for your system. This is expected behavior for this version on its first startup. Just clear the alerts and go on about your day. After that, you should only receive notices when new devices are added to a hub, or new hubs are configured in Reactor.

22080

22069

22067

22053

BREAKING CHANGE/FIX This version contains what may be a breaking change for some users. Some actions offer lists of predefined values (e.g. media_source.set offers hdmi1, hdmi2, etc.). A bug in the Reaction editor was causing a numeric index value to be stored instead of the string value (i.e. it would store 0 rather than hdmi1). The bug is now fixed, but any action like this previously created/edited may have had an invalid value stored in the rule or reaction to which it belongs, and this cannot be reliably automatically fixed, it generally requires user review. Most likely, these actions didn't work well for you anyway, because the erroneous numeric value would likely have given invalid results/behaviors/errors when attempted, and we just haven't noticed until now (they are fairly rarely-used actions, on the whole). The specific actions affected are: av_repeat.set_repeat, muting.set, media_source.set, hvac_control.set_mode, hvac_blower_unit.set_mode, hvac_blower_swing.set_mode, hvac_humidifier.set_moded, hvac_dehumidifier.set_mode, zwave_device.set_config. Hopefully this list helps you narrow down what, if any, of your rules/reactions may be affected. Just take the rule/reaction into the editor, fix the new correct value and save.

22049

**NOTE: Bare-metal users should run npm i --no-save --omit-dev to update packages for this release.

22044

22028

22025

22023

22022

22021

22010

22004

22001

21365

21362

21360

21356

21351

Users are advised only to upgrade to this release if they are affected by an issue related to the changes below; specifically, if you are not a user of Hubitat and you do not use constraints in rules or reactions, there is no need to upgrade to this release.

21349

21342

21338

21337

21336

If you have been with Reactor since before 21075 (March 15, 2021), your logging.yaml configuration may have a relative path in the name keys of the default streams (e.g. ./logs/reactor.log). These must be changed to just a simple filename (e.g. reactor.log). Reactor has been warning you at startup (in the log file) about this since 21075, if it applies to you (i.e. your logging config uses a relative path), but if you haven't seen it, you may not have changed it. The time to check it/change it is now, because the next version of Reactor that is released will not allow pathnames (relative or absolute) in this key, and will not run if it finds one.

21332

21331

21321

21313

21307

21306

Note: this release includes changes to package dependencies. Bare-metal users please run npm update --no-save to resolve.

21297

21294

21292

21286

21285 (silent release)

21281

21277

21275

NOTICE: This revision incorporates a breaking change to the recently-introduced matchEntities(). See below.

21270

21267

21258

21256

21243

21239

21237

21236

21228

21221

21219

21218

21213

21206

21203

21202

21201

21200