Hi,
i’ve played arround a while - also with old FW and the latest, but it seems that from the GUI there is no chance to have MQTT enabled and working TTN in parallel. From a technical standpoint i do not see any issue to support both, the question is if this is possible somehow to make both work in parallel…
Thanks a lot Norbert
For MQTT the unit runs a local backend and for TTN it connects to the TTN backend. Using two backends in parallel results in all kinds of potential issues and is not supported because of that. The packet forwarder does not have the option to connect to two backends so it is a technical limitation.
Thanks for the feedback.
still unclear as at least two platforms are supported to be linked (primary, secondary) and the FROM-Sensor direction should not really be an issue as its simply sending messages. Downlink to the sensor maybe but still i do not see the big problem when two iot platforms can exist.
But if its not supported the discussion anyhow does not help. Thanks again for the clear answer.
Consider LoRaWAN encryption and what is required to decrypt messages from a sensor and where those keys (and the other end device information) are stored and you have to answer to why it is an issue.
Sorry for joining late to the party. Yes it can work in parallel (there isn’t really a reason why it wouldn’t be possible, it is basically a broadcast message), so in case someone is still trying to use it that way, this is the story.
I used the scenario before, with older firmware (not sure what version, it was 2021.), and I managed to make it work simply by configuring and turning on ABP decryption. Configuration is basically filling in device address, app session key, network session key and selecting decoder. Back then, for my sensor (door sensor, LDS01) there wasn’t any selectable decoder, so I had to write it manually and add it to the proper folder (via ssh). In the meantime, in newer fw version, decoder for this sensor became available. So, in addition to configuring lorawan settings (for ttn), configuring ABP and MQTT client were things I had to do in order to make it work in parallel.
Although newer fw version seems to have fair amount of added options, the configuration is almost the same. To make it work mqtt channel needs to be added. I added it simply by clicking on AUTO ADD button on Channels page. What it does (as far as i was able to discover), this channel is basically a file that is created in /var/iot/channels/ folder when message is received form sensor and decrypted by ABP decryptor (one file per sensor/decryptor). Not long afterwards, mqtt script (basically a bash script with dead loop) picks it up and push it to the mqtt.