Devices not connecting to new gateway

I have a new enterprise gateway I’m trying to spin up, but none of the devices are connecting to it automatically. I will call this ‘gateway 3’

I have another gateway powered down, and when I turn it on, the devices only connect to the previous one. ‘gateway 1’

This is not the same behavior I had with ‘gateway 2’ where it automatically started to pickup the data from the devices.

there is a strange reading on one of the nodes I don’t normally see.

this is the configuration on gateway 1,
which is allowing me to see the data.

and this is the configuration of devices on gateway 3 which is not allowing me to read data

Hi @danempiric I’ve reviewed the screenshot you sent and noticed a few important points to address. Let me explain:

  1. To receive sensor data on any NCD Gateway, you simply need to access Node-RED. The default flow (a Wireless Gateway node and a Debug node) is preconfigured and ready to use. Once the NCD sensor is powered on, sensor data will start arriving automatically.

  2. There is a strange reading on one of the nodes I don’t normally see: If you’re referring to the “error 1 status node” in “Read first line from backlogs,” this is a normal message. It indicates that no data is currently stored in the local database, which is expected in certain scenarios.

  3. You don’t need a Wireless Device node in order to receive sensor data. We recommend using this node only when you need to set sensor parameters.

  4. Auto Config Checkbox: Ensure the ‘Auto Config’ checkbox is unchecked. Click ‘Done’ and then ‘Deploy’ to save and apply the changes. This step prevents the sensor from being reconfigured every time it sends the FLY message. Frequent reconfiguration can cause the sensor to stay active longer and drain the batteries faster.

For Gateway 3: Please try the following:

Delete all Wireless Device nodes from your workspace, leaving only the connection between the Wireless Gateway node and the Debug node. Your workspace should look like this:

Click ‘Deploy’ to save and apply the changes, then press the reset button on one of your sensors and check if incoming sensor data appears in the Debug window.

Note: If the ‘Auto Config’ checkbox is enabled on your other Gateways, please uncheck it and deploy the changes.

I recommend the following tutorial, which demonstrates what I mean:

Additionally, may I ask if you previously set the Destination Address to a specific Gateway address in any of your sensors? This configuration could cause the sensor to send data exclusively to that specific target (Unicast Mode).

Please try this and let me know how it works or if you need further assistance!
Thank you,
Eduardo M.

Thanks! Does unchecking the auto config and destination address on the original gateway reset the fields so they will work again?

If I had previously had a destination address should I set it to the default 0000FFFF or just uncheck it and put the devices back in to config mode?

Hi @danempiric To revert the sensor back to Broadcast Mode, you will need to follow these steps:

  1. Enable the ‘Auto Config’ checkbox and, if the sensor supports OTF, also enable ‘OTF Config’.
  2. Check the ‘Active’ checkbox for the ‘Destination Address’ property and set the default value for the destination address to 0000FFFF.
  3. Click Done, then Deploy, and perform the configuration (either manually or via OTF).

Note: Unchecking the ‘Auto Config’ option ensures the sensor does not reconfigure its parameters each time it sends a FLY message. This is considered a best practice to avoid unnecessary reconfiguration.

Note: Unchecking the ‘Active’ checkbox for a specific configuration property in the Wireless Device node ensures that this particular configuration will not be applied in the next configuration process. It’s important to emphasize that this action does not revert or modify any properties already configured on the sensor; it simply excludes the unchecked property from being applied in future configurations.

Take a look at this and feel free to let us know if you have any questions.
Thank you,
Eduardo M.

Hi,

I’m trying to connect a new sensor out of the box without any configuration and it’s not connecting to the gateway. Is it possible that there is some issue with the gateway? Is there a way to reset the gateway?

Hi @danempiric Before proceeding, let me ask you the following:

  1. Do you have access to Node-RED on the Enterprise IIoT Gateway?
    (If possible, could you share a screenshot or file of your current flow?)
  2. Are you receiving sensor data from other NCD sensors on this Gateway?
  3. Did you modify the Network ID on the Wireless Gateway node?
  4. Could you open the sensor, press the RST button, and check if you see any LED indications?
  5. What is the approximate distance between the sensor and the gateway?

