I am having trouble with this as well...
We have been using Teltonika RUT240 to push data from VFDs and other gizmos to Schneider Machine advisor.
We use this JSON format in the Data Sender configuration
I believe this information and the token was obtained from Machine advisor.
(This goofy "blog" system insists on needlessly double-spacing entered text)
The data shows up in Machine advisor automatically grouped by records with ID, TS, ST and VR
and one can then name the records - since the source ID, and register are visible.
However, in Thingsboard, the records also show up with a similar organization in one of the data handling views
but as far as attaching data to widgets on the dashboard, it seems that all of the various items are lumped together and averaged
rather than being made available as separate records.
I thought that JSON was specific to HTTPs, but it appears it is also used with MQTT.
So I'm confused whether the fix required is on the Teltonika end or the Thingsboard end, or both...
Ideally each of the modbus records being transferred could be tagged on the originating end in the Teltonika
In that way, that tagging would appear in the Thingsboard datastream thereby eliminating the need to reverse-deduce the
type of data being received based on ID , register, values, etc...
Where is the best place to get a general / intermediate overview of this protocol dance ? and then drill down to details ?