Devices

A device here is a piece of hardware Thalovant tracks from the factory onwards: a smart speaker, a mirror, a point-of-sale terminal, a box on a factory floor. Some are made by manufacturers who build on Thalovant, some are sold by Thalovant itself. Phones, browsers and the voice app aren’t devices in this sense; you add those yourself under Connections.

For each device, Thalovant keeps who made it and which model it is, which organisation owns it now, where it is (a site, such as a store or a home, and an area inside it, such as “front counter”), and which hub it talks to. A device on a hub has a connection like any other, created for it. It shows up under Connections with the device’s model and serial as its name.

Who changes what

Thalovant support makes every change to a device: registering it, handing it to its owner, putting it on a hub, moving it, taking it off for repair, and releasing it when it’s sold. Nobody in a customer organisation can do these, including the account that owns the organisation and people who sign in with their company account. That keeps a device’s history in one place and stops a former owner from reaching a device after it has moved on.

People in your organisation can see its devices and sites, with each device’s model, state, site, area and hub. They can’t edit, pause, re-pair or delete a device’s connection; those buttons answer that Thalovant manages it.

A manufacturer’s people see the units their company made, with the serial, the model and whether each one is in stock, with a customer or retired. They never see who owns a device, where it is, or which hub it uses.

Getting a device on your hub

The device’s claim code is printed on its label or in its box, in groups of five characters. Send it to support with the hub you want the device on, and the site and area if you’d like them recorded. Support checks the code, hands the device to your organisation and puts it on the hub.

The device then fetches its own connection details with a secret it got at the factory. It’s ready about a minute and a half later, the same wait as any new connection. You don’t download a connection file for it, and nobody else can.

Two kinds of hardware come with a rule:

• A device with a camera goes on a hub only after support has recorded that you agreed to it.
• A payment terminal only goes on a hub your organisation runs, never on a public hub that other people’s devices share.

Repair, replacement and resale

When a device goes for repair or gets replaced, support takes it off its hub. Its connection is deleted, the hub stops accepting it, and a live session is ended. The device stays yours. When it comes back, or when a replacement arrives, support puts it on the hub with a new connection. A unit that spent time in a workshop never comes back with credentials somebody there could have copied.

When a device is sold on or returned, it’s taken off its hub and released back to the manufacturer or the reseller. Release replaces the device’s secret and its claim code, so the old label and anything copied from the device stop working. It disappears from your organisation’s list straight away. What stays with you is your own data: memory items your organisation saved belong to your organisation, not to the device. Whoever refurbishes the device resets it and writes the new secret into it before the next owner claims it with the new code.

A device that’s lost, scrapped or suspected of being tampered with is retired. Its secret is dropped and it can’t fetch anything again.

Reading your devices through the API

An API token with clients:read can read what people in your organisation see. GET /v1/fleet/devices lists the devices of every organisation you belong to, and GET /v1/fleet/devices/{id} reads one. GET /v1/fleet/organizations lists those organisations with your role in each, and GET /v1/fleet/sites their sites.

curl -H "Authorization: Bearer $THALOVANT_TOKEN" https://api.thalovant.com/v1/fleet/devices

{
  "data": [
    {
      "id": "0f8e…",
      "serial": "SN-0001",
      "state": "deployed",
      "model": { "code": "ks-1", "name": "Kitchen Speaker", "capabilities": ["microphone", "speaker"] },
      "view": "owner",
      "site_id": "9a41…",
      "area": "Front counter",
      "hub_id": "5c2d…",
      "client_id": "77b0…"
    }
  ]
}

A device’s state is inventory (in stock with its maker or a reseller), claimed (yours, not on a hub yet), deployed, decommissioned (taken off its hub, still yours) or retired. A token limited to particular hubs only sees the devices on those hubs. A device that belongs to somebody else answers 404, the same as one that doesn’t exist.