600 - Connection closed by peer - #4 on sigfox same osmand protocol and sigfox 5055 and 5154

I try to use get and post on both but im getting the error, and when it dont show up the cordenates are wrong any idea of how to fix it ?
Captura de pantalla 2024-09-09 140114.png

Anton Tananaev3 months ago

Have you checked logs?

I've checked the data logs and when decoding the hex data on the following pages: http://sigfoxparse.suntechlatam.com/ for hex data and https://www.rapidtables.com/convert/number/hex-to-ascii.html for hex to string, the result is correct. However, the platform is not interpreting it correctly and is giving me 'sea' as the result." this is the log 4A454A sigfox 504f5354202f20485454502f312e310d0a636f6e74656e742d6c656e6774683a203231320d0a6163636570742d6c616e67756167653a2066720d0a686f73743a207369672e6770737261737472656f2e78797a3a353135340d0a636f6e74656e742d747970653a206170706c69636174696f6e2f6a736f6e0d0a6163636570742d656e636f64696e673a20677a69702c6465666c6174650d0a757365722d6167656e743a20534947464f580d0a6163636570742d636861727365743a205554462d383b713d302e392c2a3b713d302e370d0a0d0a7b0d0a20202264657669636522203a2022344134353441222c0d0a20202274696d6522203a202231373235393131383537222c0d0a2020226461746122203a2022323030323431396239356166633263363533633530343235222c0d0a2020227365714e756d62657222203a202231303730222c0d0a20202264657669636554797065496422203a2022363664363039373032656635633230326462653434633335222c0d0a2020227273736922203a20222d3132332e3030222c0d0a20202273746174696f6e22203a202236424344220d0a7d

Anton Tananaev3 months ago

I'm asking for proper unaltered logs from Traccar server.

ok, mb

2024-09-04 09:07:44  INFO: [Tfc2cb09b: sigfox < 185.110.98.2] 504f5354202f20485454502f312e310d0a636f6e74656e742d6c656e6774683a203231320d0a6163636570742d6c616e67756167653a2066720d0a686f7374>
2024-09-04 09:07:44  INFO: Event id: 4A454A, time: 2024-09-04 09:07:44, type: deviceOnline, notifications: 0
2024-09-04 09:07:44  INFO: [Tfc2cb09b] id: 4A454A, time: 2024-09-04 09:07:43, lat: -24.16146, lon: -96.01836, speed: 2.2, course: 188.0
2024-09-04 09:07:44  INFO: [Tfc2cb09b: sigfox > 185.110.98.2] 485454502f312e3120323030204f4b0d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2024-09-04 09:07:44  INFO: [Tfc2cb09b] disconnected
Anton Tananaev3 months ago

You're providing very conflicting information. In your first post you showed zero coordinates. Then you provided some "logs". Then you provided very different logs that don't match the previous one. And it also shows non-zero coordinates. I think you need to provide some proper explanation.

the info that we get from sigfox is correct, the info on the logs to, but dosent work if i want to see the device on the plataform it show diferent data

traccar screen.png

Anton Tananaev3 months ago

It probably means that what you see in the app has newer timestamp than what you see in the logs.