Skip to content

Version 3.9 (21126)
Compare
Choose a tag to compare
@toggledbits toggledbits released this 06 May 21:19
· 37 commits to master since this release
v3.9
f78ea0a
  • DEPRECATION: The Reactor.groups table is now deprecated; use Reactor.conditions instead (just change the name in your code, it works the same). See the Reactor documentation for more information.
  • Enhancement: There is now a "group copy/import" on (sub)groups to allow the contents of another group to be copied into the current group.
  • Enhancement: In the Reactor.conditions table, if the condition is actually a group, the subkey conditions will be an array containing the group's conditions. See the Reactor documentation for more information.
  • Enhancement: Direct support for the VeraTelegram plugin in the Notify action.
  • Enhancement: Notifications via Pushover are now supported by the Notify action. DOCS NEED: sign up and verify your email address; copy user key to PushoverUser; go to "Your Applications" and create a new application; put API token in PushoverToken.
  • Enhancement: Allow interval "relative to" time to include absolute date.
  • Enhancement: Loadable functions can be used to create user-specific/custom functions for expressions. See the docs.
  • Enhancement: Built-in updater from Github via the About tab on the Reactor master device.
  • Fix: Only enforce ALTUI version when running the Reactor UI from the ALTUI UI (i.e. if ALTUI is installed on Vera and the user is using the Reactor UI from the Vera UI, don't worry about ALTUI).
  • Fix: Try to clean up field placement/formatting on Firefox Android under ALTUI.
  • Fix: Try to resolve more inconsistencies between the ancient jQuery and Bootstrap-ish stylesheet on Vera vs the more current used on ALTUI. They just don't have much in common any more, and it's getting very difficult to work out combinations of published and custom styles that work out cleanly for both. If ALTUI continues to press forward, it will eventually diverge enough from Vera's environment that separate UI code bases will be needed. Given that more than 50% of Reactor's code is in its configuration UI, if it comes to that, I'll likely stop supporting the Luup plugin Reactor for openLuup/ALTUI, because it just doesn't make sense to maintain two very large, separate code bases for different platforms. Multi-System Reactor would be the go-to alternative at that point (and is going to work even better anyway).
  • Fix: ALTUI 2.52 (just released) now uses 3.5.1 jQuery with a modified HTML prefilter (breaking security fix); code changes throughout, very disruptive.
  • Fix: work around ALTUI not implementing JS API control panel close event.
  • Fix: work around ALTUI's emulation of api.showCustomPopup() uses different element ID for dialog.
  • Fix: ALTUI's api.showCustomPopup() produces different divs than UI7. Provide workaround (and fix to ALTUI requested).
  • Fix/Enhancement: NUL root group now does not manipulate RS tripped state. I count this as both fix and enhancement because (a) it seems logical it should have always worked this way (so fix), and (b) it's not necessary to change, but doing so supports a useful paradigm where an RS can use its own tripped state as a trigger for actions, specifically if the tripped state if changed by an HTTP request from outside the system -- it facilitates driving a reaction externally without additional virtual devices (so enhancement).
  • Fix/Enhancement: Bug in firmware for Vera3/Lite 1040 and below handling of ModeSetting delays house mode response; work around to restore performance.
  • Fix/Enhancement: Internet availability test is now offloaded to a script that runs as a daemon. openLuup users: please see https://www.toggledbits.com/static/reactor/docs/3.9/Network-Status/ for updated information on considerations for this platform.
  • Fix: fieldset positioning got a bit strange on recent releases of Chrome and Brave for Windows, maybe Mac. Firefox was not affected.
  • Internal: Enforce _UIV on ALTUI custom dashboard card.
  • Internal: further improvements to smooth startup of new RS (also published as hotfix 20313-01).
  • Internal: update directly from Github (via request, some distrubitions).
  • Internal: change default WatchResponseHoldOff to 0; watch responses now run in zero-task timing.
  • Internal: action execution now has time limit, pauses (zero-ms yield) when exceeded.
  • Hotfix 21111-01: Vera firmware beta 7.32 5372/3/4 breaks house mode arming/disarming, workaround for HMT.
  • Hotfix 20359-01: Fix a runtime error when a new, never-run, disabled RS is encountered in the master logic summary.
  • Hotfix 20320-01: Looks like UTF-8 handling has changed, so try to catch up.
  • Hotfix 20300-01: Fix an error in the event log pathname when rotating the event log (diagnostic only).
  • Hotfix 20291-01: Fix an error that makes geofence updating run as a job in all circumstances (normally only runs as a job when the JSON library is an older than 2.5+LPeg). This will primarily benefit Plus/Secure users who have install available library updates (mostly developers and power users).
Assets 2
Loading