TapiCubes

TapiCubes are Tapidu NFC readers. They present short-lived signed NFC tokens that customers scan with the mobile app to earn points.

Detail Sections

Each TapiCube has focused admin pages:

• Settings: base points, timezone, cooldown, assignment, lifecycle, and optional location label.
• Rewards: scheduled reward windows for happy hours or special earning periods.
• Operations: remote setup, working hours, LED behaviour, health thresholds, OTA polling, and remote restart.
• Status: heartbeat details, firmware version, uptime, heap, WiFi RSSI, IP address, and OTA status.
• Console: remote firmware logs for failures and support diagnostics.

Moving A TapiCube

An active TapiCube cannot be moved to another store. Disable it first, then change the assigned store.

Creating A TapiCube

When creating a TapiCube, the admin generates the signing secret. Save it immediately because it is not shown again.

Minimum setup:

• TapiCube code
• store assignment
• base points
• timezone
• signing secret

Optional setup:

• location label
• repeat tap cooldown
• reward windows
• remote config key
• OTA target release

Location label is optional. Use it only when a store has multiple TapiCubes and needs names like “Front counter”, “Bar”, or “Upstairs till”.

Operations

Use Operations for values delivered by remote config:

• working hours
• auto reboot interval
• LED brightness
• quiet hours
• WiFi and heap health thresholds
• remote poll interval
• OTA URL and interval
• setup-mode and restart requests

Disabled but non-archived TapiCubes can still poll remote config and status. This allows recovery without physical access.

Status

Use Status to confirm what the device is reporting:

• firmware version
• last heartbeat
• uptime
• free heap
• WiFi RSSI
• station IP
• OTA status and last error

If a TapiCube has no heartbeat, check remote config URL/key, WiFi, and whether the device has been flashed with heartbeat support.

Console

The Console page shows remote firmware logs. It is intended for support diagnostics, not customer history.

Useful console events include:

• remote config HTTP failures
• invalid remote config JSON
• status heartbeat failures
• OTA failures
• NFC exchange errors
• remote setup or restart requests