Unable to configure LoRaWAN after reset SenseCAP M2

Products & Technology SenseCAP
#1

Hello,

I have a SenseCAP M2 Multi-Platform LoRaWAN Gateway(M2-AS923).
At first, I was using this gateway connected to AWS IoT Core.
Then, after executing “Reset to defaults” from the Web UI to connect to other LNS, the LoRaWAN settings do not appear in the Web UI.
The following error message appears when selecting “LoRa” > “LoRa Network” from the Web UI menu.

RPCError
RPC call to uci/get failed with ubus code 4: Resource not found
  at ClassConstructor.handleCallReply (http://192.168.137.37/luci-static/resources/rpc.js?v=1.3.7:94:7)

image
image972×218 20.1 KB

How can I get this gateway back to normal?

Gateway:
Current OS Version 0.9.4-5

Thank you

#2

I created a technical support ticket and resolved it.
After restoring the gateway, I connected to the Internet and waited for about 20 minutes.

#3

How did you “reset it to defauts?” On my case I did it via Local Console. I have the Helium version and it fails to reach SenseCAP servers to OTA firmware updates. How much time does it past since it upgraded automatically on your case? I’ve created a new thread.

Powered by LuCI / OpenWrt 21.02.0 r1-20220322 r16279-5cc0535800
Model M2-US915
Build Version r1-20220322
OS Version 0.9.24-27

#4

Hi there,
Well that can’t be correct. It’s looking for a Local IP address.
You need to create a static route or get the correct IP , it’s a WAN ip btw…
HTH
GL :slight_smile: PJ

#5

Hi everyone,
I’m also facing this same issue, I did a factory reset using device button now I can’t get firmware update from SenseCAP server.

Thanks

#6

why did you do that, were you scammed?

#7

Actually configuration wasn’t done properly so I thought I can do it again after reset my device.

#8

This is interesting, can you be more specific? I see that the M2 reaches sensecapmx.com ICMP
image

#9

Hi there,
looks like the reset to default isn’t able to use the Nameserver as your Router can,
WAN ip 104.26.5.19 ok ,but http://192.168.137.37 is a local IP call back is not. so that’s what I would look to. Do the traceroute and see if it times out then. The Ping is just OK.
HTH
GL :slight_smile: PJ
:v:

#10

Got it, this answer was for @yukik issue. I don’t have that error and he has the Multi-platform version. The one that I have is the Light - Helium version that I’m updating at a new thread. On my case. traceroute completes fine as well.