> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/expert-center/id/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot.md).

# Jimi IoT

Konfigurasikan dashcam Jimi IoT JC400 dan JC261 untuk Navixy: pembaruan firmware, aktivasi SMS, aturan peringatan kejadian, optimasi lalu lintas, dan langkah pemecahan masalah.

Panduan konfigurasi dan pemecahan masalah untuk dashcam seri JC Jimi IoT, mencakup pembaruan firmware, aktivasi berbasis SMS, koneksi platform, dan pengaturan Aturan peringatan peristiwa khusus.

## Daftar isi

* [Konfigurasi dashcam Jimi IoT](/docs/expert-center/id/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-iot-dashcam-configuration.md): Pembaruan firmware, aktivasi SMS, pengaturan platform dan lalu lintas untuk perangkat JC400 dan JC261.
* [Konfigurasi peristiwa pada seri JC Jimi](/docs/expert-center/id/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/event-configuration-on-jimi-jc-series.md): Aturan peringatan peristiwa khusus menggunakan aturan nilai bidang status dan referensi kode peristiwa yang didukung.
* [Pemecahan masalah Jimi JC400](/docs/expert-center/id/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-jc400-troubleshooting.md): Mendiagnosis masalah konektivitas dan pendaftaran dengan memeriksa IMEI, status SIM, firmware, dan perintah SMS.


---

# 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://navixy.com/docs/expert-center/id/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot.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.