Skip to content

Transmit protocol #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jmezzera opened this issue Aug 24, 2020 · 0 comments
Open

Transmit protocol #13

jmezzera opened this issue Aug 24, 2020 · 0 comments

Comments

@jmezzera
Copy link

I'm currently developing a project that relies on an Arduino sending data to a MQTT server over LoRa and a dragino GateWay.
I'd really like to send data in JSON, however, all examples (at least the ones I found) use the format
attrName1=attrValue1&attrName2=attrValue2[...].
Using this protocol, I could send data correctly and receive it in the other end; however, when a use JSON encoding, the GW receives it correctly but doesn't forward it. Logs below

Mon Aug 24 19:49:44 2020 user.notice root: [IoT.MQTT]: Check for sensor update
Mon Aug 24 19:49:44 2020 user.notice root: [IoT.MQTT]: Found Data at Local Channels: 10009
Mon Aug 24 19:49:44 2020 user.notice root: [IoT.MQTT]:  Find Match Entry for 10009
Mon Aug 24 19:49:44 2020 user.notice root: [IoT.MQTT]:  [-t] /TOPIC
Mon Aug 24 19:49:44 2020 user.notice root: [IoT.MQTT]:  [-m] {"field1":29, "field2":86,"field3":87}
Mon Aug 24 19:49:50 2020 user.notice root: [IoT.MQTT]: Check for sensor update
Mon Aug 24 19:49:52 2020 daemon.info lg02_pkt_fwd[26457]:
Mon Aug 24 19:49:52 2020 daemon.info lg02_pkt_fwd[26457]: RXTX~ Receive(HEX):3c31303030393e7b226669656c6431223a33342c20226669656c6432223a38352c226669656c6433223a38397d

Is the & encoding the only one supported or am I missing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant