Reactor extends the function of a sensor within Nero, allowing a sensor to be in a true and a false state, similar to the way a Nero Multi can be in a triggered or not triggered state. Reactor uses your configured conditions to determine which state it is currently in and then to run the associated actions.
Ensure you configure Reactor sensors in the Web UI as the plugin is not fully compatible with the My Nero mobile apps.
- This is the main device page for Reactor and shows you the current status of everything configured for this sensor and their current state.
- This tab is where you configure your rules for determining if the sensor is true or false. You can use any combination of Device State, Group State, House Mode, Sunrise/Sunset, Weekday, Date/Time, Interval, Geofence, or Luup reload.
- You can combine these using NOT, AND, OR, and XORlogic gates. Not sure how logic gates work? Read our primer or dive into the Wikipedia article.
- NUL is a special type of Reactor type, used for creating groups referenced from within the sensor or elsewhere, but don't affect the state of the sensor they are a member of.
- Expressions allow you to store a little bit of information and reference that throughout your Reactor flow. Expressions can be either static information or basic evaluations such as the state of a specific attribute of a device, for example, lifetime energy usage or a Nero Plug.
- This is where you define the actual things that happen when the sensor changes state. An action can be a device action, house mode change, delay (wait), notification, Lua script, Nero scene, group activity, or reset the latched state of a Reactor sensor.
- The tools tab allows you to test your sensor by forcing a date and time or house mode. This page will also be extremely helpful with troubleshooting as it will allow you to understand the logic flow being followed with the Logic Summary.