Please try this.
Thank you,
Eduardo M

Hi,

  1. Do you have access to Node-RED on the Enterprise IIoT Gateway?
    (If possible, could you share a screenshot or file of your current flow?) This is the whole flow, I’m recycling a lot of the prebuilt codes that you’ve previously provided
    flows.json (46.9 KB)
    When I add an inject block to the mqtt, it publishes to my topic in AWS.
  2. Are you receiving sensor data from other NCD sensors on this Gateway?
    -no, none of the other sensors are connecting
  3. Did you modify the Network ID on the Wireless Gateway node?
  • I did not, it should be the same, but I did upload the flow from a previous gateway. I had done this with another gateway and it works ok, so I don’t think that would be the issue.
  1. Could you open the sensor, press the RST button, and check if you see any LED indications?
    -when pressing the reset button, both red led lights blink
  2. What is the approximate distance between the sensor and the gateway?
    -approx 1 ft.

Got it, thank you for the information. I’ve checked the Serial Port, baud rate, and Network ID on your Wireless Gateway node, and everything seems to be in order.

Are you able to check if pressing the reset button on the sensor allows you to receive data on the other gateways?

when I press the reset button, it still only pushes to my original gateway, but not the new one.

Hi Dan, This issue is quite interesting. Could you please try setting the Destination Address of the sensor to Broadcast Mode (0000FFFF) using your original gateway? After doing this, check if you can see incoming data on the new gateway.

Thank you,
Eduardo M.

Ok.

From an order of operations can you confirm this plan:

  1. powerdown and disconnect gateway that does not work (gateway 2)
  2. keep working gateway ( gateway 1) on
  3. all sensors remain on
  4. on gateway 1, set the sensor module to ‘auto config’ and OTF
  5. change Destination address to Broadcast Mode
  6. ‘Deploy’
  7. Wait for sensors to reconfigure, confirm with the messages ’ sensor mode’- otf
  8. uncheck auto config and OTF in sensor module
  9. ‘Deploy’
  10. Power Down Gateway 1
  11. Power Up Gateway 2

If the sensor is in broadcast mode, it should be seen by all of the gateways at the same time?

Hi Dan,
Yes, that procedure is correct. However, Jacob reminded me that you could perform a factory reset on the sensor. This will return the parameters to their default settings, and the default mode is Broadcast.

Before performing a sensor factory reset, please access to Node-RED on Gateway 2 and press the left button on the Wireless Gateway node, this will put the gateway into configuration mode. When the sensor undergoes a factory reset, it will output messages, which should appear in the debug window.

To apply a factory reset on the sensor:

  1. Press and release the RST button
  2. Immediately press and hold the CFG button
  3. Hold the CFG button for about 18-20 seconds
  4. Release CFG button
  5. Wait for 3 secods
  6. Press and release the RST button

For this procedure, it is not necessary to power off the Gateways.
Note: If you don’t get anything into debug window during factory reset then it could be a frequency difference.

Thank you,
Eduardo M.

I’ve tried both actions, and it doesn’t seem to have taken. What do you mean different frequency?

I’m using the NCD 4-20mA transmitters, device type 52.

These are the messages being sent from the sensors, not sure if this provides any new info.

“receive_options”: {
“ack”: 0,
“broadcast”: 0,
“type”: “”

Hi Dan, Thank you for conducting the testing. After analyzing the scenario with the provided information, it seems that the best course of action would be to return the Enterprise Gateway for RMA. It is highly likely that the configuration on the Wireless Module is incorrect, as wireless modules can occasionally fail during programming. Instructions for returning the item long with an RMA ID will be emailed to you after completing the RMA form:

Let us know if you have any questions.

Thank you,
Eduardo M.

Thanks! Would it be possible to get a different unit sent out?