Skip to content

meshsat 0.11.1

Choose a tag to compare

View all tags
@papadopouloskyriakos papadopouloskyriakos released this 29 Sep 06:54
· 7 commits to main since this release
v0.11.1
6e65a8b

meshsat 0.11.1: the Hub page, and a mailbox check that asks first

  • Setup > Hub, as MeshSat Android's "Hub connection" card:

    • Where the link to the Hub stands, in Android's words and order, with its dot: Switched off, Connected as …, Connecting, Cannot reach the Hub, Not connected, or Not set up. "Why: …" gives the reason a connect failed.
    • "Use the Hub": as on Android, the setting takes effect when the link next starts.
    • "Scan the Hub's QR code". A provisioning claim still waiting shows on the card as "Getting the Hub's settings, N s".
    • "Test the connection" is timed to the Hub broker's acknowledgement, for example "142ms". Without a link it says "Not connected" and sends nothing.
    • "Connection details" for setting up by hand: the Hub MQTT URL, Bridge ID, callsign, username, password (with its eye) and health interval. Save restarts the Bridge.
    • The Setup row and the Home lane follow the link the same way.
    • Not on this page: "Reach a kit through the Hub". The Bridge has no relay client to a kit.

  • The satellite mailbox: "Check Mailbox" opened a billed Iridium session on one tap. It now asks "Check the satellite mailbox?" first, in Android's words, and is offered only while a modem is connected.

  • Upgrades: installing a new version no longer switches the Bridge's start at boot back on when it was switched off in Diagnostics.

  • The Bridge underneath (MeshSat Bridge f761743c, MESHSAT-1417):

    • It reports the Hub link's state and the reason it failed.
    • It keeps "Use the Hub", the callsign and the health interval, and tests the connection.
    • A saved form no longer clears the Hub's CA certificate.

  • Tested: 305 unit tests. On the bench phone, the whole suite ran against the installed package, all green: 127 cases against a scripted Bridge, 10 against a second, real Bridge, and 7 live. Among them:

    • each of the Hub link's states, the switch, the test, the details saved;
    • on a real Bridge, the switch and the details kept, and the test refused without a link;
    • the mailbox check asked about first, with nothing sent on Cancel;
    • live: the T-Deck hearing the alarm test and a text typed in the app.

    After the suite, a check on the phone found that an upgrade left the Bridge stopped when its start at boot was switched off. The package now notes a running Bridge before an upgrade and starts it again after. Both ways were tested on the phone (switched on: on and running; switched off: off and still running), and the install case ran again on the final package.

    No Hub link is live on the bench: the connected and failed states are proven against the scripted Bridge and the Bridge's own tests.

Install on a Mobian phone: wget https://github.com/meshsat/meshsat-linux/releases/download/v0.11.1/meshsat_0.11.1_arm64.deb && sudo apt install ./meshsat_0.11.1_arm64.deb (docs/INSTALL.md).

Assets 4
Loading