TTN v2 doesn't enable managing integrations via an HTTP API; however, they do have an MQTT server that enables publishing/subscribing to device messages. For the TTN v2 NetworkProtocol, instead of POSTING/DELETING integrations, it subscribes/unsubscribes from MQTT messages.
I tried using TTN's "simuldate uplink" functionality, but no "uplink" events were fired as a result, so I wasn't able to test. I was able to send a downlink, but not test it. I received a "down/errors" event, because I had not converted the base64 payload to hex, so that indicates to me that the connection with the MQTT server is working, but I wasn't able to receive any "dowlink/sent" or "downlink/scheduled" events as a result of sending a downlink.
Screenshots or logs (if appropriate)
Questions:
Have you connected this PR to the issue it resolves? #161
Does the documentation need an update? No
Does this add new dependencies? No
Have you added unit or functional tests for this PR? No
What does this PR do?
Do you have any concerns with this PR?
How can the reviewer verify this PR?
View
Any background context you want to provide?
TTN v2 doesn't enable managing integrations via an HTTP API; however, they do have an MQTT server that enables publishing/subscribing to device messages. For the TTN v2 NetworkProtocol, instead of POSTING/DELETING integrations, it subscribes/unsubscribes from MQTT messages.
I tried using TTN's "simuldate uplink" functionality, but no "uplink" events were fired as a result, so I wasn't able to test. I was able to send a downlink, but not test it. I received a "down/errors" event, because I had not converted the base64 payload to hex, so that indicates to me that the connection with the MQTT server is working, but I wasn't able to receive any "dowlink/sent" or "downlink/scheduled" events as a result of sending a downlink.
Screenshots or logs (if appropriate)
Questions: