Do you have the protocol of Suear?

[maginawin]

Hello!

I tested your code and I can get the device information, but I cannot get the correct video stream.

Log:

Connecting to 192.168.1.1
Device: YIPINCHENG ICB-4U01-X6-L 6.000.025  (Serial number: YIPINCHENG)
Battery: 30% (Charging)
Serving HTTP on http://0.0.0.0:45100

...

SuearUdpMsg_StreamChunk:
  unk1        : 0x2                 (2)
  n_chunk     : 0xf2                (242)
  n_frame     : 0x4d                (77)
  last_chunk  : 0x0                 (0)
  total_chunks: 0xc                 (12)
  unk5        : 0x1                 (1)
  position    : [13673, 578, 62957]
  res_width   : 0x280               (640)
  res_height  : 0x1e0               (480)
  coordinates : 0xe8                (232)

msg.coordinates=232

The unk1 always equals 0x2, is this the problem?

[SeanPesce]

Interesting; is your device intended for use with this app? If not, send me a link to the app it uses to I can look into it.

The unk1 field is not used in my code because I didn't take the time to figure out what it's used for ("unk" is short for "unknown"), but the discrepancy might be related to why this isn't working for you.

If your device uses the app that I linked above, I'll have to do some more reversing to figure out how the behavior can differ. I might also need you to send me a packet capture so observe what the traffic looks like.

Edit: And to answer your original question, yes - you can see the definitions of some protocol messages here (note, however, that not all message types are supported).

[maginawin]

Hi,

I removed assert msg.unk1 == 1, f'{msg.unk1=}' in the suear_mirror.py and then it's working. Thank you very much!

Now I have a new problem, how to convert the coordinates to X Y Z or to Rotate Angle? May I have the protocol of the coordinates?

Best regards.

[SeanPesce]

Oops, sorry about that assert statement; that was some debug code I accidentally left in there. Nice work figuring that out though! I updated the repo to remove that line of code.

As for the coordinates, I didn't take the time to reverse engineer how they get parsed. It might not be too hard though; I'll try to take another look when I have the time.