LoRa messages not received by Node-red

[Arnaud Coiffier]

Hi,

I’m currently developping a LoRa device, and I use a multitech conduit AEP for debug purposes.

I use the nored application to display my LoRa messages, and some times, the messages are not received by LoRa node.
I am sure that these messages are sent by my device, since the acknowledgments are enabled and received.

When i reboot the multitech (and not my device), I can receive more messages. But I can’t have an application where my gateway needs to be restarted every day or so.

Has anyone had this problem before, and knows how to fix it?

Thanks.

[Jason Reiss]

Have you made any changes to the mosquitto.conf on Conduit?

Others have reported issues like this after change MQTT to be accessible from remote servers.

[Arnaud Coiffier]

Hi,

Thanks for your response.

I have not changed the mosquitto.conf (or used mosquitto). The only changes I have made are the LoRa configuration, the cellular configuration (including a DDNS), and the nodred app.

[Jason Reiss]

mosquitto is the MQTT broker on Conduit.
The lora-in and lora-out nodes use MQTT is why I ask.

There maybe clues in /var/log/app/node-red.log and /var/log/mosquitto.log

[Arnaud Coiffier]

Ok,it seems the log are erased when the conduit reboot, so the next time the bug happens, I will check the logs and post them here.

[Arnaud Coiffier]

Hi, it happened again, and I checked the logs.

I have a quick question before posting the logs.
Is node-red still working if no-one is connected to it? (I’m using nodered to post every lora message received on my server).

Thanks for your help.

node-red.log

Welcome to Node-RED
===================

13 Jul 11:50:35 - [info] Node-RED version: v0.11.1
13 Jul 11:50:35 - [info] Node.js  version: v0.10.40
13 Jul 11:50:35 - [info] Loading palette nodes
13 Jul 11:54:01 - [info] Settings file  : /var/config/app/install/development/settings.js
13 Jul 11:54:01 - [info] User directory : /var/config/app/install/development
13 Jul 11:54:01 - [info] Flows file : /var/config/app/install/development/flows.json
13 Jul 11:54:02 - [info] Server now running at http://127.0.0.1:1881/
13 Jul 11:54:09 - [info] Starting flows
13 Jul 11:54:09 - [info] [lora in:89de0be9.96cea8] lora in node created
13 Jul 11:54:11 - [info] [lora out:23e49c33.6caaf4] lora out node created
13 Jul 11:54:24 - [info] [lora in:b13ca301.5c5b3] lora in node created
13 Jul 11:54:41 - [info] [lora out:262a7916.2af206] lora out node created
13 Jul 11:54:43 - [info] Started flows
13 Jul 11:54:45 - [info] [lora in:89de0be9.96cea8] mcard: true
13 Jul 11:54:45 - [info] [lora out:23e49c33.6caaf4] mcard: true
13 Jul 11:54:45 - [info] [lora in:b13ca301.5c5b3] mcard: true
13 Jul 11:54:45 - [info] [lora out:262a7916.2af206] mcard: true
13 Jul 11:54:47 - [info] [lora in:89de0be9.96cea8] Connected to MQTT for LoRa in node.
13 Jul 11:54:47 - [info] [lora out:23e49c33.6caaf4] Connected to MQTT for LoRa out node.
13 Jul 11:54:47 - [info] [lora in:b13ca301.5c5b3] Connected to MQTT for LoRa in node.
13 Jul 11:54:47 - [info] [lora out:262a7916.2af206] Connected to MQTT for LoRa out node.
13 Jul 15:02:40 - [info] [lora out:262a7916.2af206] Published downstream lora packet
13 Jul 15:02:48 - [info] [lora out:262a7916.2af206] Published downstream lora packet
13 Jul 16:09:44 - [info] [lora out:262a7916.2af206] Published downstream lora packet
13 Jul 16:11:57 - [info] [lora out:262a7916.2af206] Published downstream lora packet
13 Jul 16:12:01 - [info] [lora out:262a7916.2af206] Published downstream lora packet
Attempting to log in as: admin
Status code: 200
Attempting to log out using token: 881E6BC4C380F9FCD86F7EDA237F8

mosquitto.log

1499939263: mosquitto version 1.4 (build date 2016-09-09 17:52:24-0500) starting
1499939263: Config loaded from /etc/mosquitto/mosquitto.conf.
1499939263: Opening ipv4 listen socket on port 1883.
1499939263: Warning: Mosquitto should not be run as root/administrator.
1499939281: New connection from 127.0.0.1 on port 1883.
1499939281: New client connected from 127.0.0.1 as 8c192d7000051000 (c1, k60).
1499939685: New connection from 127.0.0.1 on port 1883.
1499939685: New connection from 127.0.0.1 on port 1883.
1499939685: New connection from 127.0.0.1 on port 1883.
1499939686: New connection from 127.0.0.1 on port 1883.
1499939686: New client connected from 127.0.0.1 as mqttjs_6212320645f3f377 (c1, k60).
1499939686: New client connected from 127.0.0.1 as mqttjs_39a4a5b62578a679 (c1, k60).
1499939686: New client connected from 127.0.0.1 as mqttjs_d50c369dab974d80 (c1, k60).
1499939687: New client connected from 127.0.0.1 as mqttjs_a2008ec4b4c12b25 (c1, k60).
1499951024: Client 8c192d7000051000 has exceeded timeout, disconnecting.

[Görkem Polat]

Hi,

We have the same problem. We are using Node-RED to see LoRa messages coming from end-node. End-node receives response from gateway stating that transmission is successful, yet we can not see some of them on the Node-RED screen.

We did not change mosquitto.conf. Any solution?

[Lawrence Griffiths]

We’ve been seeing this problem on and off for a year.
As the number of our AEP Gateways increases it’s becoming more of an issue.

Given the low number of AEP sales I don’t think it’s a priority for MT to look at without log based evidence.

My hunch is the problem with the LoRa-in node.
Adding a [mqtt in] node to [local host] and sub to topic lora\+\up we can sometimes see uplink messages, but no LoRa-in messages.

A re-deploy of node-red flow often sorts the the problem.
We are testing a dead-mans handle which re-starts node-red via AEP API
POST to http://127.0.0.1/api/command/restart_node_red does it though it will take about 4 mins to re-start.

Lawrence

[Jason Reiss]

It appears that the lora-in node is lacking any “connectionlost” handling code.

The MQTT in/out nodes appear to be more robust in handling reconnects.

[Lawrence Griffiths]

Jason, thanks for that.
I was going to get a nodejs Dev to look at lora-in node.

Any chance of taking this up with the Dev team?
Other wise we will look to fork and fix lora-in.

Lawrence

[Jason Reiss]

Unfortunately, I don’t see this issue getting resources in the near term.

[Author]

Posts