mc-webui 2.14.0

Important

You need one command before you can install this release. Updating currently stops at Username for 'https://github.com' — your installation is fine and this repository is still public, so a username or token will not help. Run this once on your server:

git config --global http.version HTTP/1.1

Still asked for a username? Then you update with sudo, and --global only covers the user who ran it — root has its own. Run sudo git config --global http.version HTTP/1.1 as well.

Then mcupdate as usual. This release carries the same setting inside update.sh, so it is a one-off. Full explanation: #33

---

Features

• Repeater settings are no longer read all at once when you open a section. Every field under My Repeaters → Settings is a full round-trip through the mesh, and expanding a section fired one for each field in it: seven questions to a repeater four hops away, answered one at a time, while you sat and waited for the one value you actually came for — and often for a batch that timed out halfway through and left half the section blank. Nothing is read now until you ask. Each field has its own read button beside it, so checking or changing a single setting costs a single round-trip; Read all fields at the top of a section still fetches the whole thing for when that is what you want. Clicking read on several fields in a row is fine — they queue and run one after another. The values you have read are also remembered per repeater, so a section opens showing the last readings rather than empty boxes; a remembered value carries a small clock beside its name and a note at the foot of the section saying when it was read, because the repeater may well hold something else by now. Those values stay editable — applying a setting writes an absolute value, so editing from an old reading still sets exactly what you typed — but the field is one click away from being current when it matters. Field hints moved into an ⓘ next to each field name, and every field has one now instead of the handful that did; the sections are considerably shorter for it.

• The RX delay setting is now available under My Repeaters. Settings → Advanced offered the two transmit delays, txdelay and direct.txdelay, but not rxdelay, which the firmware has had all along — the only way to reach it was a raw CLI command. It is a different mechanism from the other two: instead of scattering retransmissions at random, it staggers them by how well the packet was heard, so a repeater with a strong copy repeats a flooded packet first and one that barely caught it waits, then skips the repeat entirely if a better-placed node has already done it. On a dense network that is the difference between one retransmission and five. The field accepts 0 to 20 and takes the reading you already had on the device; 0 turns it off, which is what the firmware ships with and what most repeaters should stay on unless there is a reason to change it.

Fixes

• Updating no longer stops at a GitHub username prompt. mcupdate started halting on its very first step, showing Username for 'https://github.com': and then sitting there waiting for something to be typed — on every server at once, on the same day, with nothing having changed on any of them. It is an odd thing to be asked by a repository that is public and has never needed a login, and nothing was wrong with the installs: GitHub changed how its front end answers the second half of an anonymous fetch over HTTP/2, and the git that ships with Debian 12 — version 2.39, built against libcurl 7.88 — now gets a 401 back for a request that had always been allowed. Git reads any 401 as credentials, please and asks for a username, which is why typing one never helped and why a token would not have helped either. The update script now asks git to speak HTTP/1.1 for its pull, which GitHub still answers exactly as before, and it no longer waits on the keyboard when a fetch genuinely does fail — it reports the error and stops, instead of leaving an unattended update hanging indefinitely. If you are stuck on an older copy and so cannot update to pick this up, run git config --global http.version HTTP/1.1 once on the server and mcupdate will go through.

• The same routing path can no longer be added to a contact twice. Both path editors — the one in a contact's info panel and the one under My Repeaters → Paths — took whatever they were given, so an identical route could end up in the list two or three times: added by hand, picked again from the repeater picker, or imported a second time from the device, which is the easiest of the three to do by accident because the button gives no hint that the path is already there. A duplicate is worse than untidy, because the list is a retry order: when a message fails, the app works down it, and a repeated entry simply retries a route that has just been shown not to work while the genuinely different alternative below it waits its turn. Adding a route that is already on the list is now refused with This path is already on the list, and the entry box stays open so the hops can be corrected. Two paths count as the same only when both the hops and the hash size match — the same bytes read as 1-byte hops describe a different route than as 3-byte hops, and both remain available. Duplicates already sitting in the list are collapsed into one when you update, keeping the starred copy if one of them was starred.