> 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/qna/using-navixy/my-video-device-isnt-showing-the-livestream.md).

# My video device isn't showing the livestream

Send configuration commands via Air Console to enable the livestream feature and set the correct streaming server address on the device

## Question

How do I get my video to display the livestream?

## Answer

If your device isn’t showing the livestream, the most likely case is that it’s not configured correctly. Follow the guide below for instructions. Depending on the server you’re pointing to, the commands specific to the livestream you would send to the device via the Air Console are as follows:

* COREKITSW,0
* RSERVICE, rtmp.navixy.com:1935/encoder
* VIDEORESOLUTION\_SUB,0
* SERVER,0,**{server}**,47755#

With **{server}** being the US server (13.52.37.2) or EU server (52.57.1.136) IP address.

Make sure all commands are sent *in order* as the COREKITSW,0 command is required, and the SERVER,0,**{server}**,47755# command is the required finisher command.

If your issue is due to lack of network connectivity, we recommend lowering the video quality by sending the following command to the device:

VIDEORESOLUTION\_SUB,0

## Links

* [Air Console](/docs/admin/devices/air-console.md)
* [Jimi JC400 troubleshooting](/docs/expert-center/vehicle-telematics-technology/video-telematics/configuration-guides/jimi-iot/jimi-jc400-troubleshooting.md)


---

# 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/qna/using-navixy/my-video-device-isnt-showing-the-livestream.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.