e-bon
e-bon.ro
E-BON App

Browse and manage paired devices

Browse the fiscal printers paired at your active location, add new ones via Bluetooth or network discovery, and open the four-tab device detail screen — Overview, Operations, History, Settings — for any printer the app controls.

The Devices tab is where you manage every fiscal printer the app is controlling. It lists the devices paired at the currently selected location, lets you add new ones from the Device Discovery screen, and opens a four-tab Device Detail screen for everything per-device: status, cash balance, command history and per-device settings.

Browse paired devices

The Devices screen is split into a location header bar, a device list (or empty state) and a floating + action.

Read the location header

The top of the screen shows the active location pinned with a 📍 icon, or All locations when no location is selected. To the right is a Change action — tapping it opens the same location selector documented in Settings → Change the active location. Devices listed below this bar are filtered to the active location — devices paired at other locations are not shown until you switch.

Read the device cards

Each paired device is rendered as a card with:

  • Name (top-left) and a live status badge (top-right) showing one of Online, Busy, Warning, Error or Offline
  • A meta line: protocol · transport · location · last-seen (e.g. DatecsCompact · Bluetooth · Magazin Centru · 5m ago)
  • A Remove action on the bottom-right of the card
The list is a flat, time-ordered feed. There is no search box, no filter chips, no claimed-vs-available split, no location-grouping (the location bar already pins the view to one location), and no swipe gesture — the only way to disconnect a device from the list is the explicit Remove button on the card. To split claimed vs available devices across the whole organisation, use the Portal Devices page.

Tapping anywhere else on the card opens the Device Detail screen described below.

Remove a device from the app

Tapping Remove raises a native confirmation alert with the text Remove "<name>" from this app? This will release cloud control. and two buttons: Cancel and Remove (destructive style). Confirming both removes the device from the app and releases its cloud claim, so another app instance (or the Portal) can re-claim it. To re-add the device later, run the discovery flow again.

Remove here means unclaim and forget on this app. It does not factory-reset the printer, does not erase the fiscal memory, and does not delete the device record server-side — the device row in the Portal stays put and can be re-claimed. If you intend to remove the device from the organisation entirely, do that from the Portal Devices page afterwards.

Add a device

If no devices exist at the active location, the screen shows an empty state with the Add Device button. Once at least one device is present, the + floating action button (bottom-right) takes its place. Both routes navigate to Device Discovery.

Discover a new device

The Device Discovery screen exposes three discovery entry points stacked at the top, a scanning indicator, and a list of discovered candidates below.

Pick a discovery method

Three cards are stacked at the top:

  • Scan Bluetooth — runs a Bluetooth scan. The card disables itself while a scan is running.
  • Scan Network — runs a TCP scan of the local network. Same disable-while-scanning behaviour.
  • Manual Connection — skips discovery entirely and opens the Manual Connect flow where you enter the connection details by hand.

Wait for the scanner

While a scan is in progress, the list area shows a centred spinner with the text Scanning for devices.... Discovered devices stream into the list as they are found — there is no need to wait for the scan to complete before tapping one.

If nothing is found and the scan completes, the list shows the empty hint: Tap "Scan Bluetooth" or "Scan Network" to discover nearby fiscal printers.

Read the discovered cards

Each candidate card shows:

  • Name (top, primary) — what the device advertised over Bluetooth or what the network probe pulled back
  • A secondary line that depends on transport:
    • For Bluetooth: signal strength in dBm with a label — Excellent (≥ −50 dBm), Good (≥ −65), Fair (≥ −80) or Weak (anything lower)
    • For TCP: host:port (or just host if no port was advertised)
  • A protocol badge when discovery can suggest one: Datecs Compact, Datecs Professional, Datecs Extended, Daisy, Daisy RO, Eltrade, Incotex, Tremol, Tremol V2, MF/JE or Custom
  • A trailing identifier on the right: MAC address for Bluetooth, host for TCP, or an internal device key as a fallback

Pick a device

Tapping a card hands the discovered device off to the Device Pairing screen, which negotiates the protocol, claims the device on the server side and saves it on the app. The full pairing flow is documented in Pairing a device.

Connect a device manually

If discovery cannot see the device — VPN, segmented network, or a USB-only printer — use the Manual Connection card on Device Discovery. It opens a form where you enter a name, pick the protocol and transport, and type the host/port or Bluetooth address by hand.

