Index of /download/latest

 Name                                        Last modified      Size  Description
 Parent Directory                                                 -   
 README.html                                 2024-12-08 11:30  111K  
 reactor-latest-24343-e5d3cf59.zip.sha256    2024-12-08 11:19  100   
 reactor-latest-24343-e5d3cf59.zip           2024-12-08 11:19  4.1M  
 reactor-latest-24343-e5d3cf59.tar.gz.sha256 2024-12-08 11:19  103   
 version.json                                2024-12-08 11:19   91   
 reactor-latest-24343-e5d3cf59.tar.gz        2024-12-08 11:19  3.9M  
 reactor-latest-24302-751a06b6.zip.sha256    2024-10-29 07:50  100   
 reactor-latest-24302-751a06b6.zip           2024-10-29 07:50  4.1M  
 reactor-latest-24302-751a06b6.tar.gz.sha256 2024-10-29 07:50  103   
 reactor-latest-24302-751a06b6.tar.gz        2024-10-29 07:50  3.9M  
 reactor-latest-24296-2cc3e72c.zip.sha256    2024-10-22 13:16  100   
 reactor-latest-24296-2cc3e72c.zip           2024-10-22 13:16  4.1M  
 reactor-latest-24296-2cc3e72c.tar.gz.sha256 2024-10-22 13:16  103   
 reactor-latest-24296-2cc3e72c.tar.gz        2024-10-22 13:16  3.9M  
 reactor-latest-24257-59ba2a36.zip.sha256    2024-09-13 13:30  100   
 reactor-latest-24257-59ba2a36.zip           2024-09-13 13:30  4.0M  
 reactor-latest-24257-59ba2a36.tar.gz.sha256 2024-09-13 13:30  103   
 reactor-latest-24257-59ba2a36.tar.gz        2024-09-13 13:30  3.8M  
 reactor-latest-24057-e9add9f5.zip.sha256    2024-02-26 10:46  100   
 reactor-latest-24057-e9add9f5.zip           2024-02-26 10:46  3.5M  
 reactor-latest-24057-e9add9f5.tar.gz.sha256 2024-02-26 10:46  103   
 reactor-latest-24057-e9add9f5.tar.gz        2024-02-26 10:46  3.3M

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

24343

NOTE: Notable UI Change: removing widgets on the Status tab now requires you to drag the widget (by its header) to the top navigation bar and release it there. Previously, moving a widget anywhere outside the content panel would remove it, but this was troublesome for small touch displays (too easy to remove items while scrolling).

