> For the complete documentation index, see [llms.txt](https://docs.kpnthings.com/kpn-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kpnthings.com/kpn-things/building-blocks/devices/sensors/generic-device-internet-connected.md).

# Generic Device (Internet connected)

<div align="center"><img src="https://portal.kpnthings.com/assets/images/device-types/own-internet.png" alt="Generic Device (Internet connected)"></div>

Connect your (virtual) Internet-connected device to KPN Things.

* Supported network type(s): `INTERNET`
* Device Specification ID: `own-internet`
* Device Specification UUID: `b2c5c303-4f74-4b58-95f5-b80455fdafbc`

| Decoders                                   | decoderSpecificationUUID               | Description                                                                        |
| ------------------------------------------ | -------------------------------------- | ---------------------------------------------------------------------------------- |
| › Decoded ThingsML and raw SenML data (v2) | `4a8f1ec7-df52-5a57-a281-422e000d3b1d` | Decoder that forwards raw SenML data and decoded ThingsML data sent by the device. |

| Encoders     | encoderSpecificationUUID               | Description                     |
| ------------ | -------------------------------------- | ------------------------------- |
| = SenML data | `86805e45-c394-4ebc-a2e1-a47079a57999` | Send SenML data to your device. |

### › Decoded ThingsML and raw SenML data (v2)

Decoder that forwards raw SenML data and decoded ThingsML data sent by the device.

#### Example SenML

This is completely dependent on the SenML or ThingsML input and could output almost any SenML. The decoded ThingsML below is just illustrative of what is possible.

```json
[
    {
        "bn": "urn:dev:DEVEUI:fe782a953c642aeb:",
        "bt": 1693136532.83,
        "n": "latitude",
        "u": "lat",
        "v": 51.90717
    },
    {
        "n": "longitude",
        "u": "lon",
        "v": 4.48940
    },
    {
        "n": "temperature",
        "u": "Cel",
        "v": 29.75
    },
    {
        "n": "batteryVoltage",
        "u": "V",
        "v": 3.59
    },
    {
        "n": "extTemp",
        "u": "Cel",
        "v": 17.22
    },
    {
        "n": "io",
        "vb": false
    }
]
```

### = SenML data encoding

* Protocol: HTTP response
* Description: Send SenML data to your device.
* Multiple commands in one downlink: No
* No input mapping


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kpnthings.com/kpn-things/building-blocks/devices/sensors/generic-device-internet-connected.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
