MSR UI on a mobile browser

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

[toggledbits]

Build 22168 (latest, zwavejs, stable)

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

• NUTController (for Network UPS Tools) is now available as an installable extra.
• Documentation updates to reflect updated installation archive and docker image names.

[toggledbits]

Build 22178 (latest, zwavejs)

NOTE: I will be on holiday for most of the month of July, and with limited Internet access. During this time, I will not be able to provide software support, fixes or builds, and likely will not have much time or means to read and answer questions. Please step up and provide support to your peers if questions come up!

• HassController: Set null state for switches and sensors when Hass reports them unavailable.
• HassController: Bless Hass to 2022.6.7.
• Docs: Improve details in Synology/Docker installation.

[toggledbits]

Build 22179 (latest, zwavejs)

NOTE: I will be on holiday for most of the month of July, and with limited Internet access. During this time, I will not be able to provide software support, fixes or builds, and likely will not have much time or means to read and answer questions. Please step up and provide support to your peers if questions come up!

• HassController: Fix an issue that may randomly affect/disable assignment of primary attributes (since 22118).
• Fix a problem in after...within (time-restricted) sequence conditions.

[toggledbits]

Build 22203 (latest, zwavejs)

• Expressions: the time() function has been extended to allow parsing of date/time values in strings in forms beyond ISO-8601; most simple date/time forms should work, particularly those that closely adhere to your locale's default. A string that contains only a time will be converted to that moment on the current date; a string that contains only a date will yield midnight on that date. If a given string cannot be converted, an error will be thrown. Refer to the documentation for Expressions for more information.
• HassController: Bless Hass to 2022.7.6
• Docs: documentation for Reactions now includes additional information about rule-based reaction behaviors and action groups, and has been "modernized" to use the terminology of Multi-Hub Reactor rather than that of the Reactor for Vera plugin.

[toggledbits]

Build 22233 (latest, zwavejs)

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

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

• Upgraded the Bootstrap library to 5.2, which gave rise to a large number of required UI changes, and an opportunity for some useful cleanups. The Bootstrap Icons library was also upgraded to 1.9. All of this also means that Internet Explorer is no longer a supported browser (use its replacement, Edge).
• HassController: Bless Hass to 2022.8.6

[toggledbits]

Build 22240 (latest, zwavejs)

BARE-METAL USERS: If you are upgrading to this version from any version earlier than 22233, you need to update your package dependencies. Pleasee see the post for that build for instructions.

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

• PR 0000327: Reaction Entity Action layout for additional data fields is messy.
• VeraController: Ensure x_vera_device.failed and .configured are null if Vera fails to provide state for these values.
• EzloController: Dead-marking and automatic removal (after delay) of entities for Ezlo devices/rooms/scenes that no longer exist (functional parity with other hub Controller objects).
• HassController: Implement mappings for scenes, scripts, and automations. All of these can have their actions run via Reactor's script.run action. Automations also can be en-/disabled using the power_switch capability actions (and entity primary state is the automation's en-/disabled state). All appear as runnable scenes in the dashboard.
• UI: Improve highlighting of containing groups when sort/drop changes to conditions are made in the rules editor.
• HassController: Bless Hass to 2022.8.7

[toggledbits]

Just a news item: the ZWaveJSController is now an official add-on, available for download from extras. Instructions for installing it are in the Reactor documentation.

For (only) those users who have been using the zwavejs build series for testing ZWaveJSController, you will now need to go back to the latest build series, and install ZWaveJSController as referenced above. There will be no further builds on the zwavejs branch. Also, ZWaveJSController no longer requires an authentication key to use, so you can remove the auth entry from configuration (it will be ignored and is harmless if you leave it).

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