LoRa (no deep decoding) Meshtastic, RNode (Reticulum), Helium, The Things Network (TTN), ... #3437
serialrf433
started this conversation in
General
Replies: 1 comment
-
|
Agreed, some hint that that LoRA traffic (though undecoded) has been seen would be nice. Some general function that looks at signal patterns and prints findings. If anyone is interested to tackle this: it can be developed independent from rtl_433, just use the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When i am in a new place, i like to turn on rtl_433 and check what is in the air.
These days, many people have ramped up individual use with LoRa. Some companies are transmitting their metering data over it. But most interesting are the networks around you can be part of.
I think such a use case for rtl_433 would be interesting. The same like the ability to show the rtl_433 packages that can not be decoded because no decoder implemented.
For example some implementations are LoRaWAN, some are LoRa P2P, some have custom preamble, and many other differences. Those differences could help keeping thins apart to be able to make some sort of a list what LoRa things around you are used at the moment.
I am aware of
#1657
#1939
Maybe you could reuse something from https://github.com/jgromes/RadioLib for the detection?
I am not asking here for deep decoding and decrypting public Meshtastic messages with AQ== (that would get removed in Meshtastic 3.0). For many people it is for sure interesting to know what happens around them and what LoRa network they could join.
Beta Was this translation helpful? Give feedback.
All reactions