Port 5013 should be correct one. Unfortunately you filtered your log file, so it's impossible to say what the problem is.
Sorry,I’ve got a several devices running on my system and I tried to only pick out the errors I was seeing. How much more log file data do you need?
Include full connection session for one of the devices. Don't remove any extra logs in between.
If it's big, don't post it here directly. Upload file somewhere.
Hi Anton,
I hope this helps, if not I can copy in some more.
2018-11-01 09:36:42 INFO: [ad90fe79] connected
2018-11-01 09:36:42 DEBUG: [ad90fe79: 5013 < 185.69.144.33] HEX: 2a48512c383137303836373730332c56312c3039333634302c412c353132382e323136302c4e2c30303030372e393335352c572c3030302e39322c3030302c3031313131382c46464646424246462c3233342c31352c30303133392c323038303823
2018-11-01 09:36:42 DEBUG: [ad90fe79: 5013 > 185.69.144.33] HEX: 2a48512c383137303836373730332c56342c56312c323031383131303130393336343223
2018-11-01 09:36:42 INFO: [ad90fe79] id: 8170867703, time: 2018-11-01 09:36:40, lat: xx.xxxxx, lon: -x.xxxxx, speed: 0.9, course: 0.0
2018-11-01 09:36:53 DEBUG: [a571af35: 5013 < 85.255.236.4] HEX: 24617097022709365001111851282147060000793366000000ffffbbff000000000000000000ea0f008b51482c
2018-11-01 09:36:53 INFO: [a571af35] id: 6170970227, time: 2018-11-01 09:36:50, lat: xx.xxxxx, lon: -x.xxxxx, course: 0.0
2018-11-01 09:37:12 DEBUG: [ad90fe79: 5013 < 185.69.144.33] HEX: 2a48512c383137303836373730332c56312c3039333730392c412c353132382e323135312c4e2c30303030372e393237362c572c3030302e34352c3030302c3031313131382c46464646424246462c3233342c31352c30303133392c323038303823
2018-11-01 09:37:12 DEBUG: [ad90fe79: 5013 > 185.69.144.33] HEX: 2a48512c383137303836373730332c56342c56312c323031383131303130393337313223
2018-11-01 09:37:12 INFO: [ad90fe79] id: 8170867703, time: 2018-11-01 09:37:09, lat: xx.xxxxx, lon: -x.xxxxx, speed: 0.5, course: 0.0
2018-11-01 09:37:12 DEBUG: [e57f770d: 5001 < 82.132.239.246] HEX: 3836333037303031393232383338353b
2018-11-01 09:37:12 DEBUG: [e57f770d: 5001 > 82.132.239.246] HEX: 4f4e
2018-11-01 09:37:12 DEBUG: [a571af35: 5013 < 85.255.236.4] HEX: 24617097022709371001111851282139060000793726000000ffffbbff000000000000000000ea0f008b51482d
2018-11-01 09:37:12 INFO: [a571af35] id: 6170970227, time: 2018-11-01 09:37:10, lat: xx.xxxxx, lon: -x.xxxxx, course: 0.0
2018-11-01 09:37:32 DEBUG: [a571af35: 5013 < 85.255.236.4] HEX: 24617097022709373001111851282177060000794526000000ffffbbff000000000000000000ea0f008b51482e
2018-11-01 09:37:32 INFO: [a571af35] id: 6170970227, time: 2018-11-01 09:37:30, lat: xx.xxxxx, lon: -x.xxxxx, course: 0.0
2018-11-01 09:37:41 DEBUG: [ad90fe79: 5013 < 185.69.144.33] HEX: 2a48512c383137303836373730332c56312c3039333733392c412c353132382e323132352c4e2c30303030372e393239322c572c3030302e34312c3030302c3031313131382c46464646424246462c3233342c31352c30303133392c323038303823
2018-11-01 09:37:41 DEBUG: [ad90fe79: 5013 > 185.69.144.33] HEX: 2a48512c383137303836373730332c56342c56312c323031383131303130393337343123
2018-11-01 09:37:41 INFO: [ad90fe79] id: 8170867703, time: 2018-11-01 09:37:39, lat: xx.xxxxx, lon: -x.xxxxx, speed: 0.4, course: 0.0
2018-11-01 09:37:52 DEBUG: [a571af35: 5013 < 85.255.236.4] HEX: 24617097022709375001111851282164060000795246000000ff
And what exactly is not working? I can see that data is decoded.
Sadly the device is always showing itself as offline,even though i’ve tried the full IMEI number and also the 11digits with ‘0’ added to the front.
Where's your device in the above log?
I thought it was all the hex debug messages coming in from port 5013. I can see my other two devices (Id 8170867703 and 6170970227) and they show online,but this third device always shows offline.
Which one is the third one in the logs?
After checking through the logs again and using the Hex decoder, I think this log is actually showing that my ‘unknown device’ isn’t actually seeing the server. My Server GUI has actually 3 online device which I think are:-
2018-11-01 09:36:42 INFO: [ad90fe79] id: 8170867703, time: 2018-11-01 09:36:40, lat: xx.xxxxx, lon: -x.xxxxx, speed: 0.9, course: 0.0
2018-11-01 09:36:53 INFO: [a571af35] id: 6170970227, time: 2018-11-01 09:36:50, lat: xx.xxxxx, lon: -x.xxxxx, course: 0.0
2018-11-01 09:37:12 DEBUG: [e57f770d: 5001 < 82.132.239.246] HEX: 3836333037303031393232383338353b
Whilst the fourth device that I’m unclear of it manufacture details, port number and ID,etc. isn’t actually on here.
Am I understanding the data correctly now?
Sorry for getting so confused by the log file…...I will have to go back and reconfigure the device and check all the ‘clone’ ports until hopefully I start to see new hex entries on the file.
I don't know if you understand it correctly. Your original claim was that you see device in the logs and it's not decoded somehow. I'm still waiting for any proof of that.
Yes, I thought I was seeing my unknown device in the log, but after your help I think I'm completely wrong and its not actually there. Since I'm new to Traccar I have obviously miss-read the log file and thought some of the hex debug entries from other devices were the ‘unknown’ device’.
Sorry to waste your time. Hopefully I can find more information on my random device and its configuration on the internet, although I’m struggling so far.
Anton, thanks for all the help – its really appreciated.
Happily I have now fixed my issue…..My ‘unknown device’ was a zx302 running on port5023. Once I applied the relevant port forwarding to my router the device has now started to send data to the server.
Sadly, along with others in different threads here I found the device to have some interesting quirks.
Hello,
I am trying to add an unknown device to my Traccer Server. Sadly, in my log files I am gaining several debug messages:-
When I use the Hex converter they turn into:-
Unfortunately, these don’t really make any sense to me, do they mean much to anyone else?
I have presumed that I am using port 5013 and its a ho2 protocol, sadly with the either the full imei or the shortened imei with the add 0, neither will show the device as online.