Robert Hadow

After writing my bug report, I established a new browswer tab with client.meshtastic.org and pointed it at the appropriate URL, which in my case was 192.168.1.201. The web page painted...

@philon- Subsequently, I launched client.meshtastic.org again in the same tab. No, the URL was not duplicated. At this second retry, the page populated fully with all data accurate. You are...

I use `meshtastic --help` as the current and authoritative command reference. In order for that to work, there needs to be an online source to tell us what is the...

@jp-bennett I suggest that the matter of Meshtastic documentation be loooked at holistically. Why do people look at documentation? Because they are trying to implement some feature for themselves or...

The `--nodes` command makes a beautiful table, true. That's great for a human reader. I would love `--nodes-raw` or -`-nodes-csv`. Yes, I could write regex to extract the data, but...

Brokenpipe is a common issue. In a more general sense, the meshtastic code needs to built with the same design criteria as all embedded code--a graceful exit from every possible...

Try this: https://resource.heltec.cn/download/package_heltec_esp32_index.json

In the old days (before the web server was no longer installed to the device), each tab in my Chrome browser had the URL in the address bar (e.g. 192.168.1.200,...

As you approach the design task, please consider deeply each time you add a new icon. While an icon uses the minimum amount of real estate, asking a new user...

@SpudGunMan Hello Kelly -- The point here is that the --help, the web-based documentation (https://meshtastic.org/docs/configuration/radio/bluetooth/), and the CLI error messages should all be generated from a common repository, so that...