i need to do a proper bug report on why integration+downlink converter doesn’t work for V4, but I am short on time, instead I will post here a method to do this for both TB CE and TB PE.
short: setup a rule chain to handle the downlink mqtt post to CS V4.
- listen to attribute update (I use a widget that update attribute to trigger manual payload)
- use the MQTT node in the rulechain
- use a script to format the expected CS V4 payload
- dynamically populate the devEUI in the MQTT Topic
- dynamically populate app ID in the MQTT topic (can set application ID as attribute on the triggering device and dynamically populate app id in the topic)
** I am using static app id in this post
here is the mqtt node setup, i am using static APP ID for now and dynamic devEUI
here is the script node setup:
var msg =
{
"devEui": msg.deviceid.toLowerCase(),
"confirmed": true,
"fPort": 6,
"data": btoa(msg.payload),
}
return {msg: msg, metadata: metadata, msgType: msgType};
and final result in CS V4