> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/connectors/mioty-connector.md).
# MIOTY Connector
Bring MIOTY devices into Kilo Cloud — enterprise service-center networking with dashboards, widgets, automation rules, and alarms.
The MIOTY connector brings your radio network into **Kilo Cloud's full IoT platform**. Kilo Cloud includes the enterprise Kilo Center service center; your MIOTY endpoint readings can then feed widgets and dashboards, take part in automation rules, and raise alarms with escalation.
MIOTY is a low-power wireless protocol. Its **base stations** are radio gateways, and its **endpoints** are communicating sensors or devices. The connector is the software connection between that network and your Kilo organization. Add it, connect your base stations, and register the endpoints to build the application around their readings.
Kilo Center comes three ways. If you only need networking and want to run it yourself, [Kilo Center Community Edition](/kilo-mioty-service-center.md) is the free, open-source service center, provided as is. If the network must stay on your own infrastructure with commercial support, Kilo licenses and installs the Enterprise edition on your premises. Use Kilo Cloud when you want the Enterprise service center run for you, together with the platform's application capabilities.
For the wireless protocol, see [What is MIOTY?](/connectors/mioty-connector/what-is-mioty.md). For operating your own service center, see [Kilo MIOTY Service Center](/kilo-mioty-service-center.md).
## Why the connector exists
MIOTY endpoints do not reach the network the way LoRaWAN devices do. There is no packet-forwarding gateway in the path. Endpoints transmit to **base stations**, and each base station holds a persistent, certificate-secured (mTLS) session to a service center using **BSSCI** — the Base Station Service Center Interface, the standard control protocol between the two.
That session has to terminate somewhere specific to you. The Mioty connector is what creates your organization's endpoint on the service center: when you add it, the server provisions a **BSSCI address** that your base stations connect to. Everything downstream — station identity, certificate issuance, endpoint attachment, telemetry — flows through that address.
Without a Mioty connector, the MIOTY surface is simply not there. The **Mioty Base Stations** tab does not appear on the Gateways page, and the MIOTY fields on the device form are unavailable with the message **"Create a Mioty connector first"**.
## Adding the Mioty connector
1. Navigate to **Connectors** in the sidebar.
2. Click **Add connector**.
3. In the **Connector type** dropdown, select **Mioty**.
4. Click **Add**.
The connector is created immediately and appears in the connectors table with its BSSCI endpoint address provisioned for your organization. No further configuration is required at the connector level — the work of pairing hardware happens at base station registration, where each station gets its own certificate bundle.
## What the connector unlocks
Once the Mioty connector exists, two parts of the server become available:
| Surface | Where | What you do there |
| --------------------------- | ------------- | --------------------------------------------------------------------------------- |
| **Mioty Base Stations** tab | Gateways page | Register base stations, download their certificates, monitor status and last-seen |
| MIOTY device fields | Device form | Enter the End Point EUI, network parameters, and security keys for each endpoint |
The BSSCI address is what you hand to the base station hardware, alongside the certificate pair it downloads during registration. You will see it again on each station's Overview and Settings — copying it from a station's detail page is usually more convenient than copying it from the connector, because that is where the matching certificates live.
## Planning your MIOTY deployment
* **Base stations first, endpoints second.** An endpoint has nowhere to attach until at least one base station is registered and online. Register the station, confirm it comes up, then commission endpoints against it.
* **Collect endpoint credentials before you commission.** Each endpoint needs its End Point EUI and Network Session Key. These come from the manufacturer, usually on a label or in a shipped provisioning file, and they are far easier to capture at the bench than on a pole.
* **Decide your blueprint strategy early.** MIOTY telemetry stays undecoded until a blueprint is bound to the device. If you are rolling out a few hundred units of one model, author or select the blueprint once and reuse it across the fleet.
* **Scale with base stations, not connectors.** A multi-site MIOTY deployment grows by adding base stations under your organization's BSSCI endpoint — coverage and density are a radio-infrastructure question, not a connector question.
## What's next
* **Register base stations** — bring your MIOTY radio infrastructure online with its BSSCI address and certificates. See [MIOTY base stations](/gateways/mioty-base-stations.md).
* **Commission endpoints** — enter EUIs, network parameters, and session keys for each MIOTY sensor. See [MIOTY Devices](/devices/mioty-devices.md).
* **Decode payloads** — bind a blueprint so raw endpoint telemetry becomes named, normalized measurements. See [MIOTY Blueprints](/devices/mioty-blueprints.md).
## MIOTY Reference
If you are still deciding whether MIOTY is the right radio for a site, these pages cover the protocol itself rather than the connector. Read them in order — each one hands off to the next:
* [What is MIOTY?](/connectors/mioty-connector/what-is-mioty.md) — Telegram splitting, base stations, and what ETSI TS 103 357 actually specifies
* [Core Benefits of MIOTY](/connectors/mioty-connector/core-benefits-of-mioty.md) — Interference resistance, endpoint density, range, power, and mobility
* [Ideal Use Cases for MIOTY](/connectors/mioty-connector/ideal-use-cases-for-mioty.md) — Plant floors, metering rollouts, moving assets, and rotating machinery
* [Why Choose MIOTY?](/connectors/mioty-connector/why-choose-mioty.md) — How MIOTY and LoRaWAN differ, and which constraints should decide between them
---
# 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.kiloiot.io/connectors/mioty-connector.md?ask=&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.
