Traccar 4.2 Some device doesn't work anymore

all devices work fine in Traccar v3.17 After update to Traccar 4.2 Some device doesn't work anymore ..
Meitrack protocol devices with port 5020 Work fine But other devices with Totem protocol with port 5007 doesn't work and in the tracker-server.log HEX messages in the logs Does Not Exis !!! For test and troubleshooting change port in totem device and use port 5001 finally HEX messages in the logs Does Not Exis again !!
I cant find any solution in troubleshooting !!!
https://www.traccar.org/troubleshooting/

any idea?

Regards

If you think something got broken in the decoding logic, you need to provide HEX and corresponding protocol documentation.

For test i install traccar 4.2 in windows 10 and sent HEX Totem packet to local server:

24243031303841413836333937373033353936383030327c3138383034303030313830343238313933333239343131333030303037463834343945453036313532313730303030312e3230303030303030323933342e303539384e30353233342e3435353045353134333242

i see Log :

2018-11-15 12:04:41  INFO: [58bc0a3d: 5007 < 192.168.94.10] HEX: 24243031303841413836333937373033353936383030327c3138383034303030313830343238313933333239343131333030303037463834343945453036313532313730303030312e3230303030303030323933342e303539384e30353233342e3435353045353134333242
2018-11-15 12:04:41  INFO: [58bc0a3d: 5007 > 192.168.94.10] HEX: 2424303031344141353134333036
2018-11-15 12:04:41  INFO: [58bc0a3d] id: 863977035968002, time: 2018-04-29 00:03:29, lat: 29.56766, lon: 52.57425, course: 217.0
2018-11-15 12:04:41  INFO: [58bc0a3d] disconnected

in the local server decoding is OK

again i Sent this packet to Ubuntu online server but in log HEX messages Not Exis !! i check server and open port in server
and update server
sudo apt-get update
sudo apt-get upgrade

What is different ? why my server Not show HEX log !!??

It clearly means that server doesn't receive data from your device.

Problem solved with change IP Address in server ..
regard