Local mqtt topics are bad in app-connect.py

[rawlines]

I was getting crazy why my gateway was not sending any messages to my http server. so after 1 day of debugging i found that u have some topics in local mqtt broker bad written.

local_mqtt_sub_up = "lora/+/+/up"
local_mqtt_sub_joined = "lora/+/joined"
local_mqtt_down_topic = "lora/%s/down"

When i change the up topic to "lora/+/up" it starts to receibe the Uplinks.
local_mqtt_down_topic i have not tested it, but for sure it has to be "lora/+/down"

This should be the corrected values:

local_mqtt_sub_up = "lora/+/up"
local_mqtt_sub_joined = "lora/+/joined"
local_mqtt_down_topic = "lora/+/down"

[reissjason]

Thanks for the feedback.
Can I ask what version of mPower are you using?
Some versions of mPower do not output uplinks in the lora/+/+/up topic format.

The down_topic string will be used later and the %s will be replace by the DEV-EUI, so I doubt you will want to change it.

On the conduit all local messages can be seen using this command.
$ mosquitto_sub -v -t "#"

[rawlines]

MTCDT-LEU1-247A with firmware version 5.3.8s-s1.
My bad of local_mqtt_down_topic = "lora/+/down", i have later read in the code that it is used as a template

[peralbaroger]

Hi @reissjason and @rawlines,

Maybe it's not the way but I'm using three Multitech Conduit and I'm new on Python and system development. Looking this example I have some doubts and I think it could help me to advance in my project.

First, I don't understand well the purpose for app-connect.py and inside python-mqtt-service the file server.py.

Secondly, I need to create an api to send/catch the data from my Conduit to my data visualization tool, and as I understood, it's only possible to do it with MQTT or HTTP(S)?

Could you help me with a little explanation to get a better idea of the path I should follow?

Very grateful,
Roger.

[reissjason]

See more details here, some features will be in next mPower firmware.
https://multitechsystems.github.io/lorawan-app-connect-mqtt