Group Actions
Engagement
  • Author Author: skruglewicz
  • Date Created: Date Created
  • Views 2257 views
  • Likes 7 likes
  • Comments 12 comments
Related
Recommended

Solution --- If your having trouble connecting your Gateway to the internet - THIS MIGHT HELP

skruglewicz

Hello Fellow challengers of the OMEGA  N-Layer Design challenge.

If you are having troubles as I and a fellow challenger , with getting the Gateway from the bundle to connect to the internet, this blog might help.

I contacted Omega support via email and after several conversations back and forth and a few days, they came up with the following instructions that did the trick for me. After following the steps below, by putting the recommended firmware onto the gateway I was able to connect it to the internet and continue attaching the rest of the components to it.  I’m sure it will affect more of you because my out of the box gateway had a really old firmware version. I posted this blog to help my fellow challengers avoid the time I spent, trying to get the major hardware component of the bundle to work. 

How to fix No Network/Internet Connection for Out-of-Box Gateway

Troubleshooting

You have a brand new, out-of-box Layer N gateway. You already created a Layer N account from the

cloud.omega.com. You are ready to connect the gateway to your Internet-enabled router with a

network cable.

However, after many tries to connect to the Internet and you are sure that your router does have

Internet connection, but your gateway ‘s LED light is still on either Solid Orange or Flashing Red.

Recommended Solution

You need to manually update your gateway firmware.

Here are the Steps:

  1. Access Gateway Internal Web UI – Please read enclosed Quick Start Guide
  2. Download the firmware:

If you have GW-001-2, please download your firmware at

https://omegaupdates.azurewebsites.net/Firmware/GW/gw-001-2-na_v1.0.25.bin

If you have GW-001-3, please download your firmware at

https://omegaupdates.azurewebsites.net/Firmware/GW/gw-001-3-na_v1.0.24.bin

  1. From the Gateway web UI, please navigate to the System Settings page
  2. Click on the magnify icon to browse the firmware file you just downloaded on your computer.
  3. Click Upload to get the latest firmware on your gateway. Please wait a few seconds for gateway to

Install the firmware and reboot itself.

image

My out of box settings

Current Firmware Version:1.0.5, Release Date:28, May, 2020

SO much out of date!!

 image

SUCCESS with the process !! hooray!!

After following the instructions, the LED is now solid green !!!

My settings screen shows Current Firmware Version:1.0.24, Release Date:27, Jul, 2021

image

A new option under settings “LOG”, shows the connection!

image

The n-layer cloud shows the heart beat Icon and the (i)information icon displays the connection status

 image

Now you proceed with connecting the Smart Sensor

Enjoy

 

Appendix A – Understanding the behavior of the LED light on the gateway

This pdf was emailed to me by Tech support. It defines the different LED status codes, rebooting and setting the gateway to the  factory resets

 

image

Parents

  • HI

    I had exactly the same problem. Unfortunately I did not browse element14 site for some time and I was not aware that someone else was experiencing the same issue. I spent many days troubleshooting the problem since I was convinced it was a connectivity problem that was down to something in my network, or something I did wrong.

    In the end, I made a network capture and realized there was a problem with TLS (as far as I understand, CA certificate on the server was not accepted as valid by the gateway) but then I stopped investigating the issue

    I will never thank you enough for sharing the solution! 

Comment

  • HI

    I had exactly the same problem. Unfortunately I did not browse element14 site for some time and I was not aware that someone else was experiencing the same issue. I spent many days troubleshooting the problem since I was convinced it was a connectivity problem that was down to something in my network, or something I did wrong.

    In the end, I made a network capture and realized there was a problem with TLS (as far as I understand, CA certificate on the server was not accepted as valid by the gateway) but then I stopped investigating the issue

    I will never thank you enough for sharing the solution! 

Children
  • in reply to amgalbu

    Hello ,

    Glad to hear that your on your way with the challenge. I had a great deal of frustration with the Gateway and thought to give my fellow challengers a heads up on the  buggy firmware version. Your network capture was a brilliant idea to diagnose the problem and find out that it was a TLS CA certificate problem between the gateway firmware and the N-Layer Cloud. A few of us were unfortunate to get firmware on our gateway with an old outdated certificate. Very good to know. It makes total sense to me now. Lesson learned. 

    I'm happy to help a fellow challenger. It's all about collaboration with me. I'm familiar, with your work here on the community. I've been in a Challenge with you before  and have benefited from your EE knowledge.. Nice to meet you...

     I was able to get the firmware information after a few inquires into tech support. I've been able to communicate with engineers thru the DAS email and by registering on the Omega site. The online support is kind of confusing but after a bit of persistence I was able to get an email from a Tech rep and a ticket was created.

    Once you have registered on omega.com, navigate to the support ticket page as the steps listed below,. Then press the Orange button marked "ADD NEW"  image  and fill out the contact form and submit it. You should get an email as a response eventually.

    image

    Kind Regards and Good Luck on the Challenge

    Steve K

  • in reply to amgalbu

    Usually when I'm in a challenge or test, I create a Slack channel and invite all participants. To deal with situations like this, where someone finds an issue or a solution.

  • in reply to Jan Cumps

    Hello ,

    Hope this comment finds you well across the pond.

    Yes good point . I've been on a Slack channel that you set up for a Roadtest on the OPTIGATm TPM SLM 9670 .It helped me through some hurdles.

    Interesting enough, this turned out to be TLS certificate problem but the status mechanism (a blinking colored pairing LED) on the device only told the user that "it could not connect to the internet"..

    Cheers

    Steve K.