RAK7258 - Feature requests

// Cellular Status
Mode: 2G/3G/HSDPA/4G
Operator: 02-UK
RSSI: -78 dBm
Tower: 299F7B
Roaming: Yes | No

// Basic Station

  1. White listing
  2. Automatic data recovery

// Gateway status - push from GW
Multitech have a Free cloud service for use with their Gateways called DeviceHQ
This has a range of features the one many orgs use regular Status updates from GW to DHQ.

To operate gateways in multiple countries & regions you need good visibility of GW health.
So being able to get things like cell RSSI, GW temp help with being bumped off networks or finding that a GW is mounted over an oven!

So a simple HTTPs post to a user specified end-point with a small set of key indicators or as other GW vendors do use a secured SMS service for remote commands and Status updates. Would help significantly.

Thanks
Lawrence

1 Like

+1. Bumping this post. Would like the same for RAK7249. Hoping for a reply from the RAK team.

Hi don’t hold your breath unless your buying 1000s can’t see RAK adding this.
One way around is to use say RPI to query RAK via it’s web interface.
https://ip/cgi-bin/luci/;stok=d7118d6064b064dcb7c8f70a4a002388?status=1
stok=d7118d6064b064dcb7c8f70a4a002388 is passed back when you authenticate

//status 1 returns
{
“swap”: {
“free”: 0,
“total”: 0
},
“conncount”: 111,
“leases”: [
{
“expires”: 26333,
“macaddr”: “b8:27:eb:65:0d:11”,
“ipaddr”: “192.168.230.241”,
“hostname”: “dev05a”
}
],
“leases6”: {},
“lte”: {
“band”: “LTE BAND 3”,
“CCID”: “89882806660010553487”,
“IMEI”: “862869030106749”,
“IMSI”: “901405101055348”,
“PIN”: “READY”,
“ber”: 99,
“rssi”: 15,
“channel”: 1617,
“opt_id”: “23430”,
“network_type”: “FDD LTE”,
“operator”: “EE”,
“SIMSTAT”: 1
},
“wwan”: {
“proto”: “dhcp”,
“ipaddr”: “100.123.163.2”,
“link”: “/cgi-bin/luci/;stok=d7118d6064b064dcb7c8f70a4a002388/admin/network/network/wwan”,
“netmask”: “255.255.255.252”,
“gwaddr”: “100.123.163.1”,
“expires”: -1,
“uptime”: 78301,
“ifname”: “wwan0”,
“dns”: [
“8.8.8.8”,
“8.8.4.4”
]
},
“memory”: {
“buffered”: 5664768,
“total”: 129368064,
“shared”: 15572992,
“free”: 72654848
},
“uptime”: 78368,
“wifinets”: [
{
“device”: “radio0”,
“networks”: [
{
“ifname”: “ra0”,
“disabled”: false,
“encryption”: “-”,
“bssid”: “60:C5:A8:76:12:71”,
“mode”: “Master”,
“quality”: 10,
“noise”: -75,
“ssid”: “RAK7258_1271”,
“link”: “/cgi-bin/luci/;stok=d7118d6064b064dcb7c8f70a4a002388/admin/network/wireless/radio0.network1”,
“assoclist”: {},
“txpoweroff”: 0,
“bitrate”: 300,
“txpower”: 13,
“name”: “Master "RAK7258_1271"”,
“channel”: 2,
“country”: “00”,
“signal”: -256,
“up”: true,
“frequency”: “2.417”
},
{
“ifname”: “apcli0”,
“disabled”: false,
“encryption”: “-”,
“bssid”: “00:00:00:00:00:00”,
“mode”: “Client”,
“quality”: 0,
“noise”: 0,
“ssid”: “studyAP”,
“link”: “/cgi-bin/luci/;stok=d7118d6064b064dcb7c8f70a4a002388/admin/network/wireless/radio0.network2”,
“assoclist”: {},
“txpoweroff”: 0,
“bitrate”: 300,
“txpower”: 13,
“name”: “Client "studyAP"”,
“channel”: 2,
“country”: “00”,
“signal”: 0,
“up”: false,
“frequency”: “2.417”
}
],
“name”: “Generic 802.11bg Wireless Controller (radio0)”,
“up”: false
}
],
“wan”: {
“proto”: “static”,
“ipaddr”: “192.168.1.113”,
“link”: “/cgi-bin/luci/;stok=d7118d6064b064dcb7c8f70a4a002388/admin/network/network/wan”,
“netmask”: “255.255.255.0”,
“gwaddr”: “192.168.1.254”,
“expires”: -1,
“uptime”: 78337,
“ifname”: “eth0.2”,
“dns”: [
“192.168.1.254”
]
},
“localtime”: “Thu Jan 21 13:38:08 2021”,
“connmax”: 16384,
“loadavg”: [
118880,
54752,
32288
]
}

If that has the information you are looking for, you could query that from a script on the gateway itself and push it somewhere.

Chris, yes not sure if that would survive a firmware update?
Also it’s beyond our “collective skill set” as a biz our cloud services companies want Gateway health
And reassurance as we start to move them from Multitech to RAK.
This was the quickest way for use to provide that.

My guess is that things added (which is to say, transparently captured on the overlay partition) would survive along with user configuration settings, etc.