Reactor-Editor / Reactor-ui-Status Errors

[toggledbits]

Reactor build 22248

Docker Container Users: After upgrading to this build image, please check your NODE_PATH environment value in your container configuration; it should read /opt/reactor:/opt/reactor/node_modules. If it does not, please correct it (some container managers, including Synology, do not automatically reapply/update values from newer images to existing containers).

• Run Reaction action: New option "wait for completion" causes the current reaction to wait for the started reaction to finish. When unchecked (default), the started reaction runs concurrently with the reaction that starts it. This (concurrent) is the behavior of all prior versions of Reactor, and since unchecked is the default, the behavior of your existing reactions does not change (unless you go in and change it). docref
• Internal changes to support general release of ZWaveJSController.

---

ZWaveJSController build 22248

• Reduce default logging level to 5.
• Remove unused dependency.

[toggledbits]

Reactor build 22251

Bare-metal Install Users: If you are upgrading to this version from any version prior to 22233, you need to update your package dependencies. Please see the announcement for that build for instructions.

Docker Container Users: If you are upgrading to this build from any build earlier than 22248, you need to check that your NODE_PATH for your container is correctly updated. See the announcement for that build for details and instructions.

ALL USERS -- REMINDER: A hard refresh of your browser is necessary after upgrading to any new build.

• PR 0000328: Rule Editor: editing condition options of parent of nested groups opens child's condition options panel (fixed).
• Entities list: fix name search parity with Entity Picker (ID matches).
• Change the way object arguments to actions in reactions are stored. Previously, they were stored in the reaction as native objects by converting the given string as JSON (the input was expected to be JSON) in the UI. This made expression substitution unavailable in those (object) arguments. Now, they are stored by the UI as given (i.e. a string), so substitutions are now available in those arguments. This specifically removes the limitation that x_hass_system.call_service could not perform substition in its data argument. It now works as expected. A deprecation warning has been added to the Engine to detect argument values stored as native objects in actions that will cause an alert to be displayed notifying the user that the reaction/action needs to be edited. Any trivial edit to the field, followed by a save of the reaction, will update the form of the data and eliminate future alerts.
• Dashboard: Fix stray "x" displayed on Sensor layout when source entity's units are null.
• HassController: Bless Hass to 2022.9.0

[toggledbits]

Reactor build 22252

Bare-metal Install Users: If you are upgrading to this version from any version prior to 22233, you need to update your package dependencies. Please see the announcement for that build for instructions.

Docker Container Users: If you are upgrading to this build from any build earlier than 22248, you need to check that your NODE_PATH for your container is correctly updated. See the announcement for that build for details and instructions.

ALL USERS -- REMINDER: A hard refresh of your browser is necessary after upgrading to any new build.

• PR 0000329: Rule Editor: editing sunrise/sunset condition, if only sunrise/sunset selectors are modified last, the rule does not save as configured. If other condition fields are edited after, it saves correctly.

[toggledbits]

Reactor build 22256

Bare-metal Install Users: If you are upgrading to this version from any version prior to 22233, you need to update your package dependencies. Please see the announcement for that build for instructions.

Docker Container Users: If you are upgrading to this build from any build earlier than 22248, you need to check that your NODE_PATH for your container is correctly updated. See the announcement for that build for details and instructions.

ALL USERS -- REMINDER: A hard refresh of your browser is necessary after upgrading to any new build.

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.

• PR 0000331: In the "Pulse" output condition options, the option to limit the number of pulses vanished from the editor during the upgrade to Bootstrap 5 (i.e. since 22233). It has been restored. This did not affect the operation of existing repeat count limits on conditions. If a pulsing condition was edited, that would have removed the limit, so if you use this feature, you might check those conditions that should use it. Opening the rule detail in the Rule Sets list of rules to see the condition descriptions is sufficient to see if it's there or not -- you don't need to go into the editor to see it. When present, the condition description will include "repeat after x seconds up to y times."
• Fix spurious data format warning for HTTP Request actions.
• Entities now have metadata (data about data) for each attribute that provides the time last modified, as well as the previous value and the effective time of the previous value. In addition, any data type and other definition information known for the attribute will also be present. The quickest way to see attribute metadata is to hover over the name of an attribute in the detail panel of an entity in the Entities list. The attribute metadata is accessible in expressions via each entity's attribute_meta property. The subkeys of this property are capability names, and within each capability are the attribute names, and within the attribute names are the metadata elements. For example, in the commonly used form of expression getEntity( entity_id ).attributes.power_switch.state we would get the value of the state attribute in the power_switch capability of whatever entity was matched; this tells us if the switch is on or off. To get the time that value was set, we would use getEntity( entity_id ).attribute_meta.power_switch.state.last_modified. Those of you trying to use the lastupdate property on an entity for various purposes (such as failed node detection) should particularly take note of this change and the capability it provides.
• Docs: New page Expressions with Entities & Attributes in the How-To section.
• (Advisory) HubitatController: Hub variables are limited to 255 characters by the hub firmware. Attempts to set a hub variable to a longer string will fail. See the Limitations in the HubitatController docs for more details.
• VeraController: The sys_system.reload action was incorrectly reloading the remote Vera hub; that's not really its job, but rather the job of x_vera_sys.reload. If you have been using sys_system.reload to restart Luup, please switch to x_vera_sys.reload. As of this build, sys_system.reload will cause VeraController to resync all devices and entities (i.e. it's a restart of VeraController, not your Vera).
• HassController: Bless Hass to 2022.9.2

