Segmented Switch

A row of two to five options, one selected — like a tab bar. Mode: Off / Auto / Manual. Speed: Low / Mid / High. It says which one at a glance, and the device gets a number.

What it does

Each segment carries a label you see and a value the device receives. Tapping a segment writes its value to the signal — 0, 1, 2 by default, or whatever you set. Exactly one segment is selected at a time; the app shows which, and the device knows it the instant it changes.

When to use it

• A mode — Off / Auto / Manual for a heater, an irrigation, a light. The device switches its own logic on the index.
• A preset — Low / Mid / High mapped to three PWM duty cycles.
• A source — A / B / C: which sensor, which channel, which tank.

Set it up

1. Place it — In edit mode, tap + at the bottom of the dashboard and choose Segmented Switch under Controllers. It lands on the grid with three segments.
2. Wire it to a signal — Tap the widget, open the Data tab, tap + Add a target and pick an Integer signal on your device.
3. Name the segments — In the same tab, under Segments, give each segment its label — Off, Auto, Manual — and the value it sends. Tap + Add a segment for a fourth or a fifth, or the bin to remove one; two is the minimum.
4. Try it — Close the settings, tap ▶, and tap a segment: the device receives its value.

Settings

Tap the widget in edit mode: the sheet opens with a live preview at the top, then two tabs — Data for what it reads or writes, Appearance for how it looks.

Data — what it writes

Targets

Segments

Appearance — how it looks

Title

Display

Colors

States

• Run mode — a tap selects the segment and writes its value; the previous one goes flat. Only one at a time.
• Set by the device or a rule — writing a segment’s value to the signal selects it on the dashboard.
• Device offline — a mode is a state: ISignal with Restore brings it back on reconnect.

Arduino device code

The address is all the device knows — I5 here; use the one the app gave your signal. In the sketch, index is the value of the segment that was tapped:

ISegmentedSwitch(I5, int index) { … };

Complete sketch — Cloud

Paste it into the Arduino IDE, put your Wi-Fi and the token the app gave you, upload.

#include <InstantIoT.h>

const char* WIFI_SSID    = "MyWiFi";
const char* WIFI_PASS    = "MyPassword";
const char* DEVICE_TOKEN = "PASTE_TOKEN_HERE";

int mode = 0;   // 0 off · 1 auto · 2 manual — the segment values

ISegmentedSwitch(I5, int index) {
    mode = index;
    Serial.print("Mode -> "); Serial.println(mode);
};

void setup() {
    Serial.begin(115200);
    InstantIoT.begin(WiFiLink(WIFI_SSID, WIFI_PASS), Cloud(DEVICE_TOKEN));
}

void loop() {
    InstantIoT.loop();
    if (mode == 1) { /* auto: the device decides */ }
    if (mode == 2) { /* manual: the app decides */ }
}

Other connections

The widget block never changes. Only the begin() line says how the device reaches the app:

Direct needs no token: the phone is at the other end of the wire. See Connect for TLS, timeouts and what to do when it does not connect.

ISignal does the same job — and survives a restart. ISignal(I5, int v) runs with exactly the same value as ISegmentedSwitch(I5, int index): the widget block is the readable form, ISignal the generic one, and you can use either. The difference shows when the device reconnects: with Restore after a restart on the signal, the Cloud sends the last value again and only the ISignal block runs — a mode is a state — ISignal(I5, int index) with Restore on, and the device wakes up in the mode you left it in. See One block for everything.

Notes

• Give the segments the values your sketch already uses (0, 1, 2 for an enum) rather than translating in the block.
• Three or four segments read well; five is the maximum and gets tight on a phone.
• The same signal can be set by a rule at a set time — the switch on the dashboard follows.

Next

→ Switch — two states only → Advanced Button — one value per gesture, momentary