chirpstack VS chirpstack-gateway-os

can you help me please? I wish to use the Postgresql database I installed using "apt install..." locally on the machine in a container of a Chirpstack. IP of my machine is 10.0.2.45 and Postgresql is running on ports 5432 and 5433. I know I should be able to reach it because I made a container in the same docker network 172.19.0.0/16 and installed postgresql client to try to connect to a database on the same machine 10.0.2.45 and it did. But then I try again multiple time with chirpstack and I keep getting this error: ... 2023-03-12T21:24:30.454103Z INFO chirpstack::storage: Setting up PostgreSQL connection pool Error: Setup PostgreSQL connection pool error Caused by: timed out waiting for connection: could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432? could not connect to server: Cannot assign requested address Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432? 2023-03-12T21:25:02.132215Z INFO chirpstack::cmd::root: Starting ChirpStack LoRaWAN Network Server version="4.3.0" docs="https://www.chirpstack.io/" ... and then it restarts again and again.

I "play" with LoRa and LoRaWAN devices for work so can add a few comments here to help you on this. Apologies if I'm repeating stuff you already know. LoRa (I'm going to use LoRa and LoRaWAN interchangeably cause I'm lazy) is a small packet unidirectional periodic communications protocol. More accurately you can talk to it from the gateway to the device but for class A it only opens for a very short period after it transmits, class c is always receiving but at the cost of battery life. Because it uses small packets it has limited things to send (and is encoded so needs to be decoded at the receiver so to make it simple you will want to limit what is sent). It is NOT for real time communications ie send and receive now. I have seen an article which suggested using LoRa instead of pagers for emergency services but that has limits. In terms of the system you would require to make this idea work you would need gateways (or access public gateways if available), a server stack so either Chirpstack if you want to run your own server and device manager, or use the Things Network for a managed server more info on servers. Each device that you want on your network needs to be activated and registered which if you are thinking of making it widely available becomes difficult in managing and scaling. In terms of security it's pretty good. I had a 15 second look at that link someone else has posted and have made a LoRa device with the FiPy, it's easy to get going (lots of python libraries and example code) but challenging to program well. As I said I've done a lot of research and playing with these trying to build a private network for work; I've tried to be concise but hopefully covered most things. Ideas for disaster work are critical so even if this idea doesn't pan out keep up the good work and keep the ideas coming.

FWIW, for building your own private network, there is no need to rely on something like TTN. ChirpStack (https://www.chirpstack.io/) is a very mature and easy to deploy LoRaWAN suite that's worth looking at!

Next, setup your own LoRaWAN Server on the Raspberry PI using ChirpStack: https://www.chirpstack.io/

I saw that Reticulum (https://github.com/markqvist/Reticulum/) is already using I2P for Internet communication. What I would like to create is a similar infrastructure but a bit more advanced using Chirpstack (https://www.chirpstack.io/) servers connected between each other over I2P. Everyone who wants to use the infrastructure can connect a limited number of sensors for each Chirpstack server available nearby. If they want to join more sensors, or improve the infrastructure, they can give their contribute joining new Chirpstack servers to I2P network.

My setup involved https://www.chirpstack.io/ feeding data to self-hosted InfluxDB (or FarmOS via our code at https://github.com/mockingbirdconsulting/FarmOSMQTT), with dashboards in Grafana. I started to write my own dashboard that had dedicated overview screens etc, but it was a serious effort for very little reward.

You can easily setup your own offline LoRaWAN Server Stack on a Raspberry Pi, for example this one https://www.chirpstack.io/, thats what I did. Therefore I would definitely recommend the use LoRaWAN instead of only the LoRa Modulation.

https://www.chirpstack.io/ is a complete solution written in go & open source, including mqtt broker, app server, gateway, gateway bridge and more. It also comes with docker-compose for local development. I worked with it for a while, it's a good project.

If you want to get more involved and run your own infrastructure you could look at something like ChirpStack.

Hi! I'm a new Yocto user trying to develop a fork of Chirpstack's Gateway OS for Raspberry Pi based LoRaWAN gateways. Although I have successfully modified and added new recipes, I'm struggling with adding a USB cellular modem to my image.