ZWaveJSController build 22256

• Send notice (displays in Status widget) when a new node is discovered.

[toggledbits]

Reactor build 22257

Bare-metal Install Users: If you are upgrading to this version from any version prior to 22233, you need to update your package dependencies. Please see the announcement for that build for instructions.

Docker Container Users: If you are upgrading to this build from any build earlier than 22248, you need to check that your NODE_PATH for your container is correctly updated. See the announcement for that build for details and instructions.

ALL USERS -- REMINDER: A hard refresh of your browser is necessary after upgrading to any new build.

ALL USERS -- IMPORTANT: If you are upgrading to this build from a build earlier than 22256, please read the advisories for that build prior to proceeding.

• VeraController: Specific support for iBlinds2 (Window Blind Controller mfg 647 prod 3,13) to handle its 50%=fully open way of doing business (since the covering is made up of slats/louvers, the 0 and 100 positions are closed fully tilted one direction or the other, with 50% being "flat" between the two).
• VeraController: The generic cover.set action was missing, and native toggled capability support was added for window coverings (toggles between open and closed, as one might expect).
• Dashboard: The Cover widget (window covering) was not changing its icon when the covering changed state.
• HubitatController: Tighten checking and handling around oddly-named attributes. Apparently at least one Hubitat user has a device that has a HE-native attribute with a space in its name, causing an exception to attribute naming tightened in 22256. This was causing a no-start on the controller. This build maps out non-alphanumeric characters from Hubitat to underscores, and also provides additional error handling to prevent a single attribute from stopping the controller startup.

[toggledbits]

Reactor build 22258

Bare-metal Install Users: If you are upgrading to this version from any version prior to 22233, you need to update your package dependencies. Please see the announcement for that build for instructions.

Docker Container Users: If you are upgrading to this build from any build earlier than 22248, you need to check that your NODE_PATH for your container is correctly updated. See the announcement for that build for details and instructions.

ALL USERS -- REMINDER: A hard refresh of your browser is necessary after upgrading to any new build.

ALL USERS -- IMPORTANT: If you are upgrading to this build from a build earlier than 22256, please read the advisories for that build prior to proceeding.

• VirtualEntityController: This new controller type lets you create virtual entities (devices) and manipulate them. docs.
• Entities list: Fix metadata pop-ups that sometimes "stick", caused by the entity updating and the popper losing its reference element in the DOM. Also make the pop-ups more dynamic by updating them when the attribute updates.
• HassController: Devices that Hass identifies in the "motion" device class will get the motion_sensor capability in addition to the ubiquitous binary_sensor, and motion_sensor.state will be the primary attribute.
• VeraController: Make sure all extended per-Vera-service capabilities are defined as stubs.
• HassController: Bless Hass to 2022.9.4.

[toggledbits]

MQTTController build 22260

• Add new template owntracks_in_region

[toggledbits]

Reactor build 22264

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

• VirtualEntityController: Added ability to make periodic HTTP requests and parse results to apply to attributes (see docs).
• PR 0000332: Fix missing "minutes" label (since BS5) on Interval condition fields (cosmetic).
• Added new location capability for geographic location (attributes: latitude, longitude, elevation). This is intended as a target for geolocation integrations.
• Docs: Updated for new owntracks_in_region template.
• Docs: Fixed an error in the example config for VirtualEntityController.
• HassController: Bless Hass to 2022.9.5

[toggledbits]

Reactor build 22266

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

• PR 0000333: EzloController: problem with wss (secure websocket) connection injected at 22264.

[toggledbits]

