MeshCore

Commit Graph

Author	SHA1	Message	Date
Che177	5a04e060a5	room_server: use standard mesh debug logging	4 days ago
Che177	3a9f19c14b	room_server: add room.post system posts	5 days ago
liamcottle	dd778e2189	fix bluetooth toggle on ui tiny	5 days ago
liamcottle	203fd4e407	refactor rak13800 to new ethernet interface class	5 days ago
liamcottle	e672679d6e	refactored companion interfaces to allow for multiple active connection modes	2 weeks ago
liamcottle	b4143a4402	rename class	2 weeks ago
liamcottle	5de857f8f8	initial ch390 ethernet support for thinknode m7 companion	2 weeks ago
Scott Powell	f83ad03e5e	* T114 display fix	1 week ago
Scott Powell	56274db4ad	* build fixes for old ESP32 boards	1 week ago
Scott Powell	b8504e55c6	* refactor of Color mapping in UITasks / DisplayDrivers * color displays now with a new light theme	2 weeks ago
agessaman	a71cc23854	fix(room_server): support RX boosted gain The room server never supported RX boosted gain, while the repeater does. Three consequences on SX1262/SX1268 boards: - boosted gain was never applied to the radio at boot, so a room server ran in power-saving RX mode while an identical repeater ran boosted - a real receive-sensitivity difference with nothing pointing at it - _prefs.rx_boosted_gain was never initialised (the prefs are memset to 0 before defaults are set), so it defaulted to off - 'set radio.rxgain on' replied "Error: unsupported" but CommonCLI had already written the value to prefs and saved them, so a stale setting survived reboot and was never applied Mirror the repeater's implementation: initialise the pref default under the same USE_SX1262/USE_SX1268 and SX126X_RX_BOOSTED_GAIN guards, apply it during radio init, and override setRxBoostedGain() so the CLI reports success and takes effect. Built Heltec_v3_room_server (SX1262) and LilyGo_T3S3_sx1276_room_server (guards compile out cleanly).	2 weeks ago
ViezeVingertjes	3b69e7873b	fix: guard HWCDC serial config behind ARDUINO_USB_MODE setTxTimeoutMs() and setTxBufferSize() are HWCDC-only APIs; calling them on HardwareSerial (UART-bridge boards like T-Beam) fails to compile. Co-Authored-By: Adam Gessaman <[email protected]>	1 month ago
ViezeVingertjes	fb2c61f862	fix: prevent ESP32 KISS modem stalls under USB backpressure Switch ESP32-S3 KISS modem environments to HWCDC and move outbound KISS writes to a non-blocking queued frame path so loop() and TX completion keep progressing when the host reads slowly. Add native backpressure regression tests and correct the native_kiss_modem test filter so this suite runs directly with pio test.	1 month ago
Scott Powell	a0b52be4ad	* RP2040 build fixes * new prefs file now "/prefs.json"	2 weeks ago
Scott Powell	2189f2294c	* added prefs initialisers to match original zeroed state	2 weeks ago
Florent	c644720ea7	uitask: screen and radio poweroff moved to board	2 weeks ago
Quency-D	b26f53a263	Avoid waking display from rotary input	2 weeks ago
Scott Powell	f515716032	* new NodePrefs for companion	2 weeks ago
Quency-D	05d4bd2f7f	Add a rotary encoder	2 weeks ago
Jaroslav Škarvada	15e259c572	Added MCU temp sensor to the companion Fixes #2896	4 weeks ago
Scott Powell	2af1e6d099	* first draft of new ConfigSerializer. (simple embedded JSON prefs)	3 weeks ago
Quency-D	4d0ba1516c	Remove the watchdog feeding operation from each iteration of the loop to reduce power consumption.	3 weeks ago
Florent	3ee2f77877	restore display and radio poweroff in ui	4 weeks ago
Florent	2efb3af69b	repeater: poweroff on long press	4 weeks ago
Kevin Le	7d7de88707	board->powerOff() is sufficient to power off radio, display, GPS and components	4 weeks ago
Neil Alexander	0d7379520f	Fix `recv_pkt_region` incorrect usage The `recv_pkt_region` is set when processing a flood packet in `filterRecvFloodPacket` but direct/non-flood packets would never pass through that function, so the pointer was not cleared for them. `sendFloodReply` would then later use it blindly, which meant that the response would either inherit the region from the last flood packet, or refer to a non-initialised pointer if no region floods had been received yet.	1 month ago
taco	1f9bb67400	return bool when setting rx boost	1 month ago
taco	5d0ff7fe6e	remove guard on MyMesh::setRxBoostedGain()	1 month ago
Wessel Nieboer	7c8e092457	Have CAD be a separate toggle (set cad on/off)	2 months ago
Wessel Nieboer	4f9a091671	Use hardware channel activity detection for checking interference	5 months ago
Scott Powell	2e73fe948e	* fix for anon lastmod	2 months ago
Scott Powell	07648e3344	* fix for anon contacts when full	2 months ago
Quency-D	5300fa18c7	Restore companion NodePrefs file ending	2 months ago
Quency-D	3ee58fd2e3	Remove companion FEM RX gain command IDs	2 months ago
liamcottle	ae0bb7ee95	use releasePacket instead of _mgr->free	2 months ago
liamcottle	07bfe90695	free packet on parse failure	2 months ago
Scott Powell	8c0d5c5b24	* version 1.16.0	2 months ago
Scott Powell	8fc2da5c98	* default now 8, per the will of the peoples.	2 months ago
Scott Powell	5f6821bb66	* new CLI config: flood.max.advert (default 16)	2 months ago
Sefinek	cc05ae555a	docs: fix typos, grammar, and formatting in FAQ and code comments	2 months ago
taco	e449af1723	bypass auto-shutdown delay for e-ink devices	2 months ago
Scott Powell	83ad3a6dc0	* direct/zero hop by default	2 months ago
Scott Powell	f66c1d0258	* simplified the new flood.max.unscoped pref	2 months ago
Chris Barker	a33f3011a5	Feat: Adds flood.max.unscoped setting Before this commit, there was no way to set a different max hop count for unscoped messages. Now with this change, by defaul it tracks the flood.max setting, until a user provides a flood.max.unscoped value, which tax precidence for packets if ROUTE_TYPE_FLOOD is true.	2 months ago
taco	3ce1cf404e	NRF52: disable autoshutdown if powered, add auto-shutdown warning for oled	2 months ago
Scott Powell	760bb5951d	* Bug fix: adding neighbor when path_mode != 0	2 months ago
Scott Powell	bc5d648204	* contacts sync fix * fix for reusing transient/anon contacts only	2 months ago
Scott Powell	d9df8307ca	* first draft	2 months ago
Scott Powell	b259fbd01b	* power saving: hasPendingWork() now also checks if there's a pending contacts write	2 months ago
Kemal Hadimli	bb781ff10a	companion_radio: opt-in KEEP_DISPLAY_ON_USB to keep OLED on while powered AUTO_OFF_MILLIS is a power-save feature aimed at battery use. When the board reports isExternalPowered() == true (USB or other DC source), blanking the screen serves no purpose — there's nothing to conserve. But OLEDs are vulnerable to burn-in with static content, so this behaviour is gated behind a new build flag KEEP_DISPLAY_ON_USB. Default is unchanged from upstream — the display blanks after AUTO_OFF_MILLIS on USB or battery. Variants that ship with an LCD instead of an OLED (e.g. heltec_t096) can opt in by adding -D KEEP_DISPLAY_ON_USB to their env, gaining always-on-while-powered without exposing OLED users to burn-in risk. When the flag is enabled, the implementation refreshes _auto_off every loop iteration while externally powered, so the timer naturally counts a fresh AUTO_OFF_MILLIS window from the moment power is removed — no instantaneous-blank-on-unplug. Applied to all three companion_radio UI flavours (ui-new, ui-tiny, ui-orig). Boards without an isExternalPowered() override use the base-class default in MeshCore.h (returns false), so battery-powered behaviour is unchanged everywhere. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>	2 months ago

1 2 3 4 5 ...

937 Commits (dev)