MESHCORE_WEB_UI_Communicator_EN this is a WEB interface for the Meshcore network, with serial companion (NOW with Bluetooth also !!) LATEST - V2.3.2 => Please let a Star if you like it

What's new in V2.3.2

1. Channel management fixes

Problem: channel names/keys could get mixed up between different companion radios (e.g. sending on #banat on one radio showed as #craiova on another), and the "APPLY" button reported success even when the radio rejected the change.

Fixes:

On every new connection (USB or BLE), the channel table is now reset before querying the radio, so stale names from a previous companion or from browser cache can no longer leak through. The 🔑 (private/secured) indicator is now derived from what the currently connected radio actually reports, not from local cache alone. #name channels (auto-derived key) and the standard Public channel are now correctly recognized as non-secret and never show the 🔑 lock icon. Save now waits for radio confirmation. Applying channel keys, the diagnostic Bot channel, or the Alert Bot channel all now wait for the radio's actual acknowledgement (RESP_OK/RESP_ERR) before reporting success. If the radio rejects a channel or doesn't respond, you'll see a clear warning instead of a false "saved" message. Export / Import channels — new ⬇ EXPORT / ⬆ IMPORT buttons in the private-channels (🔑) window, to back up or transfer your channel configuration (name + key + region) as a .json file, same as the existing node export/import. 2. Node list — timing accuracy

Problem: some nodes appeared "stuck" at the top of the node list, always showing a very recent time even though they hadn't actually transmitted anything in a while.

Fixes:

Fixed a double time-conversion bug in the 30-second refresh timer that could corrupt the displayed relative time. Removed a speculative heuristic that tried to estimate "last seen" from a raw uptime counter mismatch between your own radio and a remote node. This could produce a falsely "recent" timestamp for long-uptime nodes (e.g. static repeaters). Displayed times now only come from directly observed events (a real received message/advert) or an absolute timestamp reported by the radio — never a guess. 3. Real-time Noise Floor (NF) display Added a live NF: xx dBm indicator in the waterfall header, right before the existing BW / SF / CR / channel count line. The underlying radio-stats polling interval was reduced from 90 seconds to 5 seconds, so NF/RSSI/SNR/airtime figures update much faster. 4. Block / Ignore users

Two complementary ways to block unwanted senders:

a) Direct Messages (DM) — by node identity Every node row in the left-hand list now has a 🚫 BLOCK / ✅ UNBLOCK button. Double-click any DM message bubble to open a small menu with: ↩ Reply (DM) — targets that node for your next message. 🚫 Block user / ✅ Unblock user. Incoming DMs from a blocked node are silently filtered (no popup, no sound) and only noted in the raw log as filtered. b) Channel messages — by display name

MeshCore channel/group messages carry no cryptographic sender identity — the shared channel key alone can't tell you who on the channel sent a message. Like other MeshCore clients (e.g. KiekR), this UI relies on the common Name: message convention some senders use.

If an incoming channel message matches the Name: text pattern, the name is now parsed out and shown properly as the sender in the UI (instead of just the channel name). That name becomes blockable the same way: double-click the message → 🚫 Block user, or open the 🚫 Blocked panel and type the name directly (no advert/prior contact required). Future messages starting with that name, on any channel, are filtered automatically. Limitation: if a sender doesn't prefix their messages with a name at all, there's no protocol-level way to identify or block them specifically — this applies to any MeshCore client, not just this one. Keyword-based filtering would be a separate feature if ever needed. Managing blocks New 🚫 button in the bottom send bar (next to the message box, before TX) opens the Blocked Users panel: shows everyone currently blocked (node-based and name-based), with one-click unblock, plus a manual entry field that accepts either a hex node ID or a plain display name. 5. UI layout tweaks Moved the 🚫 Blocked button out of the top toolbar (where it was overlapping the node counter) into the bottom send bar, right before the TX button. Shortened the message input placeholder from "Send message... [ENTER]" to "Message... [ENTER]" to free up space.

What's new in V2.3.1

The underlying channel-message send path was hardened: manual messages, bot replies, greetings, and alerts now correctly skip the (unsupported, on some firmware) flood-scope-key handshake on channels that don't have a region scope configured, while still using it correctly on channels that do — this fixed intermittent failed deliveries that were unrelated to the alert feature itself but affected the same send path.

Configurable map basemap

The node map and the per-node route map now use a swappable basemap provider instead of a single hardcoded tile source, since OpenStreetMap's own tile servers block this kind of app and CARTO's free tiles started requiring an API key. Open ⚙ in the map panel's header to choose:

• Esri Dark Gray Canvas (default) — free, no key needed.
• OpenTopoMap — free, no key needed, more colorful/detailed.
• CARTO — needs a free personal API key (get one at carto.com/basemaps/apikey), with a style picker (Voyager / Positron / Dark Matter). The key is stored only in your own browser and is never written into the file — if you share or publish this HTML, don't fill in your key first; each person should add their own.

Switching providers/styles applies immediately to any map that's open, no reload needed.

What's new in V2.3.1

• APRS-IS Gateway — the WebUI can now take the GPS position of your local node (from the companion's SELF_INFO, or a manually entered fixed lat/lon for GPS-less modules) and beacon it to APRS-IS on a configurable interval, so your MeshCore station also shows up as a normal APRS tracker/iGate on aprs.fi.
  • Toggle button (📡 APRS-IS) in the topbar to arm/disarm the gateway with one click; right-click (or the same button when unconfigured) opens the settings panel.
  • Settings: callsign, SSID, APRS-IS passcode (with a one-click "CALC" using the standard public passcode algorithm), server/port, APRS symbol, beacon interval, comment, and an optional fixed manual position for stations without GPS.
  • Transport is a WebSocket connection to APRS-IS's readwrite port (e.g. ametx.com:8888 secure) rather than a raw TCP socket, which browsers can't open — this still gives a real "login verified/unverified" confirmation from the server, shown in the RAW panel and in the settings dialog's Test Beacon button.
• Stop Waterfall button next to the waterfall panel — pauses the SDR-like waterfall rendering on demand (useful to save CPU/GPU when you're not watching it) without affecting the rest of the app; click again to resume.

---

Why this exists — and why it's different

This WEB UI was developed out of the need for a reliable connection when working from the shack or the office, for the convenience of using a real keyboard instead of a tiny touch display. I prefer the serial connection over Bluetooth for stability — the BLE connection is constantly interrupted by drivers, Windows, software, or the companion itself; with serial I have never had a single problem.

The single biggest advantage of this project over other MeshCore clients: zero installation. No Python, no .bat files, no scripts, no dependencies to pip install, no companion app, no server, nothing to compile or configure — just one .html file. This matters most for regular users and beginners who just want to talk on the mesh without becoming a developer first. Every other requirement (pyserial, WebSocket bridges, Electron apps, CLI tools) is one more thing that can break on someone's PC and one more reason they give up.

Using this interface is extremely simple (which is exactly why I built it):

1. Open the .html file in Chrome or Edge
2. Click Connect
3. Plug in the USB cable, pick the detected port
4. … SUCCESS!! You now have a secure, robust and efficient digital communications terminal.

If you like it, please give a star to the project.

---

Description

MeshCore WebUI — Companion Radio Interface YU\YO2LDK BaseStation KN05HQ · EU_868 / US_915

What it is

MeshCore WebUI is a complete web interface for the MeshCore radio network (open-source firmware for LoRa devices — Heltec, TTGO, RAK, Waveshare RP2040-LoRa etc.), developed and extended through an iterative process of debugging, optimization and addition of new features beyond the original version. The application runs directly in the browser (Chrome/Edge with Web Serial API) and connects via USB to the local MeshCore node, providing a full control panel for monitoring and communication across the LoRa mesh network.

Two ready-to-use builds are provided:

• EU_868 — 869.618 MHz, SF8, BW62.5, CR8
• US_915 — 910.525 MHz, SF7, BW62.5, CR5 (USA/Canada preset)

Both are the same interface; only the default radio plan differs. Frequency/SF/CR/BW/TX power can all be changed live from either build (see Radio Parameters below), so you're not actually locked into one region.

---

Main Features

Network and Nodes

• Node list with automatic sync on connect and manual refresh
• Per-node badges: direct (green), 2 rpt / 3 rpt (amber), prop (blue — flood propagation), RPT (purple — MeshCore repeater)
• Persistent hop count — the repeater count is saved and does not disappear on new adverts
• Detailed info: SNR, RSSI, uptime, battery, GPS coordinates, full TRACE route
• Leaflet map with markers for GPS-equipped nodes, automatic cleanup of orphaned markers
• TXT export with all nodes, TRACE routes, signal statistics, Google Maps link per node
• JSON export/import for node list backup and restore

Messaging with per-channel tabs

• Dynamic tabs above the message area: ALL · SYS · DM · CH0–CH13 · private channels
• Bidirectional sync tab ↔ TX selector — changing the tab automatically changes the TX channel and vice versa
• Unread message badge (red) per tab
• Public channels + 6 private channel slots with AES-128 key
• Direct Messages (DM) with node selector and ACK delivery confirmation
• Message history with JSON/CSV export, previous session restore

Automatic bot on private channel

• Bot configurable on any private channel with AES-128 key
• Configurable keyword from the UI (default: cq) — automatically responds to the keyword
• Auto-response includes: RSSI, SNR, Noise floor, hop count, route, uptime, battery, UTC time
• Anti-flood cooldown (8 seconds between responses)
• Ignores own TX messages (anti-echo)

Radio Parameters — live SF / CR / BW / Frequency / TX Power

A dedicated 📻 RADIO panel lets you change the radio's operating parameters directly from the browser, no firmware reflash needed:

• Frequency, Bandwidth, Spreading Factor (SF7–SF12), Coding Rate (CR5–CR8), TX Power
• One-click EU_868 and USA/Canada presets
• Sends the real CMD_SET_RADIO_PARAMS (11) + CMD_SET_RADIO_TX_POWER (12) companion commands and waits for the device's actual RESP_OK/RESP_ERR before confirming success — no blind "it probably worked"
• One-click 🔁 Reboot Device (CMD_REBOOT, 19): MeshCore firmware persists new radio parameters to NodePrefs but only applies them to the live radio after a reboot — the panel reminds you and can trigger it directly
• Field-tested: switching a EU_868 node live to the US_915 preset and rebooting correctly moved it off 868 MHz and onto 915 MHz

Region Scope — real per-channel flood filtering

Not just a label: this sends the actual companion-protocol command (CMD_SET_FLOOD_SCOPE_KEY, code 54) that MeshCore repeaters use to decide whether to relay a flood packet.

• Click the 🌐 button next to the channel selector (or set it per-slot in the 🔑 Private Channel panel — both are kept in sync) and type a region name, e.g. ro-cs
• The region key is derived exactly the way the firmware does it: the first 16 bytes of SHA-256("#" + region name) (verified against MyMesh.cpp and the independent meshcore-decoder library)
• Right before sending a message on a scoped channel, the WebUI: sets the flood-scope key on the device → sends the message → clears the override back to the device's default, all with RESP_OK/RESP_ERR confirmation at each step (visible in the RAW panel)
• Only repeaters that are themselves configured for the same region (region put <name> / region allowf <name> on the repeater's own CLI) will forward that message — everyone else silently drops it. This is genuine network-level segmentation, not client-side filtering.
• Requirements: companion firmware v12+ (MeshCore v1.15.0+) with region support. Leave the field blank for classic, unscoped flood (reaches the whole mesh, as before).

APRS-IS Gateway

Turns your local MeshCore station into an APRS position beacon, visible on aprs.fi, without any extra hardware or software:

• Reads the GPS fix from the connected companion (SELF_INFO); for fixed/GPS-less nodes, a manual lat/lon override can be set instead
• Builds a standard APRS position packet and sends it on a configurable interval (default 10 min)
• Connects via APRS-IS's WebSocket "readwrite" port rather than a raw TCP socket (browsers can't open those) — still gets a genuine "verified"/"unverified" login response back from the server, shown in the RAW log
• One-click enable/disable from the topbar; settings (callsign, SSID, passcode, server/port, symbol, comment, interval, manual position) live in a dedicated panel with a "CALC" passcode helper and a "Test Beacon" button
• Requires your own licensed callsign and APRS-IS passcode

Map and SDR-like waterfall

• Interactive Leaflet map with GPS nodes
• Real-time waterfall spectrum, tracking the live frequency/SF/BW/CR shown in the header (updates instantly if you change Radio Parameters)
• Stop/Resume Waterfall button to pause the rendering on demand (saves CPU/GPU) without affecting the rest of the app
• TRACE route visualized graphically on the map

Configuration

• 3 themes: Dark · Slate · Light
• Private channels: 6 slots with name, index, AES-128 key (32 hex chars) and optional region scope
• BOT panel: channel, name, keyword, AES key, random key generator button
• WX weather: configurable weather station with data display
• Radio panel: frequency / bandwidth / SF / CR / TX power, with EU_868 and USA/Canada presets
• APRS-IS Gateway panel: callsign/SSID/passcode, server/port, symbol, interval, comment, manual position override

Monitoring

• SERIAL RAW with filtering and search — every command sent and every RESP_OK/RESP_ERR reply is visible here, useful for verifying Radio Parameters and Region Scope actually landed, and for confirming APRS-IS login/delivery status
• SNR/RSSI/Noise in real time in the bottom status bar
• Uptime, battery, firmware errors displayed in the topbar
• Ping/Trace with time measurement and full route display

---

Technical Requirements

• Browser: Chrome or Edge (Web Serial API — does not work in Firefox)
• Connection: USB to the local MeshCore node (Heltec V3, TTGO LoRa32, Waveshare RP2040-LoRa etc.)
• Firmware: MeshCore v11+ (v1.15.0+) — v12+ recommended if you want to use Region Scope
• Band: EU_868 (869.618 MHz, SF8, BW62.5, CR8) or US_915 (910.525 MHz, SF7, BW62.5, CR5) out of the box — changeable live from the Radio panel
• File: a single .html file — no installation, no server, no external dependencies
• APRS-IS Gateway (optional): a licensed amateur radio callsign and your own APRS-IS passcode

The YU/YO CS (Caraș-Severin Romania) Network The interface was developed and tested within the active MeshCore network of Caraș-Severin County, Romania, with active nodes at:

ROU-CS-SemenicMt-N / SE — repeater on Semenic Peak * TNX YO2LYN - STEFAN ! * 🌍 RS-Vojvodina-01 and 🌍 RS-Vojvodina-02 NW — cross-border repeater, Serbia ROU-CS-Resita-Bot — node with active bot YU\YO2LDK BaseStation KN05HQ — local base station

The network currently counts 777+ active nodes across the Western Balkans region, and continues to grow.

Developed by YO2LDK · MeshCore EU_868 · May 2026 · SDR-like waterfall interface, animated background mesh network, and many bugs removed — none of it would have been possible without AI help.