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

# Jimi IoT

Configure las dashcams Jimi IoT JC400 y JC261 para Navixy: actualizaciones de firmware, activación por SMS, alertas de eventos, optimización del tráfico y pasos de solución de problemas.

Guías de configuración y solución de problemas para las cámaras de tablero de la serie JC de Jimi IoT, que cubren actualizaciones de firmware, activación por SMS, conexión a la plataforma y configuración de Alertas personalizadas de eventos.

## Contenido

* [Configuración de la cámara de tablero Jimi IoT](/docs/expert-center/es/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-iot-dashcam-configuration.md): Actualizaciones de firmware, activación por SMS y configuraciones de plataforma y tráfico para los dispositivos JC400 y JC261.
* [Configuración de eventos en la serie JC de Jimi](/docs/expert-center/es/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/event-configuration-on-jimi-jc-series.md): Alertas personalizadas de eventos mediante reglas de valor del campo de estado y referencia de códigos de eventos compatibles.
* [Solución de problemas de Jimi JC400](/docs/expert-center/es/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-jc400-troubleshooting.md): Diagnóstico de problemas de conectividad y registro mediante la verificación del IMEI, el estado de la SIM, el firmware y los Comandos 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/es/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.