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

# Jimi IoT

Configure as dashcams Jimi IoT JC400 e JC261 para a Navixy: atualizações de firmware, ativação por SMS, Alertas de eventos, otimização de tráfego e etapas de solução de problemas.

Guias de configuração e solução de problemas para câmeras veiculares da série JC da Jimi IoT, abrangendo atualizações de firmware, ativação via SMS, conexão com a plataforma e configuração de alertas de eventos personalizados.

## Conteúdo

* [Configuração da câmera veicular Jimi IoT](/docs/expert-center/pt-br/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-iot-dashcam-configuration.md): Atualizações de firmware, ativação por SMS, configurações da plataforma e de tráfego para dispositivos JC400 e JC261.
* [Configuração de eventos na série JC da Jimi](/docs/expert-center/pt-br/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/event-configuration-on-jimi-jc-series.md): Alertas de eventos personalizados usando regras de valor do campo de estado e referência de códigos de eventos suportados.
* [Solução de problemas do Jimi JC400](/docs/expert-center/pt-br/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-jc400-troubleshooting.md): Diagnóstico de problemas de conectividade e registro verificando IMEI, status do cartão SIM, firmware e 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/pt-br/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.