Closed lyanchev closed 2 years ago
Thanks for the request, we've added this to our backlog for development.
@vicmgs This is a request to send the Join Requests to integrations. I think for compatibility's sake we will need some flag on the UI (disabled by default) to turn this on/off.
is this ready on router side already? let me know so we can coordinate
is this ready on router side already? let me know so we can coordinate
It is being worked on, will update when I got something more concrete.
router will receive channel with "receive_joins" attribute in the future from console. Let me know if you want me to change it
This was completed with #455
Are you using Helium hosted Console or running your own open source Console? Helium hosted
If you are on Helium hosted Console, which url are you currently on? N/A
If you are experiencing bugs in Helium hosted Console, please specify your Organization name and Device ID (ex. 3483050b-284d-47e2-8eda-e087fc03a753). N/A
Please describe your issue: Background: I have an IoT company - we develop software solutions and hardware products based on LoRaWAN and Wi-Fi. We've been in this space for 7 years now.
When creating our integration with Helium (using the console 2.0) we see that we receive only the uplinks. However, it's extremely useful to also receive the join requests info. It has many applications - see if the device has been restarted or whether it "lost" connection when using confirmed downlinks or it has some connection problems, etc... And the most important of all for our specific use-case - estimating the battery life of the device, as the join procedure costs significant energy.
With the other integrations we've completed - TTI, Tektelic, Actility, Kerlink (Wanesy), Chirpstack, etc., we receive info about the JR/JA.