# DeviceLookup

<!-- https://uncage.vercel.app/docs/api/react/interfaces/devicelookup/ -->

Defined in: client/dist/index.d.ts:63

`lookupDevice`: what the approve screen shows about a pending code (same shape as the hub's `lookupDevice`).

## Properties

| Property | Type | Description | Defined in |
| ------ | ------ | ------ | ------ |
| <a id="property-expiresat"></a> `expiresAt` | `string` | - | client/dist/index.d.ts:66 |
| <a id="property-name"></a> `name?` | `string` | - | client/dist/index.d.ts:64 |
| <a id="property-os"></a> `os?` | `string` | - | client/dist/index.d.ts:65 |
| <a id="property-repairsmachine"></a> `repairsMachine` | \| \{ `id`: `string`; `name`: `string`; \} \| `null` | Set when approving would re-pair this existing computer instead of adding one. | client/dist/index.d.ts:72 |
| <a id="property-requestedat"></a> `requestedAt?` | `string` | When `uncage setup` asked for the code (ISO). Hubs before 0.4.1 leave it out. | client/dist/index.d.ts:68 |
| <a id="property-requestip"></a> `requestIp?` | `string` \| `null` | The requesting computer's IP as the hub saw it; `null` = unknown. Hubs before 0.4.1 leave it out. | client/dist/index.d.ts:70 |
