3rd Party Trackers Disconnect When Official Slime with Firmware v.6.2 or later connect

[ZRock35]

3rd party ESP based Slimes (Somatic and Gorbitslimes tested) which are connected to the SlimeVR server suddenly disconnect when an official tracker running anything with 0.6.2 firmware or later connect to the SlimeVR server.

Tested with 0.3.3 up to 0.5.4 and no problems were found. 0.6.2 up through 0.7.2 produce the issue.

[unlogisch04]

As it was already pointed out in Discord.
The behavior happens only on ESP32 (ESP-IDF) and not on ESP8266.
The "reason" for that to happen is, the firmware from v0.6.2 has this line added which are send with the broadcast packet.
https://github.com/SlimeVR/SlimeVR-Tracker-ESP/blame/main/src/network/connection.cpp#L382-L391
The SlimeVR Server code does currently not look at this values https://github.com/SlimeVR/SlimeVR-Server/blob/main/server/core/src/main/java/dev/slimevr/tracking/trackers/udp/UDPPacket.kt#L95-L139 )

The reason the code on esp32 looks up is a different behavior of the UDP.parsePacket() or UDP.read()
https://github.com/SlimeVR/SlimeVR-Tracker-ESP/blob/main/src/network/connection.cpp#L662-L667
On Arduino ESP8266:

• parsePacket will return all bytes (or 0 if no bytes to read)
• read will copy the size of the buffer and discarde all not read bytes

On Arduino ESP32:

• parsePacket will return also all bytes of the packet, but will also return 0 if there are still unread bytes from the previous packet.
• read will copy the size of the buffer and stores the not read bytes in the queue.

There are 2 problems:

1. "DOS" to tracker (making it stuck till reboot)
2. Backwards compatibility (new firmware version "DOS" the old firmware version tracker)

Possible solutions:

1. Fix the handling for esp32 (check if still available, then discard)
2. Is probably harder to fix properly
   Idea 1:
   Revert the change of the broadcast packet. It is currently not used and crashes the old trackers.
   Implement a new packet for the additional Information provided in that update.
   As the firmware 0.6.2-0.7.2 are out there will be possible problems that probably cant be fixed.
   Idea 2:
   A compatibility mode the tracker can be switched too over Serial so it does not send the long broadcasts.
   Idea 3:
   Ideas are welcome ^^;