You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're attempting to use the agent with a TTN application server and a Custom Payload (Decoder configured in the TTN application server). Some questions and notes:
What's the "protocol": "GENERIC_PROTO" part in the device creation? is it related to the choice of representation format (Cayenne vs Custom)?
Could we document what restriction custom payloads have? (e.g., not-supported data types, data structures (nested?), or even characters used in the object_id (i.e., original attribute name coming form the sensor) like could that use spaces?
What kind of payloads have been tested with the custom decoders?
Thanks in advance
The text was updated successfully, but these errors were encountered:
Hi there,
We're attempting to use the agent with a TTN application server and a Custom Payload (Decoder configured in the TTN application server). Some questions and notes:
What's the
"protocol": "GENERIC_PROTO"
part in the device creation? is it related to the choice of representation format (Cayenne vs Custom)?Could we document what restriction custom payloads have? (e.g., not-supported data types, data structures (nested?), or even characters used in the
object_id
(i.e., original attribute name coming form the sensor) like could that use spaces?What kind of payloads have been tested with the custom decoders?
Thanks in advance
The text was updated successfully, but these errors were encountered: