v1.11.0

What's New in v1.11.0

🌤️ Weather API

Live weather data from AWEKAS or Weather Underground can now be fed directly into the telemetry JSON file and transmitted as MeshCom telemetry fields.

• Configure provider, station ID and API key under Settings → 🌤️ Weather API
• Configurable poll interval (minimum 5 minutes)
• Simulation provider for offline testing – no API key required
• Fixed field names (temp_out, humidity_out, pressure_rel, …) map directly to the Telemetry Mapping
• Bot command --weather reports provider, latest values and timestamp
• Weather API and HTTP Telemetry API are mutually exclusive (they share the same telemetry JSON file)

🖥️ NET Console – no-password support

The NET Console now connects successfully even when no password is set on the MeshCom node.
Previously, a direct OK response (without HMAC challenge) was incorrectly treated as an error.

💬 New messages divider

A visible divider line "New messages" is inserted in the chat tab when new messages arrive since the last read (DE/EN).

☕ Buy Me a Coffee

Added as a donation option alongside PayPal in the About page and welcome dialog.

---

🔐 Bug Fixes

• AWEKAS API key URL encoding – AWEKAS displays the key URL-encoded in the portal (%2B, %2F, %3D); now automatically decoded before the API call
• Weather API – settings persistence – WeatherApi block was missing from serialization; settings were not saved across restarts
• Weather API – API key decryption – key was encrypted on save but not decrypted on load; DecryptMeshcomSettingsPostConfigure corrected
• Double encryption prevented – aes:/dp: prefix is detected; already encrypted values are not encrypted again
• API key field empty on load – password/key fields are never pre-filled; saving with an empty field preserves the existing encrypted value
• Build no longer overwrites runtime data – data/** is excluded from build output copy; runtime files survive rebuilds
• Speaker icon – state preserved after chat page reload

---

Full Changelog: v1.10.3...v1.11.0