Hostname: {{tasker.Hostname}}    |   Current Workspace: {{tasker.Workspace.Name}}    The current workspace is disabled - Click here to enable
{{tasker.JniorTime}}    |   App Version: {{tasker.Version}} Web Version: {{tasker.WebVersion}}

Workspaces

A Workspace is a collection of business logic represented by Tasks, Devices, Loggers, Signals, Triggers, and Schedules. You can have more than one Workspace loaded and evaluated by Tasker at a time. You can also have Workspaces loaded on the unit but are disabled.

Name Version Summary Notes
{{workspace.Name}} {{workspace.Config.Version}} {{workspace.getSummary()}} {{workspace.Config.Notes}} (no notes have been defined)
Create New Workspace | Upload Workspace...

* Workspaces that are colored RED with a darker GREY background and have a # prefix are DISABLED. Workspaces in BLUE are loaded and active.

Workspaces


* Workspaces that are colored RED with a darker GREY background and have a # prefix are DISABLED. Workspaces in BLUE are loaded and active.

Tasks

Tasks are groups of actions that will be executed. Logic can be applied to cause some actions to get executed or not based on the evaluation of that logic. You can drag n drop actions to reorder them. You can also clone an Action or an Action Block by using the clone icon or by holding the CTRL while dragging and dropping.

Actions for {{taskCtrl.getSelectedTask().Name}}

Devices

Devices are external connections that can be used in Task Actions. Theyare Ethernet based connections that you can give a Name to so that they are easier to reference.

Name Type
{{device.Name}}
Add Device

Loggers

A Logger is essentially a log file that has preferences that make it easier to use in Task Actions. To create the Logger you will need to provide a name the file location and the contents to be logged on each line in the file. Use {{ }} around a Signal to embed the value in the log entry.

Name
{{file.Name}} File Name
Headers
Timestamp Format
Schema
Retention Count
Value to log on error
Log null on Boot
Add Logger

Signals

A Signal defines an I/O point to be used in various Task Actions, Loggers, or Triggers. To create a Signal you must give it a Name, select a Device and select the Channel on that Device. Some devices, like the temperature probe, have multiple variables that are available. You will need to select the variable name that you wish to represent.

Name Signal Channel Variable
{{signalProfile.Name}}
Add Signal

Triggers

Triggers monitor signals for a certain condition to be met. Once that condition is met a Task is executed. To prevent a Trigger from being 'noisy' and executing repeatedly you will to create a Reset set point. This will ensure that the Trigger will not execute again until the signal has met the Reset conditions. An example would be Triggering on a temperature value where the temperature is hovering around the set point. The Trigger would fire everytime the temperature rises above the set point even if it falls below the set point for a brief moment in time.

triggers

Schedules

Timers allow you to execute actions once or on a recurring interval. The rules that are defined give you finer control over when the actions are valid. For example, a recurring interval of once an hour but a rule that defines that the actions should only be executed between the hours of 8am to 8pm. You can also execute a Task when the JNIOR Boots or when the sun rises in the morning or sets in the evening.

NOTE: Clock accuracy is important when scheduling tasks. Please make sure NTP is working. To make changes to NTP settings, please go to the WebUI. Please visit jnior.com for information regarding Troubleshooting NTP if your unit is not currently synchronizing.

Last NTP Success:

Name Schedule Rules Task Name
{{schedule.Name}}
Add Schedule