Reactor-Editor / Reactor-ui-Status Errors

[toggledbits]

Build 22004

• PR 0000289: Fix detection of loops in expressions, and add more aggressive checks for some conditions previously missed; make sure self-referencing expressions are not considered loops.
• EzloController: Update connection error recovery; cloud auth and token requests are now only done when the controller specifically denies the current token, or when too many connection retries occur. Implement retry decay, to further reduce queries to Ezlo's cloud. Overall, this makes EzloController more resilient in the face of Internet and Ezlo cloud outages.
• Update the little-used (that may be about to change) encrypted status packager to work in docker containers.

[toggledbits]

Build 22021

Bare-metal install: you must run npm i --no-save --omit dev in your Reactor install directory to install new dependencies.

• UI: Make it possible to bypass the About page at startup.
• UI: Status page now has movable, resizable widgets. A couple of new widgets have been introduced as well.
• HubitatController: Fix volume.set action (media players)
• Support for usermedia directory inside config; if present at startup, the built-in HTTP server will serve files from this directory (meant primarily for media/audio files, but will serve most common file types). This allows the user to serve files from the Reactor installation without the need to separately install Apache or another web server.
• HassController: Bless Hass to 2021.12.10
• Engine: predicates have been refactored to tidy up the code and remove some duplication of functionality created when reaction group contraints were introduced.
• Clean up the reactor_inet_check.sh script (in tools).
• Docker: the OS base for x64 generic and armv7l (RPi) is now Alpine version 3.14 (was 3.12);

[toggledbits]

Build 22022

Bare-metal users: you must remove any existing package-lock.json file from your Reactor install directory, and then run npm i --no-save --omit dev to update package dependencies. You will get a vulnerability warning; see this post. DO NOT run npm audit fix — it will break your Reactor install.

Docker users on Raspbian Buster (Raspberry Pi): you must install a patch to run the Reactor image in a container. See the install instructions for the steps to install the patch.

• Engine: New and very experimental Repeat While action group, repeats as long as its conditions are met. The group must have at least one condition or it will not run at all. The repeat will stop if either (a) the conditions result in false, or (b) if it's in a rule-based reaction, the contra-reaction is started by a change of rule state. It is quite possible to make reaction groups that never stop, so be careful with your logic here. This feature was not included.
• UI: Fix "Recently Changed Entities" not updating dynamically.
• UI: Fix an error in the new widget text on the Status panel.
• The node-fetch package requirement has been updated to version 2.6.7 or higher (in the 2.x release path). This version is patched against CVE-2022-0235 according to the package author. Bare-metal users will need to remove any existing package-lock.json file in their Reactor install directory, and then run npm install --no-save --omit dev. DO NOT run npm audit fix — it will break your Reactor install.
• Docs: Update package install instructions for bare-metal installs, and in the Troubleshooting section.
• Docs: Update docker container installation instructions for users of Raspbian Buster (only) with additional steps to install libseccomp2 patch required to run the image.

[toggledbits]

Build 22023

Bare-metal users: you must remove any existing package-lock.json file from your Reactor install directory, and then run npm i --no-save --omit dev to update package dependencies. The previously reported vulnerability warning should no longer be present.

Docker users on Raspbian Buster (Raspberry Pi): Reactor 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.

• PR 0000296: Fixed rule throttling caused by constraints subscribing for events when they should not.
• PR 0000297: Duplicate report for 0000296.
• PR 0000298: Global expressions not updating correctly, not triggering rules correctly.
• Engine: New and very experimental Repeat While action (a form of group), repeats as long as its conditions are met. The group must have at least one condition or it will not run at all. The repeat will stop if either (a) the conditions result in false or null, or (b) if it's in a rule-based reaction, the contra-reaction is started by a change of rule state. It is quite possible to make reaction groups that never stop, so be careful with your logic here.

[toggledbits]

Build 22025

Bare-metal users: updating package dependencies when updating Reactor is recommended. To update packages, you must first remove any existing package-lock.json file from your Reactor install directory, and then run npm i --no-save --omit dev.**

Docker users on Raspbian Buster (Raspberry Pi): Reactor 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.

• VeraController: allow arrays for filter_entity and accept_entity to be consistent with other similar applications.
• Fix an issue with setting a Rule's timebase before evaluation that may affect some rule-based expressions. Likely related to PR 0000301.

[toggledbits]

Build 22028

Bare-metal users: updating package dependencies when updating Reactor is recommended. To update packages, you must first remove any existing package-lock.json file from your Reactor install directory, and then run npm i --no-save --omit dev.

Docker users on Raspbian Buster (Raspberry Pi): Reactor 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.

• PR 0000301: Fix excess sensitivity to apparently unrelated devices in some conditions. I'm leaving this PR open; I think I know why this happened, and for my system it's working great, but I want to make sure I've covered all the bases, and because the fix was pretty aggressive, didn't inject anything new.
• Fix exception trying to subscribe to non-Observer in Variable Value condition.
• Logger: Allow maxsize: 0 in log stream configuration for no log rotation at all.
• Fix condition value seen on Date/Time conditions in rule status display (cosmetic).
• HubitatController: implement Reactor energy_sensor capability; replaces x_hubitat_energymeter, which is now deprecated.

