- This topic has 1 reply, 2 voices, and was last updated 1 year, 4 months ago by
.
-
Posts
-
-
# Request for Advice: Adding Heartbeat Functionality to EByte LoRa Manager
Hello everyone,
I’m currently working on a project using the [EByte LoRa Manager for ESP32](https://github.com/xreef/EByte-LoRa-Manager-esp32-Gateway) and I need some help to enhance its capabilities.
## Project Goal
My goal is to modify this project to include a **heartbeat functionality**. This feature would allow the system to periodically send out signals to check if other LoRa devices on the same channel are active and responsive. Additionally, I want to implement a **user interface option** that would allow users to easily view all the alive LoRa devices operating on the same channel.
I would greatly appreciate any advice, resources, or examples on:
– Best practices for implementing heartbeat functionality in LoRa networks.
– Tips on modifying the ESP32 web server code to add new UI elements.
– Any known pitfalls or performance considerations to keep in mind.## Collaboration
I am open to collaboration. If you have experience in LoRa networks or ESP32 development and are interested in contributing to this project, please let me know.
Thank you all in advance for your time and help. I’m looking forward to your valuable insights!
Best regards,
lev
-
Hi Lev,
the project is subdivided into 2 parts, the first is the link in your post, and the second is the web interface that is in another repo.The “heartbeat functionality” can be managed with a broadcast message with the address set in the E32 fitted in the gateway. In the message return, you must check if it’s an acknowledgment and add the information passed in a WebSocket message.
The second is less simple, because the WebInterface is a React, Typescript, Redux framework, so you must know at least React, here an example of Message receiver box.
The only consideration is that in the project, we use a push server hosted in the ESP32 that implements WebSocket. To create a fully working gateway, the best practice says that you must use an external MQTT server, like the LoRaWAN implementation (It’s a simple standardization of a gateway to ask for money from the people).
So my advice is to implement all the needed functions in the “server” part; if it’s interesting and usable, I think some people will follow you to help on WebInterface.
Bye Renzo
-
- You must be logged in to reply to this topic.
