Register with Cloud
Step 4 of 5 — link the device to its entry in the dashboard so it can sync logs and receive commands.
The device now has the software and can update itself, but it isn't connected to the ByteGate Cloud Platform yet. Registration links this physical device to its entry in the dashboard, so it can upload access logs, send heartbeats, and receive remote commands.
Copy the credentials from the dashboard
In the Cloud Dashboard, go to Locations → your location → the device entry, and copy two values:
- Location ID — a UUID, e.g.
<location-id>. - Device Secret — starts with
sk_live_...(orsk_test_...for a test device).
Run the registration script
From the bytegate-edge directory on the Pi:
cd ~/bytegate-edge
source .venv/bin/activate
python scripts/register_device.pyEnter the values at the prompts
It asks for Location ID (UUID from cloud dashboard) first, then Device Secret. Paste the two values you copied. The script checks the format of both, then makes a live test heartbeat call to the Cloud API before it saves anything — if that succeeds, your credentials are written and registration is complete.
Restart the service
sudo systemctl restart bytegate-edgeThis reloads the environment so the running service picks up the new credentials.
Field tip
The Device Secret always starts with sk_live_ (production) or sk_test_ (test device) —
if you paste something else, the script warns you and asks whether to continue anyway.
The Location ID must be a valid UUID or the script rejects it immediately. Either way,
nothing is saved until the live heartbeat test against the Cloud API succeeds, so a typo in
either value surfaces here rather than as a silent sync failure later.
Last updated on