[toggledbits]

MQTTController Build 22029 -- download

Please run the install script after unpacking the update.

• Echo function now publishes rule states and global variables. Please see the docs for more information.

[toggledbits]

Build 22044

• PR 0000306: Certain condition options not being saved for rule-based constraints.
• PR 0000305: Copying rule expression can renumber expression in source rule.
• PR 0000302: Reaction delay "from start" working same as "from this point".
• InfluxDB: Support for more extensive control of written measurements, including name and type modification; see docs
• Reactions: Fix an issue where missing device in a rule reaction does not flag trouble on the rule.
• Three new capabilities: valve, scene_activation and battery_maintenance. These will be fully integrated with eligible Controllers and Entities in a future release.
• Reactions: An error in a special form on the Comment action is fixed (simple notification).
• Expressions: New expression case statement; see docs
• Expressions: Fix sort in median() function.
• Expressions: An error in the fileRead() function has been fixed.

[toggledbits]

Build 22049

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

• Update lexpjs for new pad() function
• PR 0000307: Nested group would repeat interior actions outside group (reaction UI)
• Update to latest minor revisions of jquery-ui, bootstrap, popper. This now silences the long-endured warning when doing npm i --no-save --omit dev

[toggledbits]

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

• PR 0000308: Fix issue where delay action with substitition in delay may self-replace evaluated value in stored object.
• UI: Autogrow fields get more room for datalist controls.
• UI: Fix issue with some value lists incorrectly showing and storing index values rather than actual listed value; see BREAKING notice above.
• Bless Hass to 2022.2.9

[toggledbits]

Build 22067

Bare-metal Users: Please run npm i --no-save --omit dev when installing this update.

• PR 0000309: Exception while evaluating global reaction predicate (conditional group).
• HubitatController: Attempt to eliminate additional query to fetch full device data when a device-change event is received from the hub. Please see the documentation for cautions.
• UI will now highlight deprecated capabilities, attributes and actions when used.
• Bless Hass to 2022.3.3

[toggledbits]

Just an FYI for everyone, I'll be on holiday from tomorrow March 10 through March 19, and I'm leaving the laptop on the shelf at home for this one. I can answer emails and forum posts, but I won't likely be checking more than once a day, and I won't doing builds or any bug fixing while away. See you all on the other side!

[toggledbits]

Build 22069

Note: Only users of Hubitat hubs need to upgrade to this version, and then only if you previously upgraded to 22067.

• HubitatController: Fix a possible loss of attribute change across restarts of the hub (that is, when a value changes during a Hubitat restart but Reactor is not restarted).

[toggledbits]

Build 22080

• PR 0000311: Vera Scene controller entities missing attributes in new and exisitng rules
• PR 0000310: Dependent global variable may not update after editing parent.
• HubitatController: Because the HE events websocket passes all values as strings, the new fast-update process introduced in 22067 would change (for example) a previously-numeric attribute value to a string when updated by the hub. While this doesn't generally bother conditions or expressions, the type change affects InfluxFeed because InfluxDB cannot digest the type change. The data type declared by the hub during inventory is now stored and used to remap the events feed values to keep the data types consistent on the attributes. It must be noted, however, that the data types of extension attributes (x_hubname_...) are driven by the hub, and are therefore not guaranteed by Reactor (types are guaranteed for Reactor-defined capabilities, e.g. dimming, value_sensor, etc.). Users exporting extension attributes into InfluxDB are advised to always use explicit type setting for those attributes in their InfluxFeed configuration. This advisory has been added to the documentation for InfluxFeed.
• HubitatController: An inconsistency in the (HE) attribute names between their MediaPlayer and MusicPlayer capabilities with respect to transport state is now handled correctly, so that Reactor's native av_transport.state attribute shows a correct value regardless of which the device uses.
• SystemController: Will now issue system alerts unconditionally when disk space becomes critical (unless disk space monitoring has been disabled by user configuration), in addition to the (previously available) values and flags on the reactor_system>system (Reactor System) entity. It's also probably a good idea to add notifications (i.e. in your own rules) for such conditions raised by the system entity, if the user is not regularly looking at the Reactor UI. See the documentation for SystemController.
• SystemController: A dst (boolean) attribute has been added to the reactor_system>sun (Sun Information) entity; it will be true when Daylight Saving Time is in effect, false otherwise.
• HassController: Fix cover capability handling on non-positionable covers (e.g. garage doors).
• Dashboard: New display for cover entities.

[toggledbits]

Build 22118 (latest and zwavejs) — PLEASE READ ALL ADVISORIES BELOW

