Skip to content

Voice Broadcast APP: Broadcast and Receipt Troubleshooting ​

Updated: 11/17/26, 11:11:43 AM

Work by symptom. For deployment and configuration steps see Deployment and Activation; for the message topics and acknowledgement mechanism see Design Architecture.

Activation Succeeds but No Broadcast ​

First decide whether this is a pipeline problem or a single-order problem; the APP interface and the event log show the reason for a broadcast connection failure directly, so start from the hint shown. Nine out of ten cases sit in the MQTT message pipeline:

  1. Is the platform configuration filled in: on the admin panel "Platform Configuration → MQTT Access", are the access address, account and password complete, and is the address wss://?
  2. Is the message service reachable: for a self-hosted Artemis, is 61614 open, does the outer reverse proxy forward the WebSocket upgrade header, and is the certificate valid?
  3. Subscription topic form: the topic delivered in the activation response must be the slash form daxpay/device/audio/{deviceNo}. If it is still the dot form, the device has not been re-activated or the backend is not upgraded; a dot subscription is rejected by the broker;
  4. Does the ACL allow it: does security-setting match="daxpay.device.#" grant both the amq publish permission and the app-device subscribe and queue-creation permissions?
  5. Has the configuration been delivered: after changing the MQTT access configuration, activated devices do not switch automatically; re-activate in the APP;
  6. Order source: orders from the online API and EasyPay sources are muted by design.

For the full link-by-link walkthrough see Voice Broadcast Receives No Messages.

Payment Received but No Print ​

Check in order:

CheckDescription
App switchIs "Receipt Printing" enabled for the app the device belongs to? Broadcast and printing are two independent switches
Printer connectionIs a printer enabled in the APP (tap "Enable this printer" on the print settings page), and are the connection type and the printer correct?
Paper widthDoes the APP paper width (58 / 80mm) match the paper actually used? A mismatch breaks the layout
Printer stateIs the printer out of paper, jammed, offline or switched off?
Order sourceOrders from the online API and EasyPay sources are not printed by default

The print data is rendered by the platform into an ESC/POS command stream, delivered as both a 58mm and an 80mm stream, and the APP picks the stream for the paper width. If the voice works and only the receipt is missing, check the printer and the app switch first; the message pipeline is unlikely to be the cause.

Printer Connection Drops ​

Handle by connection type:

  • Classic Bluetooth (SPP): confirm the printer is powered on and within pairing range; if needed, remove the pairing and pair again;
  • USB: unplug and replug, and confirm the phone recognizes the device;
  • Network (RAW TCP 9100): confirm the printer and phone are on the same LAN, the IP and port are correct, and the router does not isolate clients.

Print settings apply as soon as they are changed; there is no separate "Apply" button. The "Current printer" card sits at the top and shows the printer in use, and network printer details can be saved for reuse, so switching back to network printing needs no re-entry. After filling in the parameters, verify with "Test Connection", then produce a test receipt with "Test Print" in the APP; the "Test Print" entry on the admin and merchant device lists works as well. A print failure only affects the receipt; it does not affect the voice broadcast or the payment result.

QR Activation Fails ​

  1. QR content: it should be daxpay:activate:{deviceNo} and carry only the device number; if the code cannot be read, enter the device number by hand on the activation page;
  2. Is the device bound to a merchant: a device without a bound merchant cannot be activated; complete the binding and app assignment on the admin panel "Virtual Devices → Device Management" first;
  3. Does the device still belong to the current merchant: after unbinding, rebinding or deleting the merchant, the old binding no longer holds; deleting a merchant does not clean up its devices, so unbind or delete them first;
  4. Installer environment: the server address is built into the installer at compile time, and the environment the installer points at must match the platform that generated the device;
  5. Access parameters: when the platform-side MQTT access is not configured, activation may succeed but no message connection can be established; continue with the previous section.

When the activation API returns an error, the APP shows the reason directly; correct it as prompted and retry.

Asks to Re-Activate or Repeated Activation ​

ScenarioDescription
Switching to an installer for another environmentExpected, to prevent credentials mixing across environments; scan again as prompted
Re-activate on a new phone / unbindScanning again rotates the device key and kicks the old device offline
Changing the MQTT access configurationThe access address and account are delivered at activation, so activated devices must re-activate to use the new configuration
Topic contract changeThe topic in the device credential is fixed at activation; after a contract change existing devices must re-activate
Repeated decryption failuresThe APP trips a circuit breaker and guides re-activation, which means the local credential no longer matches the platform

Activating the same device again rotates the secret, and previously activated terminals stop working. Do not activate the same device number on two phones at the same time. When the platform rotates the access credentials, the APP re-activates automatically and restores the connection; a brief "reconnecting" state during that is normal and needs no manual action.

Device Drops Offline Frequently ​

  • Do not put the access domain behind a CDN; long connections are cut by short timeouts. Point it at the origin IP, or terminate HTTPS on an outer gateway that supports WebSocket;
  • Set the reverse proxy idle timeout to more than twice the client heartbeat interval, and disable proxy buffering;
  • On the phone, disable battery optimization and allow self-start and background running so the system does not kill the APP; reopening it restores listening;
  • Use the APP "Diagnostics" drawer to check background running and broadcast and printing, and copy the self-check report for records.

Online status follows the heartbeat. A short offline period followed by a reconnect is normal; for persistent drops, check in the order above.

Receipt Time Is Beijing Time ​

Outward-facing receipts always use UTC+8, independent of the timezone setting shown in the platform back office.

API Orders Are Not Announced ​

Orders from the online API and EasyPay sources target unattended cashiering; they are muted and not printed by default. This is not a device fault.