Reactor build 22274

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

• HubitatController: Fix too-aggressive caching of entities that makes entity names too "sticky" when device name or label is changed on hub. Note that a particularity of Hubitat, unlike most other hubs currently supported, requires a soft restart of either the controller instance (using sys_system.restart on the HubitatController's system entity) or a restart of Reactor to "see" the rename (Hubitat does not send an event when a device is renamed, so Reactor can't know).
• HassController: Bless Hass to 2022.9.7

[toggledbits]

Reactor build 22291

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

• HubitatController: Breaking change: Devices that use HE's PressureMeasurement capability will now report pressure on pressure_sensor.value rather than the generic value_sensor.value. I'm not sure this is widely used if at all, so I chose to just make the breaking change rather than deprecate and hold on to the old behavior for months.
• PR 0000283: Reactions Editor: allow drag-drop between groups. This still has some minor issues, but these are due to limitations/defects in jquery-ui (so we'll have to live with them for now).
• PR 0000334: Docs, fix an error in the example expression for metadata.
• HubitatController: Implement polling as a replacement for Hubitat's Z-Wave Poller app, which is widely reported to not work well (the author's own experience corroborates these reports). Polling is only needed for legacy Z-Wave devices that do not support instant status or some equivalent (hail, etc.) that Hubitat understands. [docs]
• DynamicGroupController: the include_entity and exclude_entity selectors now can use a regular expression to match entity canonical IDs. [docs]
• InfluxFeed: New advanced attribute handling key skip_null to suppress export of null measurement values; [docs]
• Fix a sync issue in the UI when deleting entities that previously required a hard refresh of the browser.
• UI: Fixed alignment of icons and buttons for large items in the Alerts widget (Status page).
• Documentation: Updated documentation on building Controllers, and provided new example code (WhiteBITController).
• HassController: Tighten capabilities for voltage, current, energy, power, and humidity sensor types. If you have automations using temperature or humidity sensors in Hass, please make sure your conditions use the temperature_sensor.value or humidity_sensor.value attributes, and not the generic value_sensor.value attribute -- this generic attribute is now deprecated and will be removed from a future release.
• HassController: Bless Hass to 2022.10.4

MQTTController build 22291

NOTE: This version requires Reactor version 22291 or higher.

