Device registration and connectivity

Device registration is a prerequisite for JelinaOS cloud capabilities. The registration system offers two routes, depending on the deployment environment:

Route	Environment	Method
Cloud registration	Internet connectivity with JelinaCloud access	Flash an image with configuration; the device registers automatically after boot
License registration	Disconnected / private networks / local licensing	Manual registration, LAN registration server, or offline batch licensing

Cloud registration (recommended)

For deployments with network access to JelinaCloud. Devices register automatically after connecting and typically come online within 30 seconds.

Cloud preparation in JelinaCloud

1. Create or select the device’s fleet.
2. Open the fleet, select “Add device,” choose the device type matching the hardware, and select an OS version.
3. Download the system image and device configuration file, which is unique to each device.

Note: Device type cannot be changed after selection; verify that it matches the hardware. Prefer the fleet’s default device type, or the device may be unable to follow fleet system updates.

For detailed cloud steps, see JelinaCloud device onboarding.

Device side: flashing and automatic registration

1. Select “Flash system + configuration” in JelinaFlasher to write the image and configuration file to boot media.
2. Boot the device from the medium and complete system installation.
3. Once connected, the device automatically registers with JelinaCloud using the embedded configuration, typically within 30 seconds.

After registration, verify that the device is online in the JelinaCloud device list. Open its details to view device status, running services, and logs.

Reregistration in the cloud

Registration keys are valid only once. If you delete a registered device, registering it again requires:

1. Download the configuration file or system image again.
2. Reflash the operating system.
3. Register the device again to bring it online.

License registration (disconnected / local)

For deployments without public Internet access or requiring local license management. Devices are licensed using registration codes without depending on online cloud registration.

Licensing mechanism

• Each device is licensed through a registration code bound to its unique identifier, preventing tampering and transfer.
• A device-side registration service continuously maintains registration status and issues alerts if the device remains unregistered for an extended period.
• Device type and serial number cannot be changed after registration, preserving clear management boundaries.

Manual registration

For devices without configuration embedded in the image, first use the device-side tool to set the serial number and initiate registration. Advantech provides the 32-character alphanumeric serial number:

jelina-manual-register --check       # Check registration: 0=registered / 1=unregistered / 2=registering
jelina-manual-register <serial-number>      # Set the serial number and start registration

You can also query registration status with jelina-info --get registration.status.

LAN registration

Deploy a registration server on the LAN. Devices request registration from that server to obtain their licenses, suitable for private network deployments and batch onboarding.

Offline batch registration and signing

Without a server, licensing can be completed offline:

Method	Description
Offline batch registration	Register devices in batches offline using an allowlist
Offline signing	Generate registration signatures in a connected environment and apply them to devices offline

Online synchronization

Once connectivity is restored, devices registered through the license route can synchronize license data with JelinaCloud and obtain cloud management capabilities.

Offline mode

Devices support an offline operating mode that retains cloud configuration while suspending network activity, including status reporting and update polling. It is suitable for temporary disconnections or strict isolation requirements. Query its status with:

jelina-offline --state    # Check offline-mode status

Switching offline mode affects cloud management capabilities. Do so only when needed, and ensure you understand how to restore connectivity.

Common questions

The device remains offline for a long time. Check network connectivity, verify that the correct configuration file was included during flashing, and confirm that the device type matches.

What if I selected the wrong device type? Device type cannot be changed after registration. Download the configuration again and reflash, then register using the correct device type.

How do I register devices without network access? Use the license registration route: set the serial number manually, then complete licensing through a LAN registration server or offline batch registration.

Next steps

• Fleet management and remote maintenance — Batch management and runtime policies
• Cloud application deployment and OTA — Cloud application releases
• Jelinvisor device agent — The device-side executor
• JelinaCloud device onboarding instructions