For anyone interested in working on the bleeding edge, version 3.4 (development) has been posted to the Github stable branch.
This is not a hotfix release or suggested upgrade. This is FYI only. If you like testing new stuff, this is for you. Otherwise, you can stay right where you are on the released 3.3 version (for which there are no hotfixes as of this writing).
Notable:
- In response to a question by @CaptainMoody, it is now possible for an activity to run (i.e. call like a subroutine) another activity in the same or another ReactorSensor;
- I often see need/request to “pulse” a condition/group, and until now, that’s been done with a two-condition interlock + delays. This version adds “pulse” output mode: the output of a condition or group can be configured to stay true for a configurable period of time and then reset to false on the expiration of that time. The pulse is not sensitive to changes in the input during timing–see the image below. The output mode is selectable on the condition options. The default mode is “follow”–the output remains true while the underlying condition is true (as in all prior releases). This addition also inspired me to rework the appearance of the condition options panel.
Green line: state of device under test (for example); red: pulse output.
Full change list so far:
- Enhancement: The new “Run Group Activity” action in group state activities can be used to run an activity in the current or another ReactorSensor.
- Enhancement: The RunScene service action has been extended to allow running of group state activities (related to new Run Activity action).
- Enhancement: When exporting a variable, the underlying device state variables are created on save; previously, it would take an update of the expression result to get the state variable created (and thus was not immediately available in the Conditions editor, for example).
- Enhancement: The transition of a sensor from disabled to enabled state clears all prior condition state data; this starts with a clean slate, in case the sensor has been disabled for some time. There was also no easy way to clear the state, and doing it on Restart actions proved a little aggressive in testing.
- Enhancement: Add “Reset Latched” action for activites to reset latched conditions in a specific group or for the entire RS (adding new way to reset latched conditions).
- Enhancement: Condition and group logic output is now distinctly settable in three modes: follow (maintains true output while underlying condition is true), pulse (pulse of configurable length starting when underlying condition goes true), and latch (go true when underlying condition goes true and holds until reset). The default is follow, which is also the legacy behavior. The output type is settable in the options pane for the condition.