meshtastic_firmware

9,279 Commits 1 Branch 0 Tags

3 Commits

Author	SHA1	Message	Date
Chris DanisandGitHub	7f17747d8c	NodeInfo exchange: don't bother if too far away (#6260 ) When we receive a NodeInfo from a new node, if it is more than 2 hops beyond our configured hop limit away from us, don't bother to send a NodeInfo back to it. In my dense urban environment, I see many nodes that are >= 5 hops away, but sending their NodeInfo with a hopStart of 6 or 7. In most cases I can imagine, this seems like a waste of airtime.	2025-03-08 09:33:23 +08:00
Chris DanisandGitHub	5c77d42345	i2c: 0x45 can also be an SHT35 (#6249 )	2025-03-07 09:49:55 +08:00
Chris Danis GitHub Ben Meadors	f5e0e282b6	environment: add DPS310 high-accuracy barometer (#6237 ) * dps310: initial scan support * dps310 sensor support * new protobufs * new protobufs * address cr --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com>	2025-03-06 11:58:18 +08:00

Author

SHA1

Message

Date

Chris DanisandGitHub

7f17747d8c

NodeInfo exchange: don't bother if too far away (#6260 )

When we receive a NodeInfo from a new node, if it is more than 2 hops
beyond our configured hop limit away from us, don't bother to send a
NodeInfo back to it.

In my dense urban environment, I see many nodes that are >= 5 hops away,
but sending their NodeInfo with a hopStart of 6 or 7.  In most cases
I can imagine, this seems like a waste of airtime.

2025-03-08 09:33:23 +08:00

Chris DanisandGitHub

5c77d42345

i2c: 0x45 can also be an SHT35 (#6249 )

2025-03-07 09:49:55 +08:00

f5e0e282b6

environment: add DPS310 high-accuracy barometer (#6237 )

* dps310: initial scan support

* dps310 sensor support

* new protobufs

* new protobufs

* address cr

---------

Co-authored-by: Ben Meadors <benmmeadors@gmail.com>

2025-03-06 11:58:18 +08:00