[Rafael]

Ok, thank you!

[Rafael]

Hi Jason, thanks!

Apparently, TTI has not implemented it yet:

https://github.com/TheThingsNetwork/lorawan-stack/issues/3909

But they do mention this problem in the documentation:

“In general, a gateway will receive all other LoRaWAN and non-LoRaWAN traffic from neighbouring devices, and it will forward that traffic to the Network Server. When it comes to filtering unwanted sensor data at the gateway level, users might consider using a gateway with a whitelisting function. This function can effectively reduce data traffic and operational costs. Please contact your gateway’s manufacturer for additional info.”

Is there another method for filtering packets while using a cloud-based LNS?

[Rafael]

It worked! Thank you!

[Rafael]

Hi Jeff,

Thank you!

So, just to make it clear: it’s not possible to downgrade from v5.3.3 to v5.2.x? (MTCAP-L4E1-868-001A)

Rafael

[Rafael]

Ok, so I did what you said: run-app & in the Start script and node app.js > /dev/null 2>&1 & in the run-app script. And now, after starting the app with app-manager, it runs in the background:

admin@mtcap:/var/config/app/app-name$ sudo app-manager --command start --appid APPID
AppCommand::executeStartScript: executing: /var/config/app/app-name/Start start
Success!
admin@mtcap:/var/config/app/app-name$

And these are the logs in /var/log/messages:

2020-10-30T19:24:26.319473+00:00 mtcap APPMANAGER: AppCommand::getBasePathFor: unknown app type. Defaulting to custom
2020-10-30T19:24:26.319976+00:00 mtcap APPMANAGER: AppCommand::getBasePathFor: unknown app type. Defaulting to custom
2020-10-30T19:24:26.320385+00:00 mtcap APPMANAGER: AppCommand::getBasePathFor: unknown app type. Defaulting to custom
2020-10-30T19:24:26.333177+00:00 mtcap APPMANAGER: AppCommand::executeStartScript: executing: /var/config/app/app-name/Start start
2020-10-30T19:24:26.477978+00:00 mtcap APPMANAGER: AppDataDB::SetAppData: updating app info in /var/config/AppManager.json with appId: APPID
2020-10-30T19:24:26.486483+00:00 mtcap APPMANAGER: Exiting with success status

But the application still doesn’t start after rebooting the gateway (our main problem). Any other ideas on how to solve this problem?

Thanks,

Rafael

[Rafael]

It only runs another shell script:

function ExecuteStart {
    echo "ExecuteStart:"
    ./run-app
}

And run-app looks like this:

nohup node app.js &

Thanks,

Rafael

[Rafael]

Hi Jeff,

We don’t use an SDCard and the application is installed in: /var/config/app/app-name.

Output of the app-manager start command:

admin@mtcap:~$ sudo app-manager --command start --appid APPID
Password: 
AppCommand::executeStartScript: executing: /var/config/app/app-name/Start start

After that, the application runs correctly and there are no more logs. But it doesn’t run in the background. After running the start command, I can’t use the terminal anymore. I don’t know if that’s normal, in the Start script we run the node app using nohup.

Thanks,

Rafael

• This reply was modified 3 years, 6 months ago by Rafael.
• This reply was modified 3 years, 6 months ago by Rafael.
• This reply was modified 3 years, 6 months ago by Rafael.

[Rafael]

Hi Jeff,

Here it is:

admin@mtcap:~$ cat /var/config/AppManager.json
{
	"Apps" : 
	[
		{
			"AppDescription" : "...",
			"AppId" : "<APPID>",
			"AppInfo" : "Not Available",
			"AppName" : "app-name",
			"AppType" : "CUSTOM",
			"AppVersion" : "8.3",
			"AppVersionNotes" : "...",
			"Enabled" : true
		}
	]
}

Thank you,

Rafael

[Author]

Posts