The full manual-connection walkthrough is part of the pairing reference: see Pairing a device → Manual connection. It is not duplicated here.

Open device detail

Tapping any card on the Devices list opens the Device Detail screen. It has a header (back arrow, device name, live status badge, protocol · transport · location subtitle) and four tabs: Overview, Operations, Settings and History (in that left-to-right order). Tabs are state-only — switching between them does not navigate.

If the device no longer exists when you open the screen (e.g. it was removed from another tab), the screen renders Device not found with a Back to Devices button.

Check status on the Overview tab

The Overview tab is a scrollable view with three cards:

  • Device Info — a 2-column grid with the labels Protocol, Transport, Connection (formatted as host:port for TCP or the Bluetooth address), Controller (the controller name, or Unassigned), Location and Last Seen (relative time: Just now, 5m ago, 2h ago, 3d ago, or Never)
  • Cash Balance — reads the current cash balance from the device and displays it formatted as 1.234,56 RON (Romanian locale). While the read is in flight the card shows a spinner with Loading balance...; on failure it shows Could not load balance; when the device is offline the card shows Connect to device to view cash balance without contacting the printer
  • Alerts — placeholder card. Currently always shows No alerts
There is no "last command", "last receipt" or "last error" widget on the Overview tab in the current build. For the per-command outcome trail use the History tab; for receipt history use the Receipts tab.

Run commands on the Operations tab

The Operations tab hosts every one-shot fiscal command for the device — cash deposit and withdrawal, X and Z reports, duplicate prints, drawer open, set VAT, set header/footer, set operator, upload/delete logo, sync date/time. It is also where the offline guard and the destructive Z-report confirmation live.

The Operations tab is fully documented under Daily operations — every button, every confirmation, every error path. It is not duplicated here.

Review past commands on the History tab

The History tab is a list of every command this device has executed since the app was installed (or last had its data cleared). Entries are filtered to this device.

Each row renders:

  • Command type (top, primary) — translated label such as X Report, Z Report, Cash Deposit, Cash Withdrawal, Sync Date/Time, Set VAT Rates, Set Header/Footer, Set Operator, Print Duplicate or Open Drawer. Unknown command types fall back to Unknown Operation.
  • Relative timestamp — Just now, 5m ago, 3h ago, 2d ago. If the command was triggered remotely (e.g. from the Portal) the source is appended after a · (e.g. 5m ago · cloud).
  • A pill Success (green) or Failed (red) on the right.

If no commands have run yet, the screen shows an empty state with No operations yet and the hint Operations performed on this device will appear here.

The History tab does not include a date-range filter, type filter, search box, or tap-to-detail drill-down — it is a rolling chronological feed of command outcomes. Receipts are not part of this list (each receipt's command is, but the receipt itself lives under the Receipts tab). The list is held in app memory, so wiping app data clears it.

Rename or remove on the Settings tab

The Settings tab is short and only carries three cards:

  • Device Name — a text input pre-filled with the current name and a Save button. Tapping Save trims the input, rejects empty names silently, writes the new name on the app, and confirms with Device name updated.
  • Connection Info — read-only 2-column grid with Protocol, Transport and Connection (the host:port or Bluetooth address). To change any of these, remove and re-add the device.
  • Danger Zone — a single Remove Device button styled in destructive red. Tapping it raises a confirmation: Remove this device from your organization? It can be re-added later. Confirming removes the device from the app, shows Device removed, and pops back to the Devices list.
Per-device fiscal configuration that you might expect here — header/footer, operators, VAT rates, departments, logo — does not live on the Settings tab in the app. Those are command-style operations and are wired into the Operations tab instead (e.g. Set VAT Rates, Set Header/Footer, Set Operator, Upload Logo). The Settings tab in the app is intentionally narrow: rename, read connection info, remove. For organisation-wide knobs (org settings, location settings, member access to the device, audit log) use the Portal Devices page.
Remove Device on the Settings tab only removes the device from the app — it does not release the cloud claim. To both forget the device locally and release the server-side claim in one action, use the Remove button on the Devices list card.

Where to next

Open the Home tab

What loads on the Home tab when you open the E-BON Android app — the wordmark, the welcome screen for fresh installs, and the device status card after you pair a fiscal device at the active location.

Receipts tab — history, preview, print

The standalone Receipts bottom-tab in the E-BON Android app — a chronological history of every issued receipt, the per-receipt preview & print screen, and the standalone New Receipt entry point.