KORE-DM LwM2M Client Simulator

This simulator is a real LwM2M client — every action you take here (registering, reading or writing a resource, applying a firmware update) is the same protocol exchange a real device would have with the KORE-DM server. Working through the steps below is a hands-on way to learn how KORE-DM configures and manages devices in the field, not just how this app's buttons work.

1. Log in with the username and password you were given. Only one person can be logged in at a time — logging in from elsewhere ends this session immediately.
2. Pick an instance. The sidebar on the left lists every running instance: its number, endpoint name, registered/not-registered status, transport, and firmware version. Click one to open its console.
3. Run commands. Type a command in the box at the bottom of the console and press Enter — e.g. status, read 3/0/2, fw-update <uri>. No instance prefix needed; the console is already scoped to whichever instance you selected. Use the Status / Help buttons for one-click shortcuts.
4. Watch it work. Everything that instance logs — registration, firmware progress, errors — streams into its console live, and only into that instance's pane. Switching instances and back keeps each one's scrollback and connection intact.
5. Add or start instances. "+ Add Device" starts the first available (not currently running) instance number. "Start #" starts a specific instance number instead (handy for restarting one you stopped earlier — it picks up its original identity and saved state). "Add All" starts every not-currently-running instance number at once.
6. Stop instances. "Stop Instance" stops whichever console you currently have open. "Stop #" stops a specific instance number without needing to open its console first. "Stop All" stops every running instance.
7. Try it: set a sensor value here, read it back in KORE-DM. With this instance registered against a real KORE-DM server, run set-temp 30 in its console — that writes Object 3303 / Resource 5700 (Sensor Value) locally, exactly to 30°C, with no drift applied yet. Then, in KORE-DM's device data model dashboard, open Object 3303 and read Resource 5700 — it performs a live LwM2M Read against this device and shows the same 30°C you just set. Read it promptly: this simulator also drifts and re-pushes the temperature on its own every sensor_frequency seconds (see set-sensor-frequency, default 300s), so the exact value you set only stays put until that next automatic update.
8. Log out when you're done, from the top right.

Understanding LwM2M device management

KORE-DM manages every device the same way, whether it's this simulator or a physical device in the field — by reading and writing a standardized tree of numbered Objects and Resources over LwM2M. Getting comfortable with that model here is directly transferable:

• Every device exposes its capabilities as Objects and Resources — e.g. Object 3 is "Device", Resource 9 on it is Battery Level. This is exactly the data KORE-DM's device detail pages are built from. read 3/0/9 here reads the same value KORE-DM would.
• Registration is how a device announces itself to KORE-DM and advertises which Objects/Resources it supports. Add an instance and watch its console — that registration exchange is what makes a device appear as "online" on a real KORE-DM dashboard.
• fw-update / sw-install simulate exactly what happens when KORE-DM pushes a firmware or software campaign to a real device: it writes a package URI, executes an Update resource, and the device reports progress back through the same State/Result resources KORE-DM's campaign UI displays.
• reboot / factory-reset simulate the remote device-management actions available from KORE-DM's device actions menu on a real device.
• read / write let you directly inspect or change the Object/Resource values KORE-DM's device details page shows and edits — a low-risk way to learn LwM2M resource IDs before working against a real device.