Skip to main content

FAQ

Do I need WiFi?​

No.

ArmorLink uses ESP-NOW for module communication and does not require a WiFi network.

Do I need a Gateway?​

For modular systems, yes.

The Gateway handles:

  • Routing
  • Pairing
  • App communication
  • Presence monitoring

For single-device projects, a module can also run in Gateway mode.

Do I need BLE on every module?​

No.

Typically only the Gateway enables BLE.

The ArmorLink App connects to the Gateway, which communicates with other modules through ESP-NOW.

No.

Modules can communicate entirely without the App.

The App is a management and diagnostics tool.

Can modules send commands to other modules?​

Yes.

ArmorLink.sendCommand(
    "Helmet",
    "Facemask",
    "toggle"
);

Commands are routed through the Gateway.

Can a module send commands to the Gateway?​

Yes.

ArmorLink.sendCommand(
    "Chest",
    "BTN_R1",
    "SINGLE_CLICK"
);

The Gateway can react using Actions just like any other module.

Can I broadcast commands?​

Yes.

ArmorLink.broadcastCommand(
    "Flaps",
    "toggle"
);

All modules exposing a matching Action will react.

Do I need heartbeat packets?​

No.

ArmorLink uses activity-based presence detection.

Any communication updates a module's last-seen timestamp.

The Gateway automatically tracks module activity.

When a module exceeds the configured timeout, it is considered offline.

Are configuration values stored automatically?​

Yes.

Configuration values persist automatically on the module.

No additional storage code is required.

Does changing configuration require a reboot?​

No.

Configuration changes are applied immediately.

Optional change callbacks execute automatically.

Can multiple modules react to the same command?​

Yes.

This is commonly used with Broadcast Commands.

Does telemetry run all the time?​

No.

Telemetry is only active when requested by the ArmorLink App.

This minimizes ESP-NOW traffic.

Are log messages always sent?​

No.

Remote Logging must be enabled by the ArmorLink App.

Log level filtering can further reduce traffic.

Are warnings and errors rate-limited?​

No.

Warning and Error messages are treated as important diagnostic events and are not rate-limited.

Yes.

ArmorLink works with any ESP32-based distributed system.

Examples include:

  • Robotics
  • Props
  • Interactive installations
  • Home automation
  • Sensor networks
  • Wearables

Which ESP32 boards are supported?​

ArmorLink targets ESP32 devices that support ESP-NOW.

Examples:

  • ESP32
  • ESP32-S3
  • ESP32-C3
  • ESP32-C6