Huabao (808) Protocol – 0704 (Location Batch Processing) platform's universal response issue
| Starting Byte | Field | Data Type | Description and Requirements |
|---|---|---|---|
| 0 | Response Serial Number | WORD | Corresponding Terminal Message Serial Number |
| 2 | Response ID | WORD | Corresponding Terminal Message ID |
| 4 | Result | BYTE | 0: Success/Confirmation; 1: Failure; 2: Message Error; 3: Not Supported; 4: Alarm Processing Confirmation; |
Let's see the documentation and logs.
This is the official documentation link, and this is the log (I have omitted some information about the ID number):
2025-12-10 00:01:59 INFO: [T970a9fa6: huabao < 127.0.0.1] 7e0102000c04--------03060e303432323832393030393033347e
2025-12-10 00:01:59 INFO: [T970a9fa6: huabao > 127.0.0.1] 7e8001000504--------030000060e010200b17e
2025-12-10 00:01:59 INFO: Event id: 04--------03, time: 2025-12-10 00:01:59, type: deviceOnline, notifications: 1
2025-12-10 00:02:00 INFO: [T970a9fa6: huabao < 127.0.0.1] 7e0704004d04--------03060f0001010048000020000008000301e6b52e0701683f002302f10040251207190952140400000000170200000104000021542504000000002a02000030011a31010fea04020c8300ef0400000000357e
2025-12-10 00:02:00 INFO: [T970a9fa6: huabao > 127.0.0.1] 7e8001000504--------030000060f070400b07e
So what is the problem with the response?
I'm really sorry, I think I've found the problem. The AI tells me it might be due to a reverse proxy. Thank you.
Hello, I've discovered a problem with the Huabao (808) protocol decoder when processing 0x0704 messages (batch location upload). The issue may lie in the platform's universal response (0x8001) format. The device might not receive the correct response and therefore won't send subsequent 0x0200 data, resulting in the continuous sending of 0x0704 messages, which cannot be parsed on the webpage. I've translated part of the official documentation for your reference:
8.2 Platform General Response
Message ID: 0x8001.
The platform general response message body data format is shown in Table 5
Table 5 Platform General Response Message Body Data Format
Starting Byte Field Data Type Description and Requirements
0 Response Serial Number WORD Corresponding Terminal Message Serial Number
2 Response ID WORD Corresponding Terminal Message ID
4 Result BYTE 0: Success/Confirmation; 1: Failure; 2: Message Error; 3: Not Supported;
4: Alarm Processing Confirmation;
Thanks!