JC181 by Jimi IoT in Traccar: Dual-Channel Dashcam, Field-Tested in Production

Of every camera in Jimi IoT's JC series, the JC181 is the one we've put to work on a production Traccar server. This article is the result of that test: what works, what doesn't, and what you need to be clear on before buying it for a fleet.

If you're starting from zero, read how camera support works in Traccar first. Here I'll go straight to the model.

What the JC181 is

It's a compact dual-channel video telematics device, built for light vehicles: taxis, urban delivery, light commercial fleets. It combines a camera, LTE connectivity, and GNSS in a single unit, and records locally in addition to reporting to the server.

The manufacturer's sales pitch is remote management: watch live video, play back historical recordings, and retrieve evidence from anywhere. That's true on the manufacturer's own platform. With Traccar the story has important nuances, and they're exactly the ones nobody tells you.

How Traccar sees it: the JT808 protocol

This is the part that decides everything else. The JC181 enters Traccar through the JT/T808 protocol, not through the classic Concox/GT06 protocol or Jimi's HTTP handler.

This isn't a guess: Traccar's JT808 decoder has an explicit set of Jimi models it handles with dedicated logic, and the JC181 is in there, alongside the JC371, JC182, JC450, and JC451.

The practical consequence, in two lines:

• ✅ Live video: yes.
• ❌ Video files saved on your server: no (with unmodified Traccar).

Live video works (and here's how)

Traccar implemented the JT/T 1078 video streaming standard in April 2026 — there's a dedicated pipeline in the server for it. If you searched this topic on the forum and found threads saying "JT1078 streaming isn't supported," they're outdated: they predate that date.

The mechanism, in short: when you fire videoStart, Traccar sends the camera a JT808 0x9101 message telling it which host and port to connect to, which channel to stream, and at what quality. The camera then opens a new session against the server's JT1078 port, and Traccar acts as a relay. The videoStop command corresponds to message 0x9102.

You confirm it in the log like this:

grep -i "jt1078" /opt/traccar/logs/tracker-server.log

If a jt1078 < CAMERA_IP line shows up after videoStart, the camera obeyed. That's your first checkpoint.

The mistake you're going to make

In our test, video kept cutting out constantly. The two causes:

1. The vehicle in motion. At 4–20 km/h, every handoff between 3G/4G cells knocked out the stream. There's no configuration that fixes that.
2. Insisting. Not seeing an image right away, the operator would press the button again. Every new videoStart forces the camera to cancel the ongoing session and renegotiate the TCP socket, so with rapid retries the stream never gets to stabilize.

Wait 10 to 15 seconds after requesting video before touching anything else. And in poor coverage, use the sub-stream instead of the main stream. Full details are in JT1078 live video.

Files aren't saved on the server

We looked. On a server with media.path configured:

find /opt/traccar/media -type f \( -name "*.mp4" -o -name "*.h264" -o -name "*.ts" \)

Zero results. There were only device.jpg images, which are device profile pictures and have nothing to do with the camera.

With the JC181 on Traccar, historical video lives on the unit's microSD, inside the vehicle. Traccar is a live relay, not a recorder.

Now, the honest nuance: this isn't an architecture limitation, it's a gap in the JT808 decoder, which doesn't invoke the media storage system that Traccar already has and that other protocols do use. It's implementable — we have it solved on our own server with that modification. But out of the box you don't have it.

Translation for your purchasing decision: if you need video evidence that survives the vehicle burning down or someone pulling the card, you need additional development or the manufacturer's platform. Don't find that out after buying fifty units.

Setup checklist

1. Verify the LTE bands with your distributor before buying. It's the most expensive and the dumbest mistake to make.
2. Register the device in Traccar with its unique identifier (IMEI).
3. Open the JT808 protocol port and also the JT1078 port in the firewall. If you only open the first one, you'll get positions but never video, and you'll waste an afternoon looking in the wrong place.
4. Confirm positions are coming in before touching anything video-related.
5. Test video with the vehicle parked. If that's fine and it fails while moving, it's coverage.
6. If you're expecting notifications, configure them: a notifications: 0 in the log means the event was processed but there's no rule attached to it, not that the camera is failing.

Is this the right camera?

Yes, if you want live visibility on a light fleet, with dual channel (road + cabin) and a single unit that already includes GPS. It's compact, it works, and with Traccar you get positions and live video.

No, if your requirement is centralized video storage on your own server without writing code. That's where out-of-the-box JT808 falls short.

For heavy fleets, multi-camera setups, or a need for ADAS/DSM, the JC450 is the next step within the same JT808 family. For the full picture of what's supported across models, see Traccar-compatible cameras.