[Reactor] Bug when sending MQTT boolean payloads

[toggledbits]

Build 21349

If you grabbed this release before 06:00 on 16-Dec-2021 UTC, please grab it again and reinstall. There was an issue with the next-day rollover computing sunset times that I fixed in-line.

• Make sure client API uses port for WebSocket connection, so the UI works when on a proxy or tunnel.
• Global reactions now support action groups with constraints.
• EzloController: Additional energy capabilities on certain devices/items.
• InfluxFeed: Fix an error in parsing the configuration for select_capability with attributes listed.
• The suninfo capability (used by the Sun Information entity reactor_system>sun) has been expanded to include the elevation and azimuth of the sun's current position. The elevation is given in degrees above the horizon. The azimuth is given in degrees clockwise from North (compass direction).
• The suninfo attribute sun_angle is now deprecated and will be removed from a future release. If you are using it in conditions, please switch to using elevation, which is a better representation of the sun's position.
• A bug in the computation of day_length (in hours) in the extreme latitudes (i.e. where the sun does not cross the horizon at certain times of year) is fixed. During periods during in which the sun never rises, day length will be 0; during periods in which the sun never sets, it will be 24. Similarly, period could give incorrect results and will now report correctly or the conditions.

[toggledbits]

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

• HubitatController: Aggressive management of the event websocket connection, with additional diagnostic output by default.
• HubitatController: Fix error in setup of task queue (part of attempt to control pace of outgoing actions).
• Constraints: Loosen rules on condition options for constraints in rules (a stateful context), as opposed to those in global reactions (which are stateless).
• Docs: Improve description of the time() function so that it's clear it can convert time strings (in ISO 8601 format).

[toggledbits]

Build 21356

• PR 0000278: Fix an untranslated string in rule reaction name generator.
• SystemController: publish alert data on entity, making it available for use in conditions.
• EzloController: Fix bug where cancelling a house mode change causes the mode name to get the ID rather than the name.
• EzloController: support for additional items (power-related and seismicity).
• EzloController: remove power_switch as automatic capability on dimmable lights; not all Ezlo dimmable lights publish switch items, so use the presence of the switch item on a device as the trigger to extend power_switch.
• EzloController: Fix an error thrown when handling certain extension items (e.g. electric_meter_kwh, only on some devices).
• HubitatController: Fix handling of TamperAlert capability.
• HubitatController: Add config warn_unresponsive (boolean) to turn off (when set false) warnings for quiet channel reconnects.
• HubitatController: Support for extension capabilities where an attribute like current is provided without a matching capability.
• VeraController: Log slow responses from hub (helps troubleshooting bottlenecks).
• Engine: Fix error in restore of running tasks across a reboot.
• PR 0000279: Fix an error that leaves Variable Value conditions in global reaction constraints with no variable list from which to choose (should list global variables).

HubitatController - Additional Notes

The connection health probes have some new settings, described in the docs, to make the health checks as reliable as possible and eliminate false positives in the quiet channel checks. Primary among these is recognition of a device under control of the Hub Information (community) driver. I recommend that Hubitat users install this driver (and create a device that uses the driver, and publish that device through Maker API), as it has some predictable behaviors that make it perfect for health checks, and it gives you access to other information about the hub you may find useful in Reactor. This is not required; just recommended.

[toggledbits]

Build 21360

• PR 0000282: DynamicGroupController: fix an error that could cause preloading of entities to fail (started in 21356).
• Updated lexpjs to 21360 to correctly handle assignment to object/array members.

[toggledbits]

Build 21365

• HassController: Add fire_event action on system device, to fire any event.
• Deprecation warning when starting on nodejs version < 16 (still runs, just a notice).
• HubitatController: Enforce strict ordering on initial mode and HSM queries.
• HassController: Bless Hass version to 2021.12.7
• Docs: Add startup troubleshooting page to Troubleshooting section.

[toggledbits]

Build 22001

• PR 0000284: Rule Editor: Add function to clone condition or group
• PR 0000287: Date comparison error in "between" that spans year (MDHM form); resets incorrectly at 01-01T00:00 Fix end check for next edge

Happy New Year!

[toggledbits]

Build 22002

This version has only an EzloController fix, so those of you that don't use Ezlo hubs can skip this version.

• EzloController: Fix fast update attribute issue (hopefully). I can't fully test because my device selection is limited, but it works for what I have.

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