10171 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Jonathan Bennett	1c1c0cc791	Portduino config refactor (#7796) ... * Start portduino_config refactor * refactor GPIOs to new portduino_config * More portduino_config work * More conversion to portduino_config * Finish portduino_config transition * trunk * yaml output work * Simplify the GPIO config * Trunk	2025-09-03 17:50:26 -05:00
renovate[bot]	a0c0388dd9	chore(deps): update meshtastic/device-ui digest to 10f0244 (#7840) ... Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-09-03 13:00:08 -05:00
Ben Meadors	789c1ab59d	Merge branch 'master' into develop	2025-09-03 07:02:05 -05:00
github-actions[bot]	e8367894f2	Upgrade trunk (#7835) ... Co-authored-by: vidplace7 <1779290+vidplace7@users.noreply.github.com> Co-authored-by: Ben Meadors <benmmeadors@gmail.com>	2025-09-03 06:45:14 -05:00
Manuel	8aae4f1b9d	Update device-install scripts for T-LoRa Pager (#7833) ... * add tlora-pager to device install scripts + fixes * replace deprecated commands (write_flash)	2025-09-03 06:22:57 -05:00
Daniel.Cao	5850a7cd6b	Add RAK WisMesh Tap V2 (ESP32S3) Hardware Variant (#7741) ... * Add initial variant and platformio configuration for RAK WISMESHTAP V2 * Add initial variant and platformio configuration for rak wismesh tap v2 * Remove unnecessary Meshtastic build flags from rak_wismesh_tap_v2 configuration * Enable LGFX button support in rak_wismesh_tap_v2 configuration * Revert "Enable LGFX button support in rak_wismesh_tap_v2 configuration" This reverts commit 2bd2c1a03b. --------- Co-authored-by: Daniel.Cao <daniel.cao@rakwireless.com>	2025-09-03 06:20:19 -05:00
Jonathan Bennett	6c89ea7cee	chore(deps): update platform-native digest to c490bcd (#7814) (#7832) ... Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-09-03 06:16:00 -05:00
github-actions[bot]	8a8f60d129	Update protobufs (#7831) ... Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com>	2025-09-02 19:08:05 -05:00
renovate[bot]	b59409bec0	chore(deps): update caveman99-stm32-crypto digest to 1aa30eb (#7808) ... Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-09-02 18:01:31 -05:00
renovate[bot]	c66125114f	chore(deps): update meshtastic/device-ui digest to 8019704 (#7830) ... Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-09-02 16:17:00 -05:00
renovate[bot]	edb7ec58c6	chore(deps): update platform-native digest to c490bcd (#7814) ... Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>	2025-09-02 11:58:57 -05:00
Ben Meadors	655c6b51fe	Try-fix Cardkb detection (#7825) ... * Try-fix: CardKB detection regression * Correct macro	2025-09-02 09:50:15 -05:00
Chloe Bethel	0bd4cefad3	Make ExternalNotification show up in excluded_modules, more STM32 modules (#7797) ... * Show ExternalNotification as excluded if it is * Enable ExternalNotification, SerialModule and RangeTest on STM32WL * Misc fixes for #7797 - ARCH_STM32 -> ARCH_STM32WL, use less flash by dropping weather station support for serialmodule, set tx/rx pins before begin * Enable Serial1 on RAK3172, make SerialModule use it (console is on LPUART1) * Fix SerialModule on RAK3172, fix board definition of RAK3172 to include the right pin mapping.	2025-09-02 07:09:15 -05:00
Chloe Bethel	0952007805	Make ExternalNotification show up in excluded_modules, more STM32 modules (#7797) ... * Show ExternalNotification as excluded if it is * Enable ExternalNotification, SerialModule and RangeTest on STM32WL * Misc fixes for #7797 - ARCH_STM32 -> ARCH_STM32WL, use less flash by dropping weather station support for serialmodule, set tx/rx pins before begin * Enable Serial1 on RAK3172, make SerialModule use it (console is on LPUART1) * Fix SerialModule on RAK3172, fix board definition of RAK3172 to include the right pin mapping.	2025-09-02 07:08:57 -05:00
github-actions[bot]	9b1fb795d7	Upgrade trunk (#7822) ... Co-authored-by: vidplace7 <1779290+vidplace7@users.noreply.github.com>	2025-09-02 06:41:48 -05:00
Tom Fifield	3040e5a7bb	Fix GPS that hard code 2080 as the start time. (#7803) ... * Fix GPS that hard code 2080 as the start time. Some GPS chips, such as the AG3335 in T1000e and L96 have a hardcoded time of 2080-01-05 when they start up. To fix that in a way that seems permanent, let's ignore times that are more than 40 years since the firmware was built. We should followup in late 2039 to see if any changes are needed. Reported-By: @b8b8 * Update src/gps/RTC.cpp Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Put FORTY_YEARS in header and use in both places. * Restore Ben's nicer log lines. --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>	2025-09-02 06:41:26 -05:00
Tom Fifield	7612799ef6	Fix GPS that hard code 2080 as the start time. (#7803) ... * Fix GPS that hard code 2080 as the start time. Some GPS chips, such as the AG3335 in T1000e and L96 have a hardcoded time of 2080-01-05 when they start up. To fix that in a way that seems permanent, let's ignore times that are more than 40 years since the firmware was built. We should followup in late 2039 to see if any changes are needed. Reported-By: @b8b8 * Update src/gps/RTC.cpp Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Put FORTY_YEARS in header and use in both places. * Restore Ben's nicer log lines. --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>	2025-09-02 06:40:59 -05:00
Ben Meadors	3b82d55176	Revert "Add gat562_mesh_tracker_pro device. (#7815)" (#7824) ... This reverts commit 7d1300ab66.	2025-09-02 06:17:01 -05:00
Tom Fifield	a6b8202cd4	Hold for 20s after GPS lock (#7801) ... * Hold for >20s after GPS lock GPS chips are designed to stay locked for a while to download some data and save it. This data is important for speeding up future locks, and making them higher quality. Our present configuration could make every lock perform similar to first lock. This patch sets a hold of between 20s and 10% of the lock search time after lock is acquired. This should allow the GPS to finish its work before we turn it off. Fixes https://github.com/meshtastic/firmware/issues/7466 * Remove T1000E-specific GPS holds The new code does the same thing, for all devices. * Fix publishing settings * Cleanups, removing unused variables. * ifdef log line with GPS_DEBUG * fixQual is not a bool.	2025-09-02 06:06:06 -05:00
Jason P	cfc1bf10c9	If usePreset is False, show value as Custom (#7812)	2025-09-02 06:05:55 -05:00
Tom Fifield	c5fad6cca1	Hold for 20s after GPS lock (#7801) ... * Hold for >20s after GPS lock GPS chips are designed to stay locked for a while to download some data and save it. This data is important for speeding up future locks, and making them higher quality. Our present configuration could make every lock perform similar to first lock. This patch sets a hold of between 20s and 10% of the lock search time after lock is acquired. This should allow the GPS to finish its work before we turn it off. Fixes https://github.com/meshtastic/firmware/issues/7466 * Remove T1000E-specific GPS holds The new code does the same thing, for all devices. * Fix publishing settings * Cleanups, removing unused variables. * ifdef log line with GPS_DEBUG * fixQual is not a bool.	2025-09-02 06:05:14 -05:00
Jason P	b8d7222423	If usePreset is False, show value as Custom (#7812)	2025-09-02 05:55:57 -05:00
Wilson	7d1300ab66	Add gat562_mesh_tracker_pro device. (#7815)	2025-09-02 13:06:24 +08:00
github-actions[bot]	16d7de5989	Upgrade trunk (#7804) ... Co-authored-by: vidplace7 <1779290+vidplace7@users.noreply.github.com>	2025-09-02 14:53:05 +10:00
Onyx Clawe	102c447fe3	Update variant.h (#7520) ... Updated ADC, Full charge now results in 100% charge being reported instead of 95% charge Co-authored-by: OnyxtheDragon <58921814+OnyxtheDragon@users.noreply.github.com>	2025-09-02 14:31:41 +10:00
Manuel	d66665b96e	fix: T-LoRa Pager / T-Deck Pro shutdown (#7792) ... * power down during LS and shutdown * fix T-Deck Pro shutdown * use device specific define * slightly rephrase the power off display message	2025-09-02 14:31:41 +10:00
Tom Fifield	088be6bf6a	Fix device-install.bat baud rate (master --> develop) (#7816) ... * Upgrade trunk (#7763) Co-authored-by: vidplace7 <1779290+vidplace7@users.noreply.github.com> * Fix device-install.bat baud rate As reported by @gruberaaron , work to improve the 1200bps reset for esptool caused all runs of device-install.bat to use 1200bps as the baud rate. This change removes the general SET "ESPTOOL_BAUD=1200" that was causing the issues and places the baud settings for reset mode inside the conditional. Fixes https://github.com/meshtastic/firmware/issues/7172 --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: vidplace7 <1779290+vidplace7@users.noreply.github.com>	2025-09-02 14:22:48 +10:00
Jonathan Bennett	bd3cbfc1ad	Add support for the RV-3028 on native Linux (#7802)	2025-09-01 08:04:04 -05:00
github-actions[bot]	fddc4e00ca	Automated version bumps (#7790) ... Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com>	2025-09-01 08:03:03 -05:00
github-actions[bot]	5f7eec5504	Upgrade trunk (#7804) ... Co-authored-by: vidplace7 <1779290+vidplace7@users.noreply.github.com>	2025-09-01 07:58:01 -05:00
Manuel	6b94c297b9	fix: T-LoRa Pager / T-Deck Pro shutdown (#7792) ... * power down during LS and shutdown * fix T-Deck Pro shutdown * use device specific define * slightly rephrase the power off display message	2025-09-01 07:57:49 -05:00
Onyx Clawe	edeb25cab5	Update variant.h (#7520) ... Updated ADC, Full charge now results in 100% charge being reported instead of 95% charge Co-authored-by: OnyxtheDragon <58921814+OnyxtheDragon@users.noreply.github.com>	2025-09-01 07:57:15 -05:00
Tom Fifield	44688e8363	Fix device-install.bat baud rate (#7486) ... As reported by @gruberaaron , work to improve the 1200bps reset for esptool caused all runs of device-install.bat to use 1200bps as the baud rate. This change removes the general SET "ESPTOOL_BAUD=1200" that was causing the issues and places the baud settings for reset mode inside the conditional. Fixes https://github.com/meshtastic/firmware/issues/7172	2025-09-01 14:16:24 +10:00
Jonathan Bennett	ca79760372	Add support for the RV-3028 on native Linux (#7802)	2025-08-31 21:08:58 -05:00
Wilson	4a669032dc	Change user button to cancel button on meshtiny. (#7789)	2025-08-30 08:37:18 +08:00
github-actions[bot]	b53dd2ec90	Automated version bumps (#7790) ... Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com>	2025-08-29 19:27:14 -05:00
github-actions[bot]	5ae4ff9162	Upgrade trunk (#7763) ... Co-authored-by: vidplace7 <1779290+vidplace7@users.noreply.github.com>	2025-08-29 13:59:40 -05:00
Ben Meadors	a0e14439cb	Merge pull request #7785 from meshtastic/master ... Backmerge	2025-08-29 13:59:19 -05:00
github-actions[bot]	ed394f5f9d	Update protobufs (#7784) ... Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com>	2025-08-29 13:58:32 -05:00
Tom Fifield	11db6d4dcc	Can't trust RTCs to tell the time. (#7779) ... Further to https://github.com/meshtastic/firmware/pull/7772 , we discovered that some RTCs have hard-coded start times well in the past. This patch gives RTCs the same treatment as GPS - if the time is earlier than BUILD_EPOCH, we don't use it. Fixes #7771 Fixes #7750	2025-08-29 13:23:14 -05:00
Tom Fifield	10c6836263	Can't trust RTCs to tell the time. (#7779) ... Further to https://github.com/meshtastic/firmware/pull/7772 , we discovered that some RTCs have hard-coded start times well in the past. This patch gives RTCs the same treatment as GPS - if the time is earlier than BUILD_EPOCH, we don't use it. Fixes #7771 Fixes #7750	2025-08-29 13:22:23 -05:00
Ben Meadors	4e03df5ea7	Fix freetext hang (#7781) ... * Fixed freetext hangs by adding canned modules back to self-sourced packets and transition to SENDING_ACTIVE state * Update meshmodule handling	2025-08-29 12:09:22 -05:00
Ben Meadors	9b41131af8	Backmerge (#7782) ... * Merge pull request #7777 from meshtastic/create-pull-request/bump-version Bump release version * Only send Neighbours if we have some to send. (#7493) * Only send Neighbours if we have some to send. The original intent of NeighborInfo was that when a NeighbourInfo was sent all of the nodes that saw it would reply with NeighbourInfo. So, NeighbourInfo was sent even if there were no hop-zero nodes in the NodeDB. Since 2023, when this was implemented, our understanding of running city-wide meshes has improved substantially. We have taken steps to reduce the impact of NeighborInfo over LoRa. This change aligns with those ideas: we will now only send NeighborInfo if we have some neighbors to contribute. The impact of this change is that a node must first see another directly connected node in another packet type before NeighborInfo is sent. This means that a node with no neighbors is no longer able to trigger other nodes to broadcast NeighborInfo. It will, however, receive the regular periodic broadcast of NeighborInfo, and will be able to send NeighborInfo if it has at least 1 neighbor. * Include all the things * AvOid memleak * We don't gotTime if time is 2019. (#7772) There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750 --------- Co-authored-by: Tom Fifield <tom@tomfifield.net>	2025-08-29 10:31:55 -05:00
Wilson	fb34dac08d	Add On-Screen Keyboard for UpDown Encoder and Rotary Encoder. (#7762) ... * Add On-Screen Keyboard for UpDownInterrupt. Pls notice the new keyboard layout was inspired and adviced by https://github.com/csrutil * Add longPress event for RotaryEncoder Press. * Update UpdownInterrupt UP and DOWN on main UI. * Change the interrupt trigger mode from rising edge to falling edge to improve button response.	2025-08-29 23:26:27 +08:00
Tom Fifield	d3e3a91096	We don't gotTime if time is 2019. (#7772) ... There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750	2025-08-29 09:09:13 -05:00
Tom Fifield	5f8503c62d	We don't gotTime if time is 2019. (#7772) ... There are certain GPS chips that have a hard-coded time in firmware that they will return before lock. We set our own hard-coded time, BUILD_EPOCH, that should be newer and use the comparison to not set a bad time. In https://github.com/meshtastic/firmware/pull/7261 we introduced the RTCSetResult and improved it in https://github.com/meshtastic/firmware/pull/7375 . However, the original try-fix left logic in GPS.cpp that could still result in broadcasting the bad time. Further, as part of our fix we cleared the GPS buffer if we didn't get a good time. The mesh was hurting at the time, so this was a reasonable approach. However, given time tends to come in when we're trying to get early lock, this had the potential side effect of throwing away valuable information to get position lock. This change reverses the clearBuffer and changes the logic so if time is not set it will not be broadcast. Fixes https://github.com/meshtastic/firmware/issues/7771 Fixes https://github.com/meshtastic/firmware/issues/7750	2025-08-29 09:08:33 -05:00
Tom Fifield	b0e8321514	Only send Neighbours if we have some to send. (#7493) ... * Only send Neighbours if we have some to send. The original intent of NeighborInfo was that when a NeighbourInfo was sent all of the nodes that saw it would reply with NeighbourInfo. So, NeighbourInfo was sent even if there were no hop-zero nodes in the NodeDB. Since 2023, when this was implemented, our understanding of running city-wide meshes has improved substantially. We have taken steps to reduce the impact of NeighborInfo over LoRa. This change aligns with those ideas: we will now only send NeighborInfo if we have some neighbors to contribute. The impact of this change is that a node must first see another directly connected node in another packet type before NeighborInfo is sent. This means that a node with no neighbors is no longer able to trigger other nodes to broadcast NeighborInfo. It will, however, receive the regular periodic broadcast of NeighborInfo, and will be able to send NeighborInfo if it has at least 1 neighbor. * Include all the things * AvOid memleak	2025-08-28 18:45:46 -05:00
Jason P	dd2f77ea0c	BaseUI Show/Hide Frame Functionality (#7382) ... * Rename System Frame (from Memory) in code base * Create menu options to Show/Hide frames: Node Lists, Bearings, Position, LoRa, Clock and Favorites frames * Move Region Picker into submenu * Tweak wording for Send Position vs Node Info if the device has GPS	2025-08-28 11:23:24 -05:00
Ben Meadors	6c7cff7de2	Merge pull request #7777 from meshtastic/create-pull-request/bump-version ... Bump release version	2025-08-28 06:04:37 -05:00
Ben Meadors	46f797c40d	Merge pull request #7777 from meshtastic/create-pull-request/bump-version ... Bump release version	2025-08-28 06:02:24 -05:00