NODEJS VERSION REQUIREMENT: As previously announced, nodejs versions below 16 are no longer supported as of 2022-Mar-31. Bare-metal users (only) will need to upgrade their nodejs to version 16 (the current LTS version) or higher. Bare-metal RPi users can use the install script to do this. Docker image users needn't concern themselves; the image is built with an approved version of nodejs.

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

Remember to hard-refresh all browsers after upgrading and restarting.

• PR 0000316: Variable Value condition with substitution in operand may replace expression with value in saved rule.
• PR 0000315: Improve alert message when a Rule-based reaction fails.
• PR 0000314: Fix "self-subscribe" exceptions logged after creating new Rule with local expressions and a Variable Value condition (exceptions clear after restart of Reactor).
• PR 0000312: Expressions getEntity() helper not listing or updating attributes correctly (fixed).
• Raspberry Pi Install Script: Support for 64-bit installation on Raspbian Bullseye.
• Raspberry Pi Install Script: Can now be used to upgrade nodejs with a local (user-specific) install.
• UI: Faster core startup brings up the UI more quickly, and does not wait for controller startups, so a delay in a controller becoming ready (e.g. its associated hub is offline) will no longer delay the UI being available.
• UI: You can now add an SSL/TLS certificate and have the UI and API served over HTTPS (see How-To in documentation).
• New actions in sys_system capability to tell a Controller instance to purge unused entities (i.e. that no longer exist on the hub but are still present in Reactor), delete an entity (from Reactor only, not from the hub/mesh/etc.), and rename an entity (in Reactor, not at the hub/mesh/etc.).
• UI/Entity Picker: You can now move the entity picker by dragging its title bar.
• UI/Entity Picker: The name search field will now also match on entity IDs.
• UI/Reaction editor: Changing from a group or while to another reaction type while editing would leave the conditions behind (they should be removed); fixed.
• Expressions: lexpjs updated, adds yday (day of year), isoweek (ISO-8601 week number) and dst (boolean) to dateparts() function result.
• Status: Controller Status widget now sorts down/failed controllers first.
• Docs: Added How-Tos for serving media files from Reactor's built-in web server and set up HTTPS for the UI.
• HassController: Bless Hass version 2022.4.7.

REMINDER: If you need to post an issue related to this (or any) version, please follow the posting guidelines.

[toggledbits]

Build 22123 (latest and zwavejs)

This version primarily addresses a formatting problem in error messages when certain conditions (triggers and constraints) take an error (e.g. an Entity Attribute condition references an entity that no longer exists). This is cosmetic/display only and has no operational impact, but I thought it important to make a new release for the fix because of the difficulty of troubleshooting conditions with the broken messages.

If you are upgrading to this version from any version earlier than 22118, please read the release notes for 22118 in the prior post above.

[toggledbits]

Build 22136

NEW: This version adds the availability of 64-bit ARM docker images. This is recommended for Raspberry Pi 4 users on Raspbian Bullseye (only; Raspbian Buster users should continue to use the armv7l image). The 64-bit ARM images also work (and are tested) on the NVIDIA Jetson Nano (2GB model tested, but should work for all).

NOTE TO ALL USERS, ESP. CURRENT DOCKER USERS: Starting June 1, 2022, the naming of all deployed packages and docker images will be changed to remove the "raspbian" or "generic" component of the name. For example. the latest-raspbian-armv7l docker image will be named simply latest-armv7l, and the latest-generic-amd64 ZIP archive will be named latest-amd64. You will need to update your version upgrade procedures accordingly; users of docker-compose will need to make this change in their compose files.

• Additional localization updates;
• HassController: Bless Hass to 2022.5.4

[toggledbits]

Build 22140

NOTE TO DOCKER CONTAINER USERS: Starting with the first release in June 2022, docker images will be named only with the release branch and architecture. That is, the current latest-generic-amd64 will become latest-amd64, and latest-raspbian-armv7l will become latest-armv7l. This will require changes to your upgrade procedure, or if you are using docker-compose, the image value in your compose file.

• Additional localization updates;
• HassCOntroller: Bless Hass to 2022.5.5

[toggledbits]

Build 22142 (latest, zwavejs)

• PR 0000321: HTTP API perform action does not send response when it succeeds (clients then time out waiting for the response that never comes).
• PR 0000320: API Docs: Fix entity API examples.

[toggledbits]

Build 22149 (latest, zwavejs)

• PR 0000322: EzloController: provide mapping for Xiaomi Mini Switch (a single-button remote).
• Rule: make sure clear of trouble state (on startup) is saved if necessary (so UI updates properly without need to refresh).
• VeraController: Hack for variables named sl_, which are the special Luup state variables that always send updates/call watches even when set to the same value they already have (all other state variables in Vera/Luup do not behave this way, they only trigger events when their values change). In particular, these sl_ states are changed when lock codes on locks are entered, or buttons on scene controllers are pressed. For these uses, it is important that a repeated use of the same code or button signals an additional event, so Vera/Luup's uses these special sl_ states for those. VeraController now inserts an extra _updated attribute of the same name that can be used with the changes operator to detect when the sl_ states are updated. Refer to this forum post for more information.