Good day, I have been having a problem with the watch protocol, I managed to send a custom command, but it is returning me repeatedly in the log the same command and in very small intervals of time
Annex the part of the log and modification in the code WatchProtocolDecoder:
log:
2019-02-20 10:24:05 INFO: [9569ac42] id: 1703146333, command type: custom sent
2019-02-20 10:24:05 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303031662a5b33472a313730333134363333332a303030412a485254524154452c315d205d
2019-02-20 10:24:06 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:06 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:06 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:06 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:06 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:06 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:07 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:07 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:07 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:07 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:07 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:07 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:08 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:08 DEBUG: [9569ac42: 5093 > 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
2019-02-20 10:24:08 DEBUG: [9569ac42: 5093 < 200.68.137.224] HEX: 5b33472a313730333134363333332a303030382a48525453544152545d
code part:
} else if (type.equals("HRTSTART") || type.equals("hrtstart")) {
sendResponse(channel, id, index, "HRTSTART");
}
I've seen similar behaviour in TK, this is the fix you need to do: you need to make sure you're not sending a "response", when yo received a "response". In the log you can see:
you send: HRTRATE,1
watch responds: HRSTART
but then you "respond" by:
sending: HRSTART....
and from here it's the same there and back...
IMHO you just need to ignore the HRSTART, it's a response, you don't need to answer it.
it doesn't help, I've never read about HRTRATE or HRSTART in any of the watch protocol docs (3 or 4) I saw. But it's very clear from the log you sent that the problem is that you're sending back a response to the watch's response. Stop doing that and it might start to work (but at least it stops the endless loop)
Good day, I have been having a problem with the watch protocol, I managed to send a custom command, but it is returning me repeatedly in the log the same command and in very small intervals of time
Annex the part of the log and modification in the code WatchProtocolDecoder:
log:
code part:
} else if (type.equals("HRTSTART") || type.equals("hrtstart")) { sendResponse(channel, id, index, "HRTSTART"); }