Timeline for LoRa point-to-point communication
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jul 2, 2022 at 21:38 | history | suggested | guitarpicva | CC BY-SA 4.0 |
grammar man strikes again!
|
| Jul 2, 2022 at 21:03 | review | Suggested edits | |||
| S Jul 2, 2022 at 21:38 | |||||
| Jun 27, 2021 at 18:26 | comment | added | Nina | Thank you for all the help! I posted a new question after your answer. If you would like to take a look here is the link: iot.stackexchange.com/questions/5780/… | |
| Jun 27, 2021 at 11:33 | comment | added | jcaron | Yes, LoRaWAN devices all have identifiers. Decryption happens at the LNS, so either you have to embark an LNS on the ESP32 (no idea if this is possible or if there are any implementations of that), or everything would be terminated at the LNS and then the data sent back to the ESP32. The alternative is to build your own protocol on top of LoRa, with identifiers, encryption, etc. Not knowing more details about your use case it’s difficult to say which option would be best. | |
| Jun 27, 2021 at 6:52 | comment | added | Nina | Thank you for your reply! So if I understand correctly, there are, however, device identifiers with LoRaWAN? Could the packets sent by a LoRaWAN sensor be received and pushed to a database by a M5stack with a LoRa module (and decrypted using Cloud functions) or is a LNS necessary? | |
| Jun 27, 2021 at 6:23 | vote | accept | Nina | ||
| Jun 26, 2021 at 23:19 | history | answered | jcaron | CC BY-SA 4.0 |