• Add optional default value in topic substitutions. That is, the substitution string %flavor:chocolate% would insert the word chocolate if flavor was not defined in the entity configuration.
• Template owntracks_in_region adds a user field that can be set if your Owntracks needs it. The Owntracks topic is /owntracks/user/deviceid, so the user field should be set in your entity configuration (with topic and regionName to whatever is in that user portion of the topic (e.g. if your Owntracks publishes owntracks/fred/fredsphone then topic should be set to fredsphone and user should be set to fred).
• Code cleanup and sync with Controller base class updates.

ZWaveJSController build 22291

NOTE: This version requires Reactor version 22291 or higher.

• Code cleanup and sync with Controller base class updates.

[toggledbits]

Reactor build 22293

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

• PR 0000337: Condition with "sustained for" less than X seconds malfunctions (triggers immediately).
• PR 0000336: Fix group error indication not clearing when creating new group in a reaction (global or rule-based).
• Fix an error in the translation string for "sustained for" options when the "less than X seconds" form is used (was showing incorrectly in rule status view human-readable form).
• VirtualEntityController: scheduling of HTTP requests can now be done at specific times via the at setting for the request (an alternative to interval). [docs]
• VirtualEntityController: the quiet_failure flag now accepts either a boolean value or integer; if boolean true, notifications are never sent for failed HTTP requests. If numeric, a notification is sent only after that number of requests has failed. [docs]

[toggledbits]

Reactor build 22302

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

• UI/Status: Running Reactions widget now has "stop" button to terminate a running reaction (caveat operator).
• UI/Status: Tighten the display up a bit (remove excess whitespace).
• UI/Status: Fix alerts list that can overflow its container horizontally, causing a confusing display with multiple scoll bars.
• UI/Rule Editor: An notice/badge is now shown for collapsed sections that are not empty (i.e. when content is hidden).
• Fix condition operator "is EMPTY" (and its negated partner) on array type operand (only) was incorrectly reporting not empty in some circumstances.
• Additional UI embellishments for condition (triggers/constraints) and action (reactions) drag-drop. Still some limitations/inconsistencies/bugs in jquery-ui (which provides the drag/drop/sort implementation). If you can't get your object exactly where you want it, drop it close (i.e. into the group you want it in), then drag it again to its final position within the group.
• Action logging from all controllers now uses INFO level logging rather than forced logging (this is mostly a help to me because I separately log warning and higher priority in my test and home configurations so I can more clearly see errors -- it removes noise from that).
• HassController: Bless Hass to 2022.10.5

[toggledbits]

Reactor build 22305

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

• Engine: fix bug that could cause expressions having array or object results to not detect change reliably.
• UI/Rules/Reactions: the changes operator should not be available in constraints (changes is an event, and constraints are static, not event-driven).
• UI/Rules Editor: enforce minimum size for condition type menu (tidier layout).
• UI/Reaction Editor: improve field layout, prevent fields from pushing controls out of container, enforce minimum size for action type menu (tidier layout).

[toggledbits]

Reactor build 22308

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

• PR 0000343: Fix missing fields for notification action (Pushover title reported; 22305 injection).
• PR 0000342: Documentation fix, error in example code for if expressions in Expressions doc.
• PR 0000341: Ease entity ID restriction (for users with international characters in entity IDs).
• PR 0000340: Localization of "upgrade available" alert message.
• PR 0000339: push()/unshift() functions not working as expected (not a lexp issue, it's a last-value storage/comparison problem when value is object type).
• PR 0000338: Version/license/meta info for extensions is now displayed on the About page.

[toggledbits]

Reactor 22328

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

• The baseurl config key/value is no longer required. It is used only in exceptional circumstances. It is now commented out in default configurations (dist-config/reactor.yaml), and setting it is no longer required as an installation step. Users configuring their systems to use HTTPS access to the Reactor UI should, instead of using baseurl: https://..., set use_tls: true in the reactor section of their configuration.
• Improve messages in Run Reaction actions when there is an error starting the reaction.
• DynamicGroupController: make sure change in group name in configuration is always applied at startup.
• HassController: implementation for device_tracker service to location capability.
• HassController: since HA appears to provide conversion, enable all color modes if any is supported.
• HassController: Add support for new xy_color capability.
• HassController: Allow YAML form service data in call_service actions. The service data can now be formatted as YAML or JSON. The former is the default unless { is the first character in the field, to preserve compatibility with existing actions using JSON data.
• Add xy_color system capability.
• Fix a startup issue on Windows.
• PR 0000345: Fix expression doc example for each statement
• HassController: Bless Hass to 2022.11.4

ZWaveJSController 22323

NOTE: This version requires Reactor build 22314 or higher.

• Allow zwave_device.set_config parameter to be either string (property name) or number (property/configuration parameter ID). This should improve usability for this action.
• Store property ID in metadata for x_zwave_values attributes.
• Improve "first guess" device support for many devices when Z-Wave JS is still running interviews and Reactor comes up (i.e. when data from Z-Wave JS about devices is incomplete).
• Improve device support for multiple Fibaro, Aeotec, Everspring devices.
• Improve manufacturer/device support for Remotec, Poly-Control, Danalock, Zipato, Nortek, NEO, Minoston (EVA Logik).

MQTTController 33326

NOTE: This version requires Reactor build 22306 or higher.

• Allow templates to be stored in individual files in a config/mqtt_templates subdirectory. This should improve users' configuration management for community-contributed templates.
• Additional error checking in install script.
• Implement entity deadmarking like other controllers.
• Improve entity initialization/resilience to isolated configuration problems.
• Incorporate some device template fixes from @therealdb (with gratitude for his ongoing contributions).
• Support for deterministic updating of attributes on a topic by using a new/alternate array-based configuration syntax. [docs]
• Support for requires key in templates to facilitate user-feedback when a template is used but a configuration value required by the template it not provided by the user.

[toggledbits]

Reactor build 22337

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

• Rules UI: Improved detection in UI (or more correctly, notification from core to UI) of "trouble" on rules.
• HassController: reconfigure entities on HA version change; support for person, weather, number, button, sun.
• HTTPAPI: API requests are now logged by default.
• HTTPAPI: A malformed monitored_entities configuration will no longer prevent the perform API request from completing.
• HassController: Bless Hass to 2022.11.5

[toggledbits]

Reactor build 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.
• 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).
• 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).

MQTTController build 22350

• Improve handling of x_mqtt_device.online attribute for templates that have custom LWT event.

[toggledbits]

Reactor build 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

MQTTController build 23010

• Fix spurious message when stopping MQTTController instance.

ZWaveJSController build 23011

• Fix a possible runtime error during node configuration if the target node isn't yet fully ready.
• Support for iblinds V3.

[toggledbits]

Reactor build 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