> 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/fr/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot.md).

# Jimi IoT

Configurez les dashcams Jimi IoT JC400 et JC261 pour Navixy : mises à jour du micrologiciel, activation par SMS, alertes d'événements, optimisation du trafic et étapes de dépannage.

Guides de configuration et de dépannage pour les dashcams Jimi IoT de la série JC, couvrant les mises à jour du firmware, l’activation par SMS, la connexion à la plateforme et la configuration des alertes d’événements personnalisées.

## Table des matières

* [Configuration des dashcams Jimi IoT](/docs/expert-center/fr/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-iot-dashcam-configuration.md): Mises à jour du firmware, activation par SMS, paramètres de la plateforme et du trafic pour les appareils JC400 et JC261.
* [Configuration des événements sur la série JC de Jimi IoT](/docs/expert-center/fr/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/event-configuration-on-jimi-jc-series.md): Alertes d’événements personnalisées à l’aide de règles de valeur du champ d’état et d’une référence des codes d’événements pris en charge.
* [Dépannage du Jimi JC400](/docs/expert-center/fr/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-jc400-troubleshooting.md): Diagnostic des problèmes de connectivité et d’enregistrement en vérifiant l’IMEI, l’état de la carte SIM, le firmware et les commandes 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/fr/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.