Feature work around request
i have been using traccar custom command with great success however due to the traccar limited support answers on commands for some protocols. like h02. When i send a custom command like 666 via the server log file i see it was sent and the device gets back reply via the server log only . would it be possible to view the reply from the device that has been decoded within the event area as a notification
example send via custom command
Via web Command sent : Param1 ;
server log : 706172616d31 ( decoded = param1)
server log reply : 4c4b5f4341525f5451323031382f31322f31342031323a33322c69642c343732303035393338382c49503a332e3133372e3230372e39303a353031332c73312c302c2c2c2c5331362c53303042303041312c4632333333 (decoded = LK_CAR_TQ2018/12/14 12:32,id,4720059388,IP:3.137.207.90:5013,s1,0,,,,S16,S00B00A1,F2333)
if the reply was visible via the web it would really help to know if the custom command worked
For feature requests you should use GitHub. You would also need to provide protocol documentation and details on how to identify reply.
Feature work around request
i have been using traccar custom command with great success however due to the traccar limited support answers on commands for some protocols. like h02. When i send a custom command like 666 via the server log file i see it was sent and the device gets back reply via the server log only . would it be possible to view the reply from the device that has been decoded within the event area as a notification
example send via custom command
Via web Command sent : Param1 ;
server log : 706172616d31 ( decoded = param1)
server log reply : 4c4b5f4341525f5451323031382f31322f31342031323a33322c69642c343732303035393338382c49503a332e3133372e3230372e39303a353031332c73312c302c2c2c2c5331362c53303042303041312c4632333333 (decoded = LK_CAR_TQ2018/12/14 12:32,id,4720059388,IP:3.137.207.90:5013,s1,0,,,,S16,S00B00A1,F2333)
if the reply was visible via the web it would really help to know if the custom command worked