Indicator Light
FREEBoolean status indicator light
When to reach for it
Indicator Light is the binary status pill: on or off, driven by a boolean field, a numeric threshold, or a string match. Use it for e-stop state, mode flags, gripper open/closed, fault flags: anywhere a glance beats reading a number. For the raw value next to the color, Value Display covers similar ground; its Warning/Critical threshold coloring is Pro-only.
Pick the right Mode
Boolean reads the field with plain JS truthiness, clean for std_msgs/Bool topics. Threshold compares a numeric reading against Threshold Value, for “motor temperature above 60 means warning.” String Match checks the incoming string against your String Mappings table for exact equality, useful for enum-style status fields like OK, WARN, FAULT.
Watch out for
- String Match compares values with exact, case-sensitive equality and no trimming. A topic sending
okagainst a mapping configured forOKfalls back to inactive, with nothing in the UI to explain why. - Boolean mode uses real JS truthiness, not a strict true/false check: a string field holding the text “false” reads as active, since a non-empty string is truthy.
- If Field Pathpoints at a field missing from the message, the light just goes inactive: there's no error state distinguishing a wrong path from a legitimately off value.
Configuration fields
The topic this widget reads data from. While connected, tap to pick from the topics the robot advertises.
Which field inside the message to read, as a dot-path, e.g. pose.position.x. Leave blank to use the message main value.
How to decide on or off: a boolean field, a numeric threshold, or matching text values.
In Threshold mode, the value the reading must reach to turn the light on.
In String Match mode, map incoming text values to colors (for example OK to green, FAULT to red).
Show a name under the light.
The color shown when the light is on.