Skip to main content
Chrome on HTTPS cannot send ESC/POS bytes to a printer by itself. If the tablet has no local bridge, the cook bumps the ticket and nothing prints — the guest waits at the counter with no slip. This page is for the person who sets up Fire Agent Android (Agent 1.0.1, package com.firepos.fireagent) on the KDS tablet. Windows PCs still use Windows installation.
The minimum you need to know
  • Two independent chains: KDS ↔ agent (DNS + WSS + token) and agent ↔ printer (LAN TCP, usually port 9100).
  • The printer name you save in the app is the name you pick in fire-kds. They must match exactly.
  • On HTTPS kitchens, kds-agent.fire.rest must resolve to 127.0.0.1 on that tablet. If DNS sends it to the internet, print never starts.

​
The simple path

1

Install the APK

Install Agente-1.0.1.apk on the tablet. Open the app and set Language to English if you follow this page’s labels.
2

Start the agent

On Home, tap Start agent. The badge must read LIVE. Allow notifications if Android asks (needed for the foreground service).
3

Add the printer

Open Printers. Enter Name in KDS, IP address, and TCP port (usually 9100). Tap Save printer, then Test print.
4

Arm the same name in KDS

In fire-kds, open Printer for this screen and pick that exact name. Enable store Print on bump so a bump actually sends paper. See Peripherals, printing and validation.
Fire Agent Android Home tab with the agent stopped and Start agent
Fire Agent Android Home tab LIVE with ws and wss status line
If Test print already comes out of the kitchen printer and KDS shows the agent online, you can stop here.

​
Home, Diagnostics, Printers, Settings

Fire Agent Android Diagnostics with KDS and printers all good
Fire Agent Android Printers tab with a saved LAN printer and Test print
Fire Agent Android Settings with Auth token and WebSocket port
The agent listens only on 127.0.0.1. fire-kds on Android tries wss://kds-agent.fire.rest:9101 first, then the Windows URL if that connect fails. See Agent web tools.

​
Recipes

  1. Start the agent until LIVE.
  2. Save one printer named Kitchen at the printer’s LAN IP, port 9100.
  3. Test print.
  4. In fire-kds pick Kitchen and enable Print on bump.
  1. Stay on Diagnostics → KDS.
  2. If DNS fails, IT must point kds-agent.fire.rest to 127.0.0.1 on this tablet.
  3. If the token step fails, match Auth token to NEXT_PUBLIC_FIRE_AGENT_TOKEN in fire-kds.
  4. Do not change the printer — Part 2 is already healthy.
  1. Confirm the printer is on the same Wi‑Fi / VLAN.
  2. Recheck IP and port 9100 (some devices use 9102).
  3. Run Test print from the Printers tab.
  4. KDS can connect and still print nothing if TCP to the printer fails.
  1. Open Settings → Advanced: KDS connection.
  2. Paste the new Auth token.
  3. Save settings (the agent restarts if it was LIVE).
  4. Update the same token in the fire-kds deploy for that tablet.

​
Worked example

​
Errors that cost money

Public DNS for kds-agent.fire.rest. The browser must talk to the agent on this tablet. If the name leaves the device, fiscal and comanda slips never print and the bump still looks successful.
Token mismatch. Auth token must equal fire-kds NEXT_PUBLIC_FIRE_AGENT_TOKEN. Otherwise KDS shows the agent offline or Unauthorized.
Name in the agent ≠ name in KDS. The store rule can be correct and still print nothing. Use the same string, including spaces and accents.
Printer on another network. The agent sends TCP RAW to the IP you typed. A guest Wi‑Fi or a blocked VLAN looks like a dead printer.

​
Glossary

​
FAQ

No. Windows uses the Windows installer. This APK is only for the Android KDS device.
No. You install the app, start it, and register printers. Pairing codes are for kitchen devices in fire-kds, not for this agent.
9100 is plain WS. 9101 is WSS with the shipped certificate so HTTPS KDS can connect. The printer’s own port is usually also 9100 — that is a different hop.
Yes by default, after the app was opened at least once after install (Android 12+). If Home shows OFF, tap Start agent.

​
What this page does not do

  • It does not choose Comanda vs Fiscal — that is store Print on bump.
  • It does not replace Fire credentials for fiscal data. The agent only moves bytes to paper.
  • It does not expose a public print API. Traffic stays on 127.0.0.1.