router
router combines a LoRaWAN Network Server with an API for console, and provides a proxy to the Helium blockchain (by helium)
packet-purchaser | router | |
---|---|---|
1 | 5 | |
16 | 70 | |
- | - | |
6.2 | 7.6 | |
7 months ago | 4 months ago | |
Erlang | Erlang | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
packet-purchaser
Posts with mentions or reviews of packet-purchaser.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-03.
-
Thank you Helium miners!
And the situation with almost any LoRaWAN feature is pretty close to that what I described above. It doesn't seem to be a secret for the Helium team, they aren't all idiots. That's why they have been trying to integrate Chirpstack open source LoRaWAN server with Helium ( https://github.com/helium/packet-purchaser/issues/23 , https://github.com/helium/packet-purchaser/issues/24 , https://github.com/helium/packet-purchaser/issues/25). I wish them a good luck, but from that what I see in the code and in the issues description, the result can be more disastrous than that "Light Hotspot transition". And, of course, this work should be started a couple of years ago.
router
Posts with mentions or reviews of router.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-03.
-
Thank you Helium miners!
Please take another look at this link which I already posted: https://github.com/helium/router/issues/642
-
How do I send a downlink message instantly? A downlink message is only received after an uplink one. For 5 seconds max delay on downlink, I need to send 17280 empty/dummy uplinks (polling for downlinks) every day.
Class C support doesn't require GW FW update. They just don't seem to have enough dev resources to make changes to their server code (see https://github.com/helium/router/issues/642 for more details. BTW, that guy who raised the issue is Semtech's VP of BizDev).
-
HIP51 and why it's important for HNT
Take a look, for instance, at this: https://github.com/helium/router/issues/642 That guy who created the issue is Senior Director LoRa Business Development at Semtech (which owns LoRa). And what's their answer? " As you can imagine we often hear prospects mention they will deploy "100,000's" of devices if only (insert magical blank)." Heck, first deploy that works properly, and only when ask for money...
-
Console v2.2.1.5 out of band release
This is an out of band release that addresses the latest issue related to receive window delay, specifically this issue: https://github.com/helium/router/issues/571.
What are some alternatives?
When comparing packet-purchaser and router you can also consider the following projects:
helium-data-traffic - script to analyse data traffic on the Helium network by accessing the blockchain API
lorawan-server - Compact server for private LoRaWAN networks