Enterprise Gateway issues

Hi,

I have an Enterprise Gateway Lite. I have had it connected to a sensor and reading, no problem when the gateway is in Wifi AP mode.

However, when I put it into Wifi Client mode, and connected it to my home wifi, the device becomes unusable. Any attempt to connect through ETH1 timeouts and the only way I can get back to the device, is to turn off the power, quickly get access as it’s starting up and restore to factory defaults. If I leave it longer, it appears the device is running at 100% CPU.

I’ve followed the instructions here: Enterprise IIoT Gateway Network Settings - NCD.io.

What going on? I need this gateway to access the internet by wifi.

Appreciate any help,

Charles

And now I realise that the factory reset is has removed some of your configuration and now the sensor does not read the same. I am not receiving sensor data in the message or FLY messages.

How can I restore to out of the box settings please?

Hi @charlesg Could you please clarify which parts of the configuration are removed when performing a factory reset on the device?

Could you share a screenshot of your Node-RED flow?
Additionally, could you share your Node-RED flow? To do so, please follow these steps:

  1. Click the main menu (three horizontal lines in the top-right corner) in Node-RED.
  2. Select the “Export” option.
  3. Ensure the “Current Flow” option is selected.
  4. Click the “Download” button to save the JSON file.
  5. Attach the JSON file to this thread.

thank you,
Eduardo M

Hi Eduardo,

Since I did the reset there is no default flow to export. I imported this one, mentioned elsewhere on the forum:

NCD-Edge-CR/configuration/flows at main · ncd-io/NCD-Edge-CR

flows.json (7.6 KB)

After the factory reset, I noticed that the default flow and the node red NCD flow examples are no longer present.

Previously the Wireless Device node would pick up that MAC address but now I needed to type it in.

Hi @charlesg Thank you for sharing the information, I think you will need to update the NCD library in Node-RED, please follow these steps:

  1. Open Node-RED and navigate to the main menu (three horizontal lines in the top-right corner).
  2. Select “Manage Palette” from the menu.
  3. Locate the @ncd-io/node-red-enterprise-sensors library in the palette.
  4. If an “Update to 1.4.x” button appears in the lower-right corner, please click it to initiate the update.

Once the update is complete, close the Manage Palette window and restart Node-RED. To assist with this process, please import the following Node-RED flow into your workspace:

[{"id":"69f9288b47110fd2","type":"inject","z":"dd33b5f28aad9520","name":"Enable to restart","props":[],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","x":260,"y":640,"wires":[["9001f60183cf49b1"]]},{"id":"9001f60183cf49b1","type":"exec","z":"dd33b5f28aad9520","command":"pm2 restart all","addpay":"","append":"","useSpawn":"false","timer":"","winHide":false,"oldrc":false,"name":"Restart","x":560,"y":640,"wires":[["bab52ac9709c66f0"],["bab52ac9709c66f0"],["bab52ac9709c66f0"]]},{"id":"bab52ac9709c66f0","type":"debug","z":"dd33b5f28aad9520","name":"debug 8","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":710,"y":640,"wires":[]},{"id":"60347b12cfb4eda2","type":"comment","z":"dd33b5f28aad9520","name":"👇🏼 Click the embedded left button to enable.","info":"","x":290,"y":600,"wires":[]}]

To do this, copy this json code, then go to Node-RED and click on main menu, then select import option and paste the code into pink text box input, and finally click on Import button, then locate the flow and click on Deploy button, to Restart Node-RED click on inject node:

Wait a few seconds, refresh the web browser page and please could you reset your sensor in order to see if now you see the correct sensor_data and FLY message, please.

Try this and feel free to let us know if you have any questions,
Thanks,
Eduardo M

Hi,

What is the Gateway IP address and subnet of the WiFi network the Gateway is connecting to in client mode?

Thanks @Eduardo_Mtz I will try that but I imagine that the gateway needs an internet connection which I am struggling with.

@jacob please see screenshot, if that helps

Hi,

Most likely this is caused by an network conflict which is confusing the Gateway’s network routing.

Before connecting the Gateway to the WiFi network can you change some network settings on the Gateway to see if this resolves the issue?

  1. Open the web configuration dashboard (port 80)
  2. go to Network > LAN
  3. Click the edit icon next to LAN1
  4. Change IPv4, IP Pool Start, and IP Pool End to a different subnet (see example below)
  5. Click Submit and the red checkmark at the top of the page

Example settings:

WARNING this will change the IP address you use to access the Gateway over ETH1 or when connected directly over WiFi while the Gateway is AP mode to whatever IP Address you have in the IPv4 Address field (minus the /24).

1 Like

@Eduardo_Mtz and @jacob thank you so much, you’ve solved it and made my day!