Install the Print Agent
Run the local service near the printers, approve its tenant pairing, and verify that configuration and printer discovery are healthy.
What the agent does
The Print Agent connects local printers to Chemilla Labels. It synchronizes templates and images, receives tenant-scoped jobs, renders labels to PDF, and sends them to the operating-system print queue.
Install it on a machine that stays online and can reach every printer it is expected to manage.
- The current agent runtime requires Node.js 22 for development builds.
- The desktop shell reads local status from 127.0.0.1:49200 and local logs from 127.0.0.1:49201.
- Windows runtime data is stored under C:\ProgramData\Chemilla Labels Agent by default.
Download and pair
- 1
Download the stable agent
Open Workspace > Agents and choose Latest stable agent.
- 2
Install and start it
Use the machine that can reach the intended printers. Keep the agent running while pairing.
- 3
Open the exact onboarding link
When the agent shows a link or pair code, open that exact request while signed in to Chemilla Labels.
- 4
Review the request
Select the tenant and verify hostname, platform, version, and fingerprint before approval.
- 5
Approve
Optionally name the service account, then approve. The agent can now register printers and receive jobs for the tenant.
Read agent state
| Signal | Meaning |
|---|---|
| Runtime: online | The service is currently reporting to Labels. |
| Runtime: unknown | No current runtime state is available; check the process, network, and last-seen time. |
| Active | The desired state allows the agent to work. |
| Paused | The desired state is stalled; resume it before expecting new work. |
| Config: applied | The desired runtime configuration has been acknowledged. |
| Config: pending / failed | The new settings are waiting for acknowledgement or could not be applied. |
Update runtime configuration
Choose Config on the agent row to change log level, heartbeat schedule, or printer synchronization schedule. Saving queues a desired configuration revision; the status changes when the agent acknowledges it.
More frequent schedules improve freshness but produce more synchronization traffic. Keep the default two-minute cadence unless a specific operational need justifies a change.
If printers do not appear
- Confirm the agent process is running and its runtime state is online.
- Confirm the desired state is Active and configuration is Applied.
- Check that the operating system sees the printer on the agent machine.
- Wait for the configured printer synchronization interval, then refresh Agents and Printers.
- Open the local logs page on the agent machine and inspect the latest printer-sync or print error.
- When contacting support, share the agent ID, printer name, job ID, and relevant log time window, but never send service-account secrets.