2025-10-14 - 2026-10-14
Overview
53 Pull requests merged by 1 user
Merged
#57 Remove insecure NODE_TLS_REJECT_UNAUTHORIZED=0 TLS workaround (follow-up to #56)
Merged
#56 Drive MeshService through the MeshMonitor HTTP gateway (Phase 2)
Merged
#55 Ignore 0% battery readings in low-battery alerting
Merged
#54 fix(notifier): migrate opencode notifier to v2 routes (v0.21.11)
Merged
#53 Container TZ: Europe/Warsaw so cron hours are local (v0.21.10)
Merged
#52 Add #loser command — worst packet delivery record (v0.21.9)
Merged
#51 Fix unhandled ECONNRESET in fake-bridge teardown — npm test exits 0 again (v0.21.8)
Merged
#50 Fix double ScheduleModule.forRoot() — all cron jobs fired twice (v0.21.7)
Merged
#49 Add #help command with short list of all commands (v0.21.6)
Merged
#48 Space multi-line command replies 5 s apart (v0.21.5)
Merged
#47 LLM timeout default 60 s → 180 s (v0.21.4)
Merged
#46 Reconnect tuning: 1 min idle timeout + 5 min periodic autoreconnect (v0.21.3)
Merged
#45 Watchdog: track decoded frames, not raw bytes (v0.21.2)
Merged
#44 Bridge idle watchdog + forced reconnect (v0.21.1)
Merged
#43 #rss get: 3-5 separate messages with short headers (v0.21.0)
Merged
#42 Cap #rss get summaries to one mesh packet (v0.20.1)
Merged
#41 Add #rss command family with LLM tags and summaries (v0.20.0)
Merged
#40 Add OpenAI-compatible LLM client service (v0.19.0)
Merged
#39 Route command replies through respond() — same channel, threaded quote (v0.18.1)
Merged
#38 v0.18.0: channel-2 auto-responder with extensible #command boilerplate
Merged
#37 Multi-channel notify gate + ch0 DM-only filtering (v0.17.0)
Merged
#36 v0.15.0+v0.16.0: /api/respond reply endpoint + message-id in notifier wrapper, GET /api/forwarded ring
Merged
#35 v0.14.0 — in-process opencode notifier replaces the forwarder service
Merged
#34 Battery alerts → testowy channel (ch2) — v0.13.1
Merged
#33 v0.13.0 — battery-low alert module (merged broadcasts, @mentions, cooldown)
Merged
#32 MESHTASTIC.md: questions get their answer on the channel (owner standing rule)
Merged
#31 Optional replyId on send (API + MCP) — protocol-level threaded replies
Merged
#30 MESHTASTIC.md: back to channel-only replies (no DMs)
Merged
#29 MESHTASTIC.md: reply to senders as DMs; always respond before starting work
Merged
#28 Forwarder: resolve opencode workspace/session dynamically per request
Merged
#27 Retry notify webhook POST with backoff (2 s / 10 s / 30 s) before dropping
Merged
#26 Run notify forwarder as a compose service (host networking, restart policy)
Merged
#25 Fix weather module DI (MeshService export + value import) and pass WEATHER_CRON through compose
Merged
#24 Hourly cron weather report for Lublin (Open-Meteo) broadcast on mesh
Merged
#23 Add MESHTASTIC.md communication rules + AGENTS.md mention
Merged
#22 Self-echo filter for notify webhook (skip own-node messages)
Merged
#21 Notify webhook also fires for injected messages (channel match) + compose env passthroughs
Merged
#20 Outbound notification webhook (MESH_NOTIFY_URL) on RX text — issue #17
Merged
#19 Persist message history to SQLite with 1s poller (#15)
Merged
#18 Inbox injection endpoint: POST /api/messages + MCP inject_message (#12)
Merged
#16 Telemetry stream: GET /api/telemetry + MCP get_telemetry
Merged
#14 Fix BigInt serialization in GET /api/device (500 on real hardware)
Merged
#13 Device info endpoint + richer node summaries (GET /api/device, MCP device_info)
Merged
#11 MCP server at POST /mcp (official SDK, stateless Streamable HTTP)
Merged
#10 Publish on 'test' channel (index 3) by default
Merged
#9 Send to by node name or broadcast sentinel (GET-free resolution via node DB)
Merged
#8 Message history with delivery tracking (GET /api/messages)
Merged
#7 Node database: collect nodes during sync, expose GET /api/nodes
Merged
#6 Send want_config_id on connect to trigger initial sync
Merged
#5 feat: pin sends to testowy channel (index 2), never primary (v0.1.3)
Merged
#4 ci: Gitea Actions test pipeline (v0.1.2)
Merged
#3 fix: bridge port is 4403, not 4003 (v0.1.1)
Merged
#2 feat: /api/channels endpoint, /api namespace, Scalar at root (v0.1.0)
4 Issues closed from 1 user
Closed
#17 After message send to channel 3 - test trigger simple information send to opencode that inform there was message (with this message content) and that he should react to it.
Closed
#15 Add sqlite database on system and add frequent pooling (1s? configurable) of messages to this database.
Closed
#12 Add a endpoint that will send message to you - we will later use it to trigger communication from external source.
Closed
#1 make endpoint /api/channels that wil show meshtastic chanels
4 Issues created by 0 users
Opened
#1 make endpoint /api/channels that wil show meshtastic chanels
Opened
#12 Add a endpoint that will send message to you - we will later use it to trigger communication from external source.
Opened
#15 Add sqlite database on system and add frequent pooling (1s? configurable) of messages to this database.
Opened
#17 After message send to channel 3 - test trigger simple information send to opencode that inform there was message (with this message content) and that he should react to it.