Currently running the full ChirpStackOS on a single RPi4 and another RPi4 is running an MQTT client handling the device info. That all works great and stable (when internet connection is there …).
My idea is to have the Chirpstack running as stand-alone. As said when the internet is no longer connected the ChirpStack is not fully operational.
1> Webaccess partially works. Often errors “Context deadline exceeded Code: 2”). E.g. live traffic from the LoRaWAN gateway can no longer be seen.
2> External MQTT client does not receive any messages
Look like internal communication is somehow failing. Does anybody have an idea what is causing this and how it can be solved?
All the “map” stuff is probably not going to work. A quick look at the dev_console in my browser points to openstreetmap. For that to work you’d need to also host a tile-server. For the DNS Issue, you could try mDNS: https://www.howtogeek.com/167190/how-and-why-to-assign-the-.local-domain-to-your-raspberry-pi/
should “just-work” in a “.local” environment.
I dont know if the Chirpstack Image already supports it.
Hi there, and I hope this finds you well.
Did you develop a reliable architecture for your standalone/private IoT system? I am keen to have a conversation since I am doing a thesis and aiming to set up a private IoT system without dependency on the internet or wifi.
Thanks
Adam