Skip to main content
Work through three checks after you install the agent or integrate an SDK: the device is connected, it’s eligible for work, and it’s earning.

1. Connected

The device has joined the network with your SDK key.
Construct the SDK with enableLogs = true, keep the app in the foreground, and watch logcat:
The device is connected once you see WebSocket ready for tasks.
Then open Analytics in the Edge Operator Portal. The Device Fleet map shows devices seen in the last 24 hours, and Unique Devices counts them over time.

2. Eligible for workloads

A connected device receives work when all of these hold:
A registration that’s “politely refused”, or a device that sits ready without tasks, is normal. Work follows network demand, and new devices get less work at first. Keep devices running, and keep their stored identity (app data, ZG_DATA_DIR, the /data volume, or the agent’s state folder): a reset device starts over as a newcomer.

3. Earning

Once a device serves its first request, it shows up in Edge Requests and Earnings on the portal’s Analytics page. See Earnings and payouts.

Platform guides

Android

Chrome Extension

Browser

Telegram Mini Apps

macOS desktop apps

Server / npm

Windows agent

macOS agent

Linux agent