We have a very large number of different protocols. The set of supported standard commands depends on the protocol and many protocols only >support custom commands. When you try to create a saved command, it shows you the full list of types because it doesn't know what device you >will link it to. But it doesn't mean it will work. This is what we're discussing here.
I know there's "a lot" of commands "available" and they will not appear when I'm sending them to the wrong device.
I already made that mistake and learn.
What I'm telling, and what I could understand, is that whathever the device can handle, can be sent from traccar server, no matter what traccar can enable for that device as default, if is available or if I write it and put in the corresponding "saved command" custom command slot.
The first image I show is that all those custom commands are "saved commands"
The second image, shows how they are named "saved commands" and they are the commands I wrote/saved.
And the last one was only to show enabled commands as default that don't work.
I know there's "a lot" of commands "available" and they will not appear when I'm sending them to the wrong device.
I already made that mistake and learn.
What I'm telling, and what I could understand, is that whathever the device can handle, can be sent from traccar server, no matter what traccar can enable for that device as default, if is available or if I write it and put in the corresponding "saved command" custom command slot.
The first image I show is that all those custom commands are "saved commands"
The second image, shows how they are named "saved commands" and they are the commands I wrote/saved.
And the last one was only to show enabled commands as default that don't work.
