Strange protocol behavior with amazon Reiwour device. h02, jt808, wialon

mrmrm 9 days ago

I have a Reiwour OBD2 off amazon and successfully set the APN for my simbase sim. It responds to sms commands and will reply with google maps link. So I know it's connected and gps is locked.

In my traccar server the only way it will show up in server.logs is if I use the h02 protocol. However it replies with jt808 hex. When I change the protocol for that port to jt808 it then sends replies as wialon. Setting <entry key>='wialon.port'>0</entry> doesn't help.

For example-
Set <entry key='h02.port'>5039</entry> I get:

2026-02-12 05:58:19  INFO: [Tdb06f410: h02 < 145.40.69.40] 7e0100002d01917640631800ec0000000037303131325345472d3938383847000000000000000000000036343036333138003736343036333138257e

Which is a jt808 hex code.

So I set <entry key='jt808.port'>5039</entry> I get

2026-02-12 07:30:58  INFO: [Tff85925b: wialon < 147.75.51.168] 7e0100002d01917640631800cf0000000037303131325345472d3938383847000000000000000000000036343036333138003736343036333138067e

Here's my device config if that helps anyone shed some light:
CXZT Feb 12 2026 07:01

ver:C005D7070GXM808V1020220712-GD303 id:xxxxxxxx ip:traccar.mydomain.com 5039 apn:simbase--,acc:1,sf:0gsm:4-22,gp Feb 12 2026 07:02 s:1-15,time:30-60-300,spd:0,zone:+8,obd:1,net:

Thanks!

Anton Tananaev 9 days ago