Client is sending periodic Device Online

Hello together,
i use amongst other devices a H02 Tracker.
But this tracker sends every 10 Minutes a Device Online EMail ... but i became every 20 seconds a GPS Position.
My Timeout Value <entry key='status.timeout'>7200</entry> is at 7200 and all other devices are working well and send only a Online Message when device is coming up.
But the H02 Tracker is annoying me with the periodic online / offline messages.
The Log shows the following

2017-03-30 20:44:34  INFO: [2629FA6E] disconnected
2017-03-30 20:44:35  INFO: [C9587015] connected

2017-03-30 20:54:16  INFO: [C9587015] disconnected
2017-03-30 20:54:17  INFO: [29BEFC4E] connected

2017-03-30 21:03:58  INFO: [29BEFC4E] disconnected
2017-03-30 21:03:59  INFO: [34EC7D88] connected

2017-03-30 21:13:40  INFO: [34EC7D88] disconnected
2017-03-30 21:13:41  INFO: [98EF5EE0] connected

and so on

Any proposals to solve this messages?

Anton Tananaev7 years ago

I need to see HEX messages from your device.

Vladimir S6 years ago

Same problem here with H02 protocol.

2017-12-10 00:02:55  INFO: [ECA6FAC5] disconnected
2017-12-10 00:02:56  INFO: [38A2CCB2] connected
2017-12-10 00:03:27 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233303332332c412c343930332e343036352c4e2c30313835352e343939342c452c3030302e31342c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3430393123
2017-12-10 00:03:28  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:03:23, lat: 49.05678, lon: 18.92499, speed: 0.1, course: 0.0
2017-12-10 00:04:26 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233303432312c412c343930332e343037382c4e2c30313835352e343939382c452c3030302e30382c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3430393123
2017-12-10 00:04:26  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:04:21, lat: 49.05680, lon: 18.92500, speed: 0.1, course: 0.0
2017-12-10 00:05:24 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233303531392c412c343930332e343034382c4e2c30313835352e353030372c452c3030302e31322c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:05:24  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:05:19, lat: 49.05675, lon: 18.92501, speed: 0.1, course: 0.0
2017-12-10 00:06:22 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233303632302c562c343930332e343034332c4e2c30313835352e353031302c452c3030302e31362c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:06:22  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:06:20, lat: 49.05674, lon: 18.92502, speed: 0.2, course: 0.0
2017-12-10 00:07:20 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233303731342c412c343930332e343033382c4e2c30313835352e343939312c452c3030302e37342c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:07:21  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:07:14, lat: 49.05673, lon: 18.92499, speed: 0.7, course: 0.0
2017-12-10 00:08:19 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233303831352c412c343930332e343035372c4e2c30313835352e343931312c452c3030302e30372c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:08:19  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:08:15, lat: 49.05676, lon: 18.92485, speed: 0.1, course: 0.0
2017-12-10 00:09:17 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233303931332c412c343930332e343032372c4e2c30313835352e343939392c452c3030302e30382c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:09:17  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:09:13, lat: 49.05671, lon: 18.92500, speed: 0.1, course: 0.0
2017-12-10 00:10:15 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233313031302c412c343930332e343033382c4e2c30313835352e343938312c452c3030302e31382c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:10:15  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:10:10, lat: 49.05673, lon: 18.92497, speed: 0.2, course: 0.0
2017-12-10 00:11:13 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233313131312c562c343930332e343034302c4e2c30313835352e343935392c452c3030302e33382c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:11:13  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:11:11, lat: 49.05673, lon: 18.92493, speed: 0.4, course: 0.0
2017-12-10 00:12:11 DEBUG: [38A2CCB2: 5013 < 84.245.120.93] HEX: 2a48512c383137303837323534322c56312c3233313230392c562c343930332e343033332c4e2c30313835352e353030362c452c3030302e30342c3030302c3039313231372c46464646424246462c3233312c30332c30303036302c3631323123
2017-12-10 00:12:11  INFO: [38A2CCB2] id: 8170872542, time: 2017-12-10 00:12:09, lat: 49.05672, lon: 18.92501, speed: 0.0, course: 0.0
2017-12-10 00:12:37  INFO: [38A2CCB2] disconnected
2017-12-10 00:12:38  INFO: [61E6AC31] connected

Anton Tananaev6 years ago

It looks like device disconnects from the server. You need to contact device vendor. It doesn't seem to be a server issue.