PR 0000389: Improve mobile device compatibility. Although many aspects of the UI have been tweaked for better presentation on small displays, it will continue to be the case that editing of major system objects (Rules, Reactions, Expressions) is a high-interactivity task, and the design goals do not and will not include "mobile first" compatibility for that.
PR 0000387: Make VirtualEntityController operation of reactor_system.set_attribute action identical to (and in fact, just an alias for) x_virtualentity.set_attribute. On virtual entities, all attributes are de-facto writable.
PR 0000386: Fix an issue with HubitatController where it could attempt to set NaN on an attribute, generating a warning in the log.
The Reaction List has been modified to show a spinner while a Reaction is running, rather than holding a green highlight.
Fix an issue with the Reaction List not repainting correctly after editing a (global) reaction.
Additional hard-coded colors in some CSS styles have been removed in favor of CSS variables (Bootstrap- or Reactor-defined). This should help user making custom themes.
Improve the error message given when a script/expression attempts to set a global variable that is not writable (i.e. it's not expressionless).
The default action handlers for increasing/decreasing values in dimming, position, and volume capabilities has been updated to more consistently move in increments of the related step value. For example, when the current dimming level is 0.55 (55%), the dimming.up action with a step of 0.1 will move to 0.6 rather than 0.65 as previously implemented. Not all devices/Controllers use the default action handlers for these actions — if the Controller implements its own semantics, this change has no effect.
VirtualEntityController can now do HTTP requests in actions. This allows you to create a virtual entity that functions as an interface for a device that is HTTP-controllable without the need to write a custom Controller instance. See the docs for VirtualEntityController for updated section on actions.
HassController: Bless Hass to 2024.11.3

24302

UPGRADE NOTICE: If you are upgrading to this version from earlier than 24293, please see the notes and instructions for 24293 for additional actions you need to perform during upgrade.

You may supply a CSS (Cascading Style Sheet) containing customizations for Bootstrap 5.3 in a file called config/customstyles.css. This allows you to further adjust theme colors to your liking. For instructions on how to customize Bootstrap styles, refer to its documentation.
PR 0000383 (and 385): The changes operator was not allowing "pulse" output option. It is now allowed (whether terminal values are used or not).

24296

UPGRADE NOTICE: If you are upgrading to this version from earlier than 24293, please see the notes and instructions for 24293 for additional actions you need to perform during upgrade.

Fix a race condition when painting the Status tab when painting a widget that must traverse the ruleset index.
Make sure errors thrown by widgets show in the widget container, not by popping the exception dialog.
Fix activation of the Expressions tab so it paints every time (a guard for edit mode was too aggressive, because this tab is always in edit mode).
Fix a number of reported appearance issues, and some new ones.

24293

BARE-METAL USERS: UPDATE YOUR PACKAGES! You must run npm i --no-save --no-package-lock --omit dev after unpacking the Reactor distribution archive. Failure to do so will result in a non-functioning UI and many other issues.

POTENTIAL BREAKING CHANGE: The validity of characters in entity IDs is now enforced. Previously, only a warning was written to the log if the ID contained invalid characters; now, the entity will not be allowed to exist. If you use VirtualEntityController, MQTTController, or other Controllers where you can configurably create entities, the IDs you establish for those entities must now contain only valid characters, which are ASCII alphanumerics, dash (-), underscore (_), and the high ASCII ranges 192-214, 216-246, and 248-255 (which covers some letters with diacritics). Other characters, including Unicode characters outside this range, are not permitted.

POTENTIAL BREAKING CHANGE: The alert attributes have been moved off of the Reactor System (reactor_system>system) entity on to a separate Reactor System Alerts (reactor_system>alerts) entity. If you have Rules or Reactions that use alert data in conditions, you will need to point them to the new entity/attributes.

LOCALIZATION UPDATE: There are several new strings in the reference localization template (new version 24293). See the Github repository for the current reference version and change log.

Entity action implementations can now return values/results and store them directly to a local (Rule-based) or global variable for further processing. Note that HassController was previously (in build 24115) given this ability in a slightly different form, where the response was written to a single attribute from which it could be retrieved by other expressions. HassController will support both mechanisms for the foreseeable future, but transition to the new mechanism is recommended.
New Script Action action in Reactions allows you to run an expression/script in-line in a Reaction. This is intended to simplify handing of results from Entity Actions that return results.
Scripts/expressions may now make assignments to expression-less global and local (rule-based, when the script/expression is in a Rule) variables.
Fixed a bug in the changes operator where, if there were terminal values (values for changes from, to, or both), the output would pulse rather than "stick." The design intent was such that it should stick, because a change with terminal values is predictably persistent (i.e. a condition that watches for an alarm panel state change from disarmed to away will go true and should stay true as long as the alarm panel remains in away state). When there are no terminal values, a change is still signalled with a pulse (i.e. a change from any value to any other value produces a pulse, and is then ready to signal a change to yet another value).
Capabilities may now define user-writable attributes, and the user may set the value of such an attribute on an entity. The intent of this feature is to provide storage for user preference in actions (such as the amount to change the light level when performing dimming.up), but could have many other uses. To make an attribute user-writable, the developer must include writable: true in the attribute definition. Attributes derived from device data (like switch state or blind position; i.e. where a Controller instance controls the value) are not writable by the user and should not be made user-writable by developers. User-writable attribute values can be set using the new Set Attribute button in Entity list detail cards, or using the reactor_entity.set_attribute action.
New reactor_entity capability is extended to all entities, and contains actions to rename the entity and set its writable attributes.
Additional work to preserve the state of attributes across upgrades/changes to underlying capabilities and implementations. The new Controller methods refreshCapabilites() and refreshCapability() provide a mechanism for updating an Entity's stored capability data without losing the values of attributes and metadata that exist in both the old and new versions of a capability.
Logger now supports (via logging.yaml entry) the rotation of log files on specific intervals. The maxage: time configuration can be added, where time is an integer followed by secs, mins, hours, or days. These may be abbreviated to a single character (e.g. 1d or 4h). If the time is an integer only, the units are assumed to be days.
DynamicGroupController now supports an expanded form of group_actions configuration to more narrowly specify which actions are to be made available as group actions. See the Group Actions section of the documentation for DynamicGroupController.
UI now has a dark theme (long-awaited).
UI (Reaction Editor) for HTTP Request action now shows more clearly that when storing response to a variable, it must wait for the response to complete (i.e. when you choose a target variable, it automatically checks the "Wait for" checkbox in addition to disabling it). The semantics of this have been documented since inception, but the UI now reinforces the concept in its display.
UI (Entities List) detail cards for Entities now have a Perform dropdown to run actions, rather than a list of links. The selected action is performed immediately if it has no arguments; otherwise, the arguments are requested in a modal dialog as before. This should improve access to actions on entities from this area.
New expression functions from updated lexpjs: isvalue(), scale(), constrain(). See docs for Expressions.
PR 0000380: Resolve an issue with an optional argument in a HAss-specific service requiring a value in the action editor (service climate.set_temperature for example).
A (very) simple log file viewer/fetcher is now available at /api/v1/log. The optional file query parameter can be given to select which log file (by name); by default, reactor.log is displayed. This endpoint is protected when access control is enabled, so if you are using access control, you may need to modify an existing ACL or create a new one to enable access to it.
HassController: Bless Hass to 2024.10.3

24257

System Capabilities: the new tag system capability has been introduced to extend data and behavior for RFID tags and similar devices.
HassController: Implement tag_scanned event handling, which creates a new entity from the tag ID. This entity is updated whenever Hass reports that the tag is detected any scanning device. This automatic event handling does not preempt or prevent user-configurable event handling for different behavior, if desired.
HassController: Improve the initialization of event-driven entities so they are not cleared every time Reactor is restarted (they will be cleared only if a configuration change is detected).
HassController: The event processor now ensures that time_fired is included in the event data before handling. If not, Reactor will provide it. In addition, since Hass passes time_fired as a string, Reactor will parse the string to an Epoch time (seconds since midnight Jan 1, 1970 UTC) and provide it in time_fired_epoch, which can be used in user configuration for events.
HassController: Allow filtering of state attributes to reduce rule re-evaluation traffic for related entities. (see docs)
HassController: Bless Hass to 2024.9.1

24243

POTENTIAL BREAKING CHANGE: The conditions in a Reaction's repeat…while group are meant to be Constraints, not Triggers -- they are stateless, meaning that they are evaluated each time they are run, not when an underlying condition triggers them (such as a timer expiring on a sustained for option). This was always meant to be the case, but an error in the UI implementation permitted certain condition options applicable only to trigger conditions. This is now fixed, and any constraints containing condition options will have those options removed during later editing, and the options will not function (they haven't been working correctly anyway) until that time.

Shell Command action now supports expression substitution. This makes an already dangerous (security-wise) action even moreso, so it must be enabled explicitly by setting allow_shell_action_substitution: true in the engine configuration section of reactor.yaml. It is highly recommended that Shell Command actions only be used on systems that have HTTPS access and Access Control (user authentication) enabled, to reduce the possibility that the action could be a vector for attacking the host system and your network.
PR 0000378: VirtualEntityController: fix configuration collision between virtual entities affecting time-series aggregations.
PR 0000369: Add error attribute for ev_charger system capability documentation.
PR 0000349: Support custom sounds for Pushover notification.
PR 0000290: Display rule ID in rule editor (convenience).
HassController: Bless Hass to 2024.8.3

24212

PR 0000376: Search by name is now available on the Reactions list (similar to Entities list).
Attribute security_mode.state recognizes max value.
Action security_mode.set_mode now takes code argument (if not given, the default code in the Controller's configuration will be applied, if available).
Dashboard: support /dashboard/group/<group-canonical-id> path for direct display of a group.
PR 0000375: Fix a path where a global variable (expressionless) could have its value modified and not update variables that depend on it.
HassController: Bless Hass to 2024.7.3

24190

BREAKING CHANGE: Home Assistant versions prior to 2023.6 are no longer supported. Going forward, you may expect HassController to support Home Assistant releases made in the last 12 months. Older releases may continue to work, but will rececive a warning at startup, and may cause errors (that I will not troubleshoot or fix/work around). Special workarounds for pecularities of releases older than 24 months will be removed from the code (meaning versions of Home Assistant older than that will almost certainly have issues).

Access Control: setting the session timeout to 0 in users.yaml disables timed-based session expiration.
PR 0000374: Rolling refresh appears not to work (many UI operations don't cause enough activity to stimulate the refresh).
PR 0000371: Localization for login page submit button.
Conditions: Ignore excess whitespace in comma-separated list of values for "in" and "not in" condition operators.
Rule UI: Hovering over a condition's value in a rule detail card now shows info for current and previous value.
HassController: Bless Hass to 2024.7.0

24152

POTENTIAL BREAKING CHANGE: The port on which Reactor provides HTTP(S) service is now determined by the baseurl configuration value first. If no port is given there, the PORT environment variable is then queried; if that's not set, the default port is used (different for HTTP and HTTPS; see below). In previous versions, the PORT environment variable had the highest priority, but this is no longer the case. This will likely have no effect on most users, but if you're having trouble accessing the UI after upgrade, check your baseurl configuration first (if you don't have one or need an example, refer to the distribution version of reactor.yaml in dist-config. For users using Reactor via HTTPS (SSL/TLS encryption), I recommend using port 8554 in baseurl; regular HTTP (no encryption) remains on port 8111.

User Authentication and Access Control. See the Access Control documentation. This is feature request PR 0000351.
The default port for HTTPS-enabled Reactor is now 8554 (8111+443). If your system or docker configuration set the PORT environment variable before starting Reactor, whatever port that specifies will be used as before. See the How-To: HTTPS section of the documentation for information about configuring Reactor for HTTPS.
The port used for HTTP(S) service is now determined by the port specified in baseurl (in config/reactor.yaml) first; if no port is specified in baseurl, the PORT environment variable is used if set, and finally the Reactor default of 8111 (or 8554 if TLS is enabled).
If HTTPS (HTTP + SSL/TLS) is enabled and its configured port is other than 8111 (the standard HTTP (non-SSL/TLS) port for Reactor), an HTTP service on port 8111 will now be created to redirect requests from HTTP to HTTPS (no unencrypted service is provided other than redirection). This feature can be disabled by configuring redirect_http to false in the reactor section of config/reactor.yaml.
The allow_ips in the reactor section of config/reactor.yaml now allows CIDR address range specification (e.g. 10/8 or 192.168.0/24) for ranges of addresses.
Updated the documentation theme and its supporting plugins; improved the appearance of code snippets with syntax highlighting in most cases; add line highlighting in many code snippets to draw attention to certain elements or changes.
Dashboard: added new Thermostat type (supported by Level.updown layout) for capabilities hvac_heating_unit/hvac_cooling_unit. Evolving; further improvements coming.
VirtualEntityController: Support for time-series data collection and aggregation. See the docs).
VirtualEntityController: Preserve attribute values if possible across system updates that affect capability definitions or implementations.
DynamicGroupController: It is now possible to set the primary attribute of a dynamic group, and determine its value dynamically. Trivial example: add the binary_sensor.state attribute to a group to show true when any light in the group is on. Refer to the docs for DynamicGroupController.
The dist-config directory is now copied to the user data virtual path target when running in docker containers so that its contents are more easily accessible to docker users (no need to docker exec into the running container).
Rules: the logging level for most rule evaluation messages has been reduced to DEBUG0 (numeric level 5); rules will now log only startup/shutdown and rule state changes at INFO level. Per-object logging configuration can be used to enable more detailed logging for a specific rule when required.
Fixed an issue in the core related to deleting certain objects (a Global Reaction was reported, but could have been many object types).
Fixed an issue with local service of docs that caused a cross-site scriping error on some browsers (this is the "Initializing search…" bug).
Developer Tools: the util function deepCompare() now works with JavaScript Set, Map, Buffer, RegExp objects.
Developer Tools: documented util function hash() (it's been around a while, just not documented).
HassController: Bless Hass to 2024.5.5

24115

Entities UI: When a capability filter is selected, the value column header displays a selector allowing the user to display a value in the column other than the primary value for the filtered entities.
The extensions subdirectory ext may now be located under config, which makes its location uniform for bare-metal and docker users; this will eventually become the standard location. It is not necessary at this time to relocate your existing ext directory if you have one — either or both the old and new locations will work for the foreseeable future.
Improve the coordination of the Reactions and Rules displays when open and interacting on multiple displays (e.g. when you delete a reaction on one screen, it should disappear from the other(s)).
Fix a browser-side performance issue/delay with reconnection to a restarting Reactor service when the Status page is up and displaying the Recently Changed Entities widget. This also improves the memory consumption and performance of the widget generally.
Increase tolerance for damage to most storage objects, particularly those that only maintain state that can usually be safely rebuilt on the fly. For those that cannot, like rules and expressions, isolate a faulty file and ignore the object with an alert to the user. Preserve the broken file.
PR 0000367 Localization of the new strings in the rule state override menu and state display have been added.
PR 0000368 Fix missing localization string for Copy Attributes button in Entities list entity detail card.
Report detected time zone and offset in startup messages. Add time zone display to hover title on browser and host times in UI header.
New wifi_status system capability for WiFi-connected devices that can report connection status.
PR 0000369 Docs: Add documentation for ev_charger system capability.
HassController now supports responses from services that support them; whether required or optional, a response will be requested and stored in x_hass.last_response on the target Reactor entity. The data returned is not processed in any way; it is written as-received to the attribute. Tip: if possible, always make the service call from the target entity, not from the system entity.
HassController: Bless Hass to 2024.4.4

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.

PR 0000366: Fix an injection caused by the rule state override option added in 24052, which results in constraints on rules being handled incorrectly.

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.

Update support for many packages. Please remember to do npm i --no-save --no-package-lock (bare-metal installs only; docker containers are always up-to-date).
Add ability to override the state of a rule from the UI, for logic debugging purposes. A disabled rule will have its state forced, but will not run its reactions. An enabled rule will also have its state forced, but the corresponding rule reaction will run on the state transition. When overridden, the trigger and constraint conditions have no effect on the overall rule state, but (if rule enabled) are still evaluated and their status is still accurately displayed on the status card for the rule in the UI.
PR 0000357: Implement getRule() extension function to get rule metadata; refer to the docs for more.
Fix an error in the handling of the entity action cache in the UI.
Docs: improvements to description of custom event handlers for HassController (still a work in progress, but isn't everything?).
Docs: add a section in VeraController doc for the firmware's UnsafeLua flag, required to be on for the x_vera_sys.runlua action to be available. The value is now also published as an attribute on the system entity.
HassController: Implement new HA valve domain with our valve capability.
HassController: Bless Hass to 2024.2.2

23344

PR 0000294: InfluxFeed now supports exporting of global variable values to InfluxDB. See docs.
VirtualEntityController: Fix issue where a global variable dependency (value change) was detected, but the old GV value was always retrieved.
Dashboard: Strings displayed by ValueSensor widgets are now elastic-sized to reduce overflow.
Dashboard: Fix group spec handling so that custom top-level dashboards for a group can be created. This needs documentation.
HassController: Bless Hass to 2023.12.1

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

Expressions: Update lexpjs to fix degenerate case of case with single when and an else (which is better written as an if...then...else, but shouldn't throw an error in any case).
CallMeBot: the built-in CallMeBot notifier is now deprecated. There are no plans to remove it right now, but it will not receive future updates. Use HTTP Request actions directly in Reactions instead.
Reduce the frequency of reminder alerts when an upgrade is available.
HassController: Bless Hass to 2023.11.3

23302

Expressions: functions asin(), acos(), atan(), and atan2(), and the reserved word pi (lowercase), are now supported (identical to their JavaScript equivalents).
Update the documentation for migrating (importing) rules from Reactor for Vera (the Vera Reactor Plugin).
HassController: All use of x_hass.call_service (the entity-based service call action) now uses the target field to specify the entity_id, rather than the old form which embedded the entity_id in the data field.
HassController: The x_hass_system.call_service (system-global service call action) has been extended to allow the user to enter a target field for service calls that benefit from it. It should be noted, however, that the x_hass.call_service action on a Reactor entity (mapping a HA entity) should be used in preference to the system-global service call whenever possible, as changes in ID by HA will break the system-global call without warning (entity-based service call actions will simply use the new ID given by HA).
PR 0000360: Fix expression meta modification example in docs.
HassController: Bless Hass to 2023.10.5

23242

Rules Editor: Fixed an issue where a cond option change to the duration operator with no change to duration value may not be saved.
HassController: Add mapping for proximity domain (to value_sensor).
HassController: Bless Hass to 2023.8.2

23218

Improve the initialization of new global variables so they don't show "not yet evaluated" until a non-null value is set (null is a valid evaluation result and should remove the "not yet").
Expressions: improve the display of non-printing characters in the expression editor's "current value" display (they now display as Unicode escape sequences).
i18n: Fix init of localized weekday names when most recent Sunday occurs in prior month (caused, for example, incorrect weekday checkbox labels in Weekday conditions; cosmetic only, no operational effect).
SystemController: for Reactor update, include update branch, version, and commit as attributes on system entity.
Entities page: New Copy Attributes button in entity detail copies all attribute values to the clipboard.
HassController: Bless Hass to 2023.8.0

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.

Introduce a maximum delay in the write-back of certain storage containers (e.g. that used for expressions).
Docs: fix an error in an example on the How-To: Expressions with Entities page.
HassController: Bless Hass to 2023.7.2

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.

HassController: Bless Hass to 2023.6.2

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.

PR 0000356: Fix an issue where a rule with multiple sunrise/sunset conditions using the between operator chooses the first condition's before/after constraints rather than its own (i.e. it was choosing the control states from the first row rather than the current row).
SystemController: the deprecated suninfo.sun_angle attribute is now removed (its replacement is suninfo.elevation).
HubitatController: Hub variables can now be set up to 1024 characters with hub firmware 2.3.5.135 and above; for earlier firmware, the limit is 255 characters. The length limit is enforced by the hub, not HubitatController.
HassController: Bless Hass to 2023.5.3

23114

Conditions: add is NOT TRUE and is NOT FALSE operators. The is NOT TRUE operator (for example) is unlike the is FALSE operator in that, if the tested value is null, the is NOT TRUE operator result would be true, while the is FALSE operator result would be false. This distinction facilitates some tests where it may be desirable to handle null as equivalent to either true or false without having to provide an additional, separate is NULL condition (and possibly an enclosing OR group).
DynamicGroupController: document group actions; this makes it an official feature (was experimental).
Engine/Rule: Clean up a misspelled method name.
InfluxFeed docs: update supported and recommended versions. [doc]
HubitatController: Tweak reconnect timing decay (allow for longer decay when hub cannot be contacted for an extended period).
Reactions: Clarify what "Disabled" means in the constraints of a Group action (incl. Repeat…While) of a reaction. It does not disable the actions in the group. The disable flag applies to the constraint conditions only, having the same effect as it would on rule-based triggers and constraints (i.e. it becomes as if the constraint conditions do not exist). [docs] and [docs]
HassController: Bless Hass to 2023.4.6

23078

Fix loading of local capabilities definitions broken in a previous build.
HassController: Bless Hass to 2023.3.5

23063

Reaction Editor (UI): restore wide fields in HTTP Request action; injection from changes in 23049.
Reaction Editor (UI): fix detection of substitution in some cases that would cause single-action "try" button to not be disabled when a substitution was in the action's parameters (substitution isn't performed on single-action try).
Entities Page: Action dialog now warns that substitution isn't performed in that tool (launching an action from entity detail panel).
HassController: support for humidifier/dehumidifier (domain/service and device class, respectively).
VirtualEntityController: Fix an error in config check that was not allowing underscore (_) in entity IDs.
VirtualEntityController: Enforce x_virtualentity.set_attribute parameters more aggressively (better error message when not provided).
VirtualEntityController: Fix an error in x_virtualentity.set_attribute that would cause the HTTP API to not give a response when the action completed.
I18n: Rework the loading of locale settings files, their relation to the node or browser locale, and the configurable overrides. Reactor will now use the requested locale (host config, browser config/URL, Reactor config) even if a translation file is not available for it. This places the burden on JS' native Intl, which is ample, and reduces some complexity in Reactor's model.
HassController: Bless Hass to 2023.3.1

23049

Rule and Reaction Editors: Use fixed "helper" for drag/drop to circumvent limitations in jQuery-UI causing odd restrictions and side-effects when dragging large objects (like HTTP Request actions). It's not as cool-looking, but function over form is required here.
Docs: Provide installation link for community-supplied HassOS add-on; thank you to mrw298 for this.
HubitatController: Do not automatically select the Hub Information device for health probes; the new Hub Information v3 operates differently from previous versions and now is longer usable for health probes. A device will be chosen at random unless the probe_device config is set. [docs]
HassController: Bless Hass to 2023.2.5

23028

UI/Rules Editor: Collapsed sections now change the color of the "hidden content" badge -- red if the hidden content contains an error that needs to be corrected before save, green if it contains modified conditions or actions, and info blue (as before) if no errors and unmodified. No badge is shown if the section is empty (as before). The badge icon has been changed to a crossed eye.
Docs: Add Portainer installation instructions: https://reactor.toggledbits.com/docs/Installation-docker-portainer/
EzloController: If there are too many consecutive timeouts on requests to the hub, recycle the hub connection.
HassController: Bless Hass to 2023.1.7

23010

Stop Reaction action now allows you to stop the current/running reaction. This is intended to be used in constrained groups, where a match to the constraints may stop the reaction to prevent it from doing anything else.
New ev_charger system capability.
Reaction Editor: Fix incorrect storage type for boolean arguments affecting some controllers.
HassController: Bless Hass to 2023.1.2

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.

Expressions: isNaN() now returns false when passed null. This is now different from JavaScript, where parseFloat(null)/parseInt(null) return NaN, but isNaN(null) (oddly, IMO) returns true.
Fix an error in Group class implementation that was causing spurious errors from DynamicGroupController after a member entity was deleted or purged.
VeraController: Improve detection of UV sensor child devices registered as GenericSensor device type and having LightSensor1/CurrentLevel state variable when LightSensor1 isn't even a declared service for the type (i.e. a mess). This applies specifically to Aeotec Multi-Sensor 6 devices on 7.32beta4, but may apply to other devices/firmware.
EzloController: Sound sensors are now handled with Reactor value_sensor capability.
HassController: Bless Hass to 2022.12.6
i18n: Improve messages for Rules/Predicates when dependent objects are missing.
Improvements from the 22343 silent release (see below).

22343

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

EzloController: Guard against missing item enumerated in data for a device (data inconsistency in Ezlo API's returned device data).
UI Entities List: UI now stores the last 10 actions and their parameters, and restores the parameters when an action is repeated.
UI Entities List: Action parameter default values for certain types are now provided correctly (some types would come up blank even though a non-blank default was provided in the parameter definition).