01Active work
Command
Lights the LED, may play sound, expects a worker action, and clears on ACK or timeout.
- Selector
commandorline1–line5- Lifetime
seconds- Feedback
- ACK / NACK
Button press → ACK → return to statics
Device field guide
From first flash
to closed loop.
A practical, interactive guide to driving Cloud Display Devices from your WMS, ERP, or a simple script.
Cloud Display Device
01
Quick start
Light your first device.
You need a powered Turbo, a Cloud Display Device with two AAA batteries, an API key, and the device's unique DeviceID.
- 01Connect the TurboUse Ethernet or Wi-Fi with DHCP. Then verify that its server and database status are okay.Check network prerequisites
- 02Find the DeviceIDLook in Big Block or call
GET /api/device/. DeviceIDs look likeFFFFFF:EEEEEE. - 03POST a commandTarget
/api/device/DEVICE_ID/and keep the required trailing slash.Follow the guided first test
import requests
session = requests.Session()
base_url = "https://www.voodoodevices.com/api/"
device_id = "E8D008:619874" # Replace with your DeviceID
response = session.post(
f"{base_url}device/{device_id}/",
headers={"API-KEY": "your-api-key"},
json={
"command": "flash",
"line1": "A-01-04",
"line2": "PICK",
"barcode": "10482",
"quantity": 3,
"arrow": "up",
"color": "blue",
"seconds": 60,
"nonce": "pick-10482-001",
},
)
response.raise_for_status()POST
Use an API User key in the API-KEY header. Treat it like a password and keep it out of browser-side code. API key details
02
Display simulator
Build the instruction.
Change any field and see the 296 × 128 display and API payload update together. Use Magnify to test scanner-ready barcodes and QR codes.
Update type
Editor
Five-field example26 characters per slot
Encoded elementsallocated after text
Command behaviordoes not consume display slots
5 / 5 requested display elements
L1line1
L2line2
L3barcode
L4quantity
L5arrow
Preview is illustrative; the image on a physical device may differ slightly.
POST device command
{
"command": "flash",
"line1": "A-01-04",
"line2": "PICK",
"barcode": "10482",
"quantity": 3,
"arrow": "up",
"color": "blue",
"seconds": 60,
"nonce": "pick-10482-001"
}Five elements maximum. Text lines, quantity, barcode, QR code, icon, and arrow each consume one of five firmware slots.
Two boxed elements maximum. Quantity 0–63, QR codes, arrows, and icons render in the left graphic area. Barcodes use the bottom strip.
Complete line encoding reference03Commands drive work.
Behavior
Commands drive work.
Statics describe state.
The fields in your request determine which path Big Block takes. After a command is acknowledged or expires, the device falls back to its persistent statics.
02Idle context
Static
Shows persistent background information without an active LED, timeout, ACK, or NACK.
- Fields
statica–statice- Lifetime
- Until explicitly changed
- Feedback
- None
Minimal battery use between tasks
Rule of thumb
LED + timeout behavior → send a command.
Information that should stick → update statics.
Compare timeouts04
Addressing
Target the right place.
Use the device directly, give it one durable location, or let one physical device represent several logical locations with automatic arrows.
DeviceID
D4F660:AFA0CBYour system owns the physical location mapping and commands the unique device identifier.
locationoverride
Zone A|A-01-04A persistent location label for a device permanently assigned to one position.
Location Alias
Cart 7|Top LeftOne device represents multiple sub-locations. Big Block can supply the matching directional arrow.
05
Closed loop
Know what happened next.
Add a unique nonce to the command. Big Block returns it in the callback so your WMS or ERP can match the physical action to the transaction that created it.
POST command
nonce: pick-10482-001Worker presses
quantity: 3POST callback
acknack: ackTypical callback
Correlate on the nonce.
Simple callbacks report acknowledgements, timeouts, and idle button calls. Use structured business callbacks when your WMS needs item, shipment, or order events.
- ack Worker acknowledged the active command
- nack Command expired before acknowledgement
- call Long press while idle and showing statics
JSON POST
{
"acknack": "ack",
"deviceid": "D4F660:AFA0CB",
"location": "A-01-04",
"nonce": "pick-10482-001",
"qty": 3
}Keep building
Documentation for the next step.
This field guide gives you the working model. Use the detailed guides and references below when you are ready to implement each part.
01
Getting Started
Hardware, Turbo setup, DeviceIDs, and your first command.
02System Overview
How devices, Turbos, Big Block, and your WMS work together.
03REST API
Endpoints, request formats, callbacks, and bulk device updates.
04Authentication
Choose an authentication method and protect your credentials.
05Line Encodings
Text, quantity, barcodes, QR codes, arrows, and hazard icons.
06Devices & Networking
Device placement, Turbo connectivity, power, and troubleshooting.
07Orders API
Upload and manage structured fulfillment work in Big Block.
08Sequence API
Coordinate reusable, multi-device execution flows.
09Server & Deployment
Compare hosted and on-premise systems and plan a rollout.