When using ChirpStack (before loraserverio) as application_server "provider": "loraserver.io" , and use a payload format decoding done by the application server, this agent expect receive a message.object (See loraserveriorAppService.js), but Chirspack publish with name objectJSON (See https://www.chirpstack.io/application-server/integrations/events/)
The solution I have found is to set the payload marshaler on the Chirpstack application server as json_v3.
# Payload marshaler.
#
# This defines how the MQTT payloads are encoded. Valid options are:
# * protobuf: Protobuf encoding
# * json: JSON encoding (easier for debugging, but less compact than 'protobuf')
# * json_v3: v3 JSON (will be removed in the next major release)
marshaler="json_v3"
With json (change the object name to JSON object and also put the escape character "\" before the double quotes, then the agent failed:
When using ChirpStack (before loraserverio) as application_server
"provider": "loraserver.io"
, and use a payload format decoding done by the application server, this agent expect receive amessage.object
(See loraserveriorAppService.js), but Chirspack publish with nameobjectJSON
(See https://www.chirpstack.io/application-server/integrations/events/)The solution I have found is to set the payload marshaler on the Chirpstack application server as json_v3.
With json (change the object name to JSON object and also put the escape character "\" before the double quotes, then the agent failed:
With json_v3: