GPSLogger suddenly can't log the location properly through Cloud connection

Hi there,

i’ve setupped the GPSLogger as mentioned in the Addon-Section.
It was working two days ago.
Today it’s not.
I set the Cloud Connector to DEBUG and everytime my tracker sends a location i find in the log the following statement:

2024-06-20 21:52:23.659 [DEBUG] [io.openhabcloud.internal.CloudClient] - Got request 151919
2024-06-20 21:52:23.660 [DEBUG] [io.openhabcloud.internal.CloudClient] - Path /gpstracker/gpslogger
2024-06-20 21:52:23.660 [DEBUG] [io.openhabcloud.internal.CloudClient] - Method POST
2024-06-20 21:52:23.661 [DEBUG] [io.openhabcloud.internal.CloudClient] - Headers: {"content-length":"129","host":"home.myopenhab.org:443","content-type":"application/json","accept-encoding":"gzip","user-agent":"openhab-cloud/0.0.1"}
2024-06-20 21:52:23.661 [DEBUG] [io.openhabcloud.internal.CloudClient] - Query {}
2024-06-20 21:52:23.661 [DEBUG] [io.openhabcloud.internal.CloudClient] - Request method is POST
2024-06-20 21:52:23.662 [DEBUG] [io.openhabcloud.internal.CloudClient] - Jetty set header content-length = 129
2024-06-20 21:52:23.662 [DEBUG] [io.openhabcloud.internal.CloudClient] - Jetty set header host = home.myopenhab.org:443
2024-06-20 21:52:23.663 [DEBUG] [io.openhabcloud.internal.CloudClient] - Jetty set header content-type = application/json
2024-06-20 21:52:23.663 [DEBUG] [io.openhabcloud.internal.CloudClient] - Jetty set header accept-encoding = gzip
2024-06-20 21:52:23.664 [DEBUG] [io.openhabcloud.internal.CloudClient] - Jetty set header user-agent = openhab-cloud/0.0.1
2024-06-20 21:52:23.669 [DEBUG] [io.openhabcloud.internal.CloudClient] - onHeaders 151919
2024-06-20 21:52:23.670 [DEBUG] [io.openhabcloud.internal.CloudClient] - onResponseContent: 151919, content size 2
2024-06-20 21:52:23.671 [DEBUG] [io.openhabcloud.internal.CloudClient] - onComplete: 151919
2024-06-20 21:52:23.672 [DEBUG] [io.openhabcloud.internal.CloudClient] - Finished responding to request 151919

So the connection seems to work, but the handling seems incorrect or the query is empty?
But in the last days it was working, without any change!?

Does anyone has a similar problem or maybe a solution?

Kind regads,
Minfred