Repository navigation
ChirpStack - #2546
ChirpStack#2546
Conversation
Try this script
COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/tomfrenzel/DevScripts/chirpstack \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/tomfrenzel/DevScripts/chirpstack/ct/chirpstack.sh)"
Against a core branch as wellAdd Useful flags while testing
|
There was a problem hiding this comment.
Proxmox script test failed at 6ecac5e:
ct/chirpstack.sh(pve): update: exited 1: var_region is required for unattended installs (e.g. var_region=eu868).ct/chirpstack.sh(incus): update: exited 1: var_region is required for unattended installs (e.g. var_region=eu868).
Logs and details: test result. Push a fix, then ask for /test again.
Proxmox script test@tomfrenzel ✅ 2/2 passed at
ARM64 (information only, not counted): 1/1 passed. Notes (information only, not counted):
📊 Resources
📄 ct/chirpstack.sh (pve) — install log (1292 lines)🔄 ct/chirpstack.sh (pve) — update log (23 lines)🔁 ct/chirpstack.sh (pve) — second update log📄 ct/chirpstack.sh (incus) — install log (520 lines)🔄 ct/chirpstack.sh (incus) — update log (18 lines)🔁 ct/chirpstack.sh (incus) — second update log📄 ct/chirpstack.sh (arm64) — install log (498 lines)🔄 ct/chirpstack.sh (arm64) — update log (18 lines)🔁 ct/chirpstack.sh (arm64) — second update logFull logs: workflow run (artifacts |
Proxmox script test passed at 6fc85c1.
| var_unprivileged="${var_unprivileged:-1}" | ||
|
|
||
| export var_region="${var_region:-}" | ||
| var_testurl="${var_testurl:-https://github.com/community-scripts/DevScripts/issues/2521}" |
There was a problem hiding this comment.
Instead of that hack here, can we give the var_region some sane default? The test should run as if a user dose not provide anything ideally.
There was a problem hiding this comment.
I thought about that as well, but since it's dependent on the users region it did not much sense. For example if an american user runs this with a default like eu868, they would have the gateway running with a frequency which is not allowed there.
If that's fine with you, i could set eu868 as default (official docs also use that) and let them know to configure a region that matches their home location
There was a problem hiding this comment.
@michelroegl-brunner Now looking at your comment again: It's on the change from my second commit. There i just removed the variable inside the update script which i forgot to remove from my testings.
So the update script does not need the variable at all.
The install script still requires it, but the tests are successful since they set the variable to ci-test.
Do you still prefer if we use a default value here?
I saw that other scripts also abort if required variables aren't set (i.e. opencloud)
There was a problem hiding this comment.
@tomfrenzel
If deafults will not work then we leave them out. worst thing is that the CI will fail, wich is fine.
I just want to try and push defaults where possible, so it is easier for the users to install suff. Is there a list onlie of all regiones a user can pick? I saw you added a hint in the json for a .toml file, wich a user only can access after the install. Would be greate if we can add a link to some online resource. Or if such thing dose not exist, would you mind openeing a discussion in the main repository where you list the contents of the toml file and link to it in the JSON?
Thank you!
There was a problem hiding this comment.
Alright, then i would say we keep it required during install. The linkt to the list of available regions is being printed above the prompt (https://github.com/chirpstack/chirpstack/tree/master/chirpstack/configuration)
It's on Line 17 in chirpstack-install.sh. So either the user sets the variable directly (They see the warning with the link on the website and can choose their region before running the script) or the see the link during install with no prevoisulsy specified region.
If thats fine with you, i would update the json and add the GitHub link with the regions there as well (instead of toml file reference)
There was a problem hiding this comment.
Ah i did miss that you print it during install. Than it is fine and we can keep it as is!






✍️ Description
This adds the ChirpStack scripts. Implementation details are below ind "Additional Information"
🔗 Related PR / Issue
Link: #2521
✅ Prerequisites (X in brackets)
🧩 Script
Name: ChirpStack
Tool:
🗂️ Category (X in brackets)
ct/+install/)vm/)tools/addon/tools/pve/🖥️ Platform – tested on (X in brackets)
🏗️ Architecture (X in brackets)
🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.🔍 Code & Security Review (X in brackets)
CODE-AUDIT.md&CONTRIBUTING.mdguidelinesAppName.sh,AppName-install.sh,AppName.json)fetch_and_deploy_gh_release,fetch_and_deploy_codeberg_release,fetch_and_deploy_gl_release, orfetch_and_deploy_from_urlinstead ofgit pull.📋 Additional Information (optional)
ChirpStack publishes apt packages for their server and gateway but users need to manuelly configure their region. Without a propper region, the setup will not work out of the box. This is also the reason why the service fails after installation and needs to be reset after configuration (
systemctl reset-failed chirpstack).I tested it with my Seeed M2 Gateway and it worked as supposed to.
selfh.st does not have an icon yet so i referenced the svg from the ChirpStack docs repo. I also requested the icon for selfh.st in selfhst/icons#1085
📦 Application Requirements (for new scripts)
🌐 Source
https://github.com/chirpstack/chirpstack
🤖 AI Assistance (X in brackets)
AGENTS.mdand.github/agents/pve-script-creator.agent.mdas guidance, and the output has been reviewed and corrected to match those guidelines.GitHub Copilot Fusion -> GPT-6.1-Sol (Medium)
Used it for the
sedas i can't wrap my head around thesedsyntax 😄