Multi Input

The Multi Input widget lets people change device values straight from a dashboard - a set point for an optimisation algorithm, a mode, an on/off flag. Each row is one input that writes one field on one device - a contextual parameter such as contextMap.setValue, or any other field such as value.setpoint - and rows for different devices stack in a column. A row can also change one setting of a Rule Engine rule, such as a threshold or a sun event offset, so nobody has to open the rule editor for it.

Every device save is written to the device's log, so you can see afterwards who changed what.

Adding inputs

1. Pick one or more Devices.
2. Pick the field to write. The list shows the fields the first selected device already has; type a new one, such as contextMap.override, to add a field it does not have yet. System fields such as name, reportedAt or devEui cannot be picked, and a field cannot contain $, brackets, quotes or a part made only of digits. A field that holds several values (an object such as contextMap itself) cannot be picked either - pick one of the fields inside it.
3. Press Add inputs. One row is added per selected device.

The input type is guessed from the current value: a number gives a number input, true/false gives a switch, anything else gives a text input. Change it under the row's settings if the guess is wrong.

Adding rule settings

Switch Input changes to Rule setting, then pick:

1. The Rule.
2. The Component - Whole rule for switching the rule on or off, or one of its blocks.
3. The Setting, shown with its current value. A block with a single setting picks it for you.

Press Add input. The input type and the Min and Max follow the setting: a sun event offset is a number from -720 to 720 minutes, Active is a switch, a threshold keeps the type it has in the rule.

Block	Settings
Whole rule	Active
Sun event	Offset (minutes)
Value threshold	Threshold
Delay	Duration, in the delay's own unit
Redundancy check	Check interval, Max retries, Expected value

To save a rule setting the user needs a role that may edit rules (editor or admin) and write access to the rule, plus read access to see its current value - see Who can see a rule. If the rule or the block is deleted, the row says so and is locked.

Editing an input

Open a row with its edit button to set:

• Label - the text in front of the input. Defaults to the last part of the field name.
• Unit - shown after the input.
• Input type - Text, Number or On/off. Not shown for a rule setting, whose type the rule decides.
• Min and Max - number inputs only. Values outside the range cannot be saved, and Min cannot be above Max. Not shown for a rule setting that has its own range, such as a sun event offset.

Under Appearance:

• Base color (tints the icon) and Icon.
• Description - a smaller line under the label.

Layout

The Layout section is folded away at first; open it to change how the widget looks.

• Label width - how much of each row the label takes, from 20 to 80 percent.
• Show device name - the device's name under each label. On by default, so rows for different devices with the same field can be told apart.
• Row background and Row border - colours for every row. Reset returns to the default. On a dark background the row text turns white so it stays readable.
• Heading - an optional title above the rows.

Saving

Save button, under the inputs list, picks one Save button per row or a single Save all button that saves every changed row.

Change a value and press Save. Enter in a text or number input does the same: it saves that row, or every changed row when the widget has a single Save all button. An On/off switch has no Save button of its own: flipping it saves straight away, unless the widget uses Save all, where it waits for that button like every other row. A green message confirms what was saved. Numbers can be typed with a decimal point or a decimal comma. Only the changed fields are written, so the rest of the device is left alone.

• Inputs are locked while the dashboard is in edit mode.
• Users whose role cannot edit devices (the viewer roles) see the values but cannot change them.
• A device you only have read access to is rejected when you save, with a message that you don't have permission to change it. The field then shows the device's real value again.