In version 5.8 the graph report includes custom attributes, but the attribute is not configurable, which may mean that an ordinary user does not understand it. For example a teltonika device may display the attribute io251 and not know what it is.
You could implement that if the attribute is not in usePositionAttributes it could be configurable.
You can use Computed Attributes to "map" the io* values to something that is user understandable (or update the decoders in the code and submit a pull request).
In version 5.8 the graph report includes custom attributes, but the attribute is not configurable, which may mean that an ordinary user does not understand it. For example a teltonika device may display the attribute io251 and not know what it is.
You could implement that if the attribute is not in usePositionAttributes it could be configurable.
this was the change in 5.8 https://github.com/traccar/traccar-web/commit/b756ef71c34dbfb5caa8a908ff890afc168fda3d