Release v0.9.397

Fixed

• A Waev or LetsMesh broker no longer publishes under a leftover custom topic. The Observer page sent the custom base topic for every broker, although the field only shows for the Custom MQTT format. A value typed there before switching the format replaced the whole topic the broker expects, and the broker refused everything the repeater sent. The topic now goes out only for a Custom MQTT broker.
• Typing a broker's host no longer sets its JWT audience to the first letter. The audience followed the host one keystroke at a time and stopped at the first character, so a broker added by hand presented m as its audience. Leave the audience blank and the host is used.
• The Observer page cannot save before its settings have loaded. Edit Settings opened on an empty form while the repeater's answer was still on its way, and Save then wrote that empty form, dropping every broker. The key now waits for the settings.
• Saved Observer settings stay on screen. After a save the page showed the values from before it until the next refresh, and a second Edit and Save sent those old values back. The page re-reads the settings as part of saving.
• A blank IATA code is refused. The repeater publishes under a topic that begins with the code, and a broker drops a blank one without a word.
• Packets heard from an openHop repeater over MQTT keep their real time. The browser-side MQTT subscriber could not read the repeater's timestamps and stamped every packet with the moment it reached the browser.
• A broker added to the repeater's configuration as a preset shows on the Observer page. An entry such as preset: waev, the form the repeater's own example file recommends, appeared as a blank broker, and Save refused it as incomplete. The page now lists it as a preset you can keep or remove, and saves it back as it is, so the repeater keeps using the preset's current addresses.
• A password your browser fills in no longer counts as an unsaved change on the Configuration page. Browsers put the saved sign-in password into the Password section's Current Password box on their own. The page then asked "Leave unsaved changes?" whenever you moved to another page, and it also held back the default-interface switch and the other sections' apply buttons. Only a new password you type, or its confirmation, counts as a draft now.

Security

• Source passwords are no longer saved in the browser. The MQTT Subscription and External Database sources wrote their passwords to the browser's storage in plain text, where any script on the page could read them, including another plugin's page when the console runs as a plugin. A password now lasts until the page is closed or reloaded, so enter it again after a reload; one an earlier version saved is erased the next time the console opens.

Under the hood

• Two test files that failed about one run in four now wait for the key calculation they depend on, so the full test run no longer fails at random.

---

Full history: CHANGELOG.md

Installation

In the built-in Repeater interface, open System → Plugins → Catalogue, find waev:outpost, and press Install. Catalogue installation enables the plugin automatically. Confirm UI READY on the Installed tab, then use Open UI or visit /plugins/waev.outpost/ with your existing Repeater credentials.

To use waev:outpost at /, open System → Configuration → Access → Web Options → Web Frontend and select the waev:outpost plugin entry. The built-in interface applies this selection immediately.

For a direct installation, download this release's .whl, use System → Plugins → Install wheel, select the file and press Install, then Enable if disabled.

Moving from pymc_console-dist? v0.9.394 is the final legacy standalone release. Keep your existing files and Repeater configuration. In waev:outpost, use Configuration → Web Frontend → Default Frontend to return to the built-in Repeater interface, then follow the plugin installation steps. See the migration and recovery guide. No credential reset or standalone uninstall is needed.

Upgrade

For catalogue installs, use System → Plugins → Catalogue → Refresh → Update when offered, or What's new → Update in waev:outpost. A published release becomes available there only after catalogue approval.

A fresh local-wheel installation has no catalogue repository metadata, so automatic Update may be unavailable. Upload the newer wheel with Install wheel again, or use the guide's catalogue-install API to adopt the approved version. Check that version first because it may be older than a manually uploaded release. Repeater configuration and credentials remain in place.