Device history

The History tab on a device page is the chronological audit log of every fiscal command e-bon recorded for that printer — whether it was issued from the E-BON Android app, from the Portal, or directly through the API. Open it to confirm a void receipt actually went through, to chase a printer error, or to verify your API call landed on the right device.

Open the history tab

Read the table

Each row is one fiscal command sent to this device. The table has five columns:

• Command Type — what kind of command it was (a fiscal receipt, an X report, a Z report, a void, and so on).
• Status — where the command is in its lifecycle (see colour legend below).
• Source — where the command came from (the local app, the API, the Portal, or the cloud).
• Date / Time — when the command was created, formatted in your browser's local timezone.
• Duration — how long the command took to finish, or — if it is still in flight.

Filter by command type

A dropdown in the card header lets you narrow the list to a single command type — for example, only Z reports, or only voids. The default is All types.

Selecting a type narrows the visible rows; it does not re-query the server. When you change the filter, the list jumps back to page 1.

Read the status colour

The pill in the Status column tells you where each command stands:

• Green — Completed. The command finished successfully.
• Yellow — Pending, Sent or Processing. The command is still in flight.
• Red — Failed or Timed out. The command did not complete.

Understand error codes

When a command failed or timed out, a second pill appears next to the status with the error code (for example, PRINTER_OFFLINE). The colour tells you what to do next:

• Yellow — you can safely retry the command. The failure was temporary (a connectivity blip, a busy printer, and so on).
• Red — the command failed permanently. Retrying will not help until you fix the underlying issue (paper out, wrong configuration, expired certificate, and so on).

For the catalogue of codes and their meanings, see Error codes.

Understand the duration

The Duration column shows how long the command took from creation to completion:

• Anything under one second is shown in milliseconds (for example, 420ms).
• One second or longer is shown in seconds with one decimal (for example, 1.7s).
• A command that is still in flight shows — until it completes.

Page through history

The table shows 20 rows per page. When there are more, Previous and Next buttons appear in the footer along with a page / total indicator. Paging happens entirely in your browser, so it is instant. Changing the type filter resets you to page 1.

Refresh automatically

The list refreshes automatically every 30 seconds while you stay on the tab. There is no manual refresh button — to force a fresh load before the next tick, navigate away and come back.

Where to next

• Devices — the parent list page with all your devices.
• Commands API — the REST endpoint that backs this list.
• Command types — the full reference for what each command type does.
• Error codes — the catalogue of error codes and which ones are safe to retry.
• Idempotency and retries — how to retry failed commands safely.