Traccar Upgrade from 5.6 -> 5.9 Issue

After upgrading from 5.6 to either 5.7 - 5.8 - 5.9

I have this issues with my devices - devices is a mix of OSMAND - H02 -GT06

The log is showing this:

2023-10-04 11:47:36  INFO: [T4d45799a] disconnected
2023-10-04 11:47:37  INFO: [T773e5b55] connected
2023-10-04 11:47:37  INFO: [T773e5b55: osmand < *.*.*.*] 504f5354202f3f69643d3639343034392674696d657374616d703d31363936343132393933266c61743d35372e30393232323237266c6f6e3d392e3532353539352673706565643d302e302662656172696e673d302e3026616c7469747564653d35312e352661636375726163793d3130302e3026626174743d35312e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f69642031333b20534d2d4e39383642204275696c642f545031412e3232303632342e303134290d0a486f73743a2038372e35312e362e3137383a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a

I have been searching for the sollution and I have tried to disable the geocoding as suggested elsewhere .
If I revert back to 5.6 the problem is gone.

Best Nanna

I don't see any issues in your log.

In version 5.6 I get a valid decode on all 3 device protocols, after the opdate tried 5.7 5.8 and 5.9. It looks like it's not decoding and I don't get a valid lat, lon, altitude and speed.
And all my devices Osmand, H02 and gt06 stays offline.

Reverting back to 5.6 it works again

If you need some help, you would have to provide some evidence.

This is the log from version 5.9 narrowed down to one Osmand device:

2023-10-04 11:47:26  INFO: [T3296fc37] connected
2023-10-04 11:47:26  INFO: [T3296fc37: osmand < 80.62.*.*] 504f5354202f3f69643d3639343034392674696d657374616d703d31363734353337373630266c61743d35372e30393230393337266c6f6e3d392e353235353637362673706565643d302e30353235323232353535383839313134372662656172696e673d302e3026616c7469747564653d35302e3430303030313532353837383930362661636375726163793d382e30373630303032313336323330343726626174743d38312e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f69642031333b20534d2d4e39383642204275696c642f545031412e3232303632342e303134290d0a486f73743a2038372e35312e362e3137383a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2023-10-04 11:47:28  INFO: [T3296fc37] error - MessageBodyReader not found for media type=text/plain;charset=utf-8, type=interface jakarta.json.JsonObject, genericType=interface jakarta.json.JsonObject. - MessageBodyProviderNotFoundException (... < NotificatorTraccar:106 < NotificationManager:110 < ... < *:107 < ... < *:106 < *:148 < ConnectionManager:247 < ...)
2023-10-04 11:47:28  INFO: [T3296fc37] disconnected
2023-10-04 11:47:28  INFO: [Tef44876e] connected
2023-10-04 11:47:28  INFO: [Tef44876e: osmand < 80.62.*.*] 504f5354202f3f69643d3639343034392674696d657374616d703d31363936343132393832266c61743d35372e30393232323237266c6f6e3d392e3532353539352673706565643d302e302662656172696e673d302e3026616c7469747564653d35312e352661636375726163793d3130302e3026626174743d35312e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f69642031333b20534d2d4e39383642204275696c642f545031412e3232303632342e303134290d0a486f73743a2038372e35312e362e3137383a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2023-10-04 11:47:28  INFO: [Tef44876e] error - MessageBodyReader not found for media type=text/plain;charset=utf-8, type=interface jakarta.json.JsonObject, genericType=interface jakarta.json.JsonObject. - MessageBodyProviderNotFoundException (... < NotificatorTraccar:106 < NotificationManager:110 < ... < *:107 < ... < *:106 < *:148 < ConnectionManager:247 < ...)

And the same Osmand device in version 5.6

2023-10-20 07:11:49  INFO: [Tdc48b814: osmand > 87.49.*.*] 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2023-10-20 07:11:49  WARN: Position forwarding failed: 0 pending - HTTP code 405 - RuntimeException (PositionForwarderUrl:74 < *:67 < ...)
2023-10-20 07:11:49  INFO: [Tdc48b814] id: 694049, time: 2023-10-20 07:11:50, lat: 57.10083, lon: 9.53101, speed: 7.7, course: 104.8, accuracy: 128.0
2023-10-20 07:11:50  INFO: [Tdc48b814: osmand < 87.49.*.*] 504f5354202f3f69643d3639343034392674696d657374616d703d31363937373738373131266c61743d35372e31303038303935266c6f6e3d392e353331313535362673706565643d31302e3535373032373431323139333239382662656172696e673d3130342e3737373436353832303331323526616c7469747564653d34332e3930303030313532353837383930362661636375726163793d3133342e323936303035323439303233343426626174743d38312e3020485454502f312e310d0a436f6e74656e742d547970653a206170706c69636174696f6e2f782d7777772d666f726d2d75726c656e636f6465640d0a557365722d4167656e743a2044616c76696b2f322e312e3020284c696e75783b20553b20416e64726f69642031333b20534d2d4e39383642204275696c642f545031412e3232303632342e303134290d0a486f73743a2038372e35312e362e3137383a353035350d0a436f6e6e656374696f6e3a204b6565702d416c6976650d0a4163636570742d456e636f64696e673a20677a69700d0a436f6e74656e742d4c656e6774683a20300d0a0d0a
2023-10-20 07:11:50  INFO: [Tdc48b814: osmand > 87.49.*.*] 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2023-10-20 07:11:50  WARN: Position forwarding failed: 0 pending - HTTP code 405 - RuntimeException (PositionForwarderUrl:74 < *:67 < ...)
2023-10-20 07:11:50  INFO: [Tdc48b814] id: 694049, time: 2023-10-20 07:11:51, lat: 57.10081, lon: 9.53116, speed: 10.6, course: 104.8, accuracy: 134.3
2023-10-20 07:11:51  INFO: [Tdc48b814: osmand < 87.49.*.*] 

You have some issue with push notifications. Try disabling them.

Thanks Anton - it worked

What specific in the log led you to that conclusion?

You error message says where the error is coming from.