Thank you Helium miners!

• router

  5 70 7.6 Erlang

  router combines a LoRaWAN Network Server with an API for console, and provides a proxy to the Helium blockchain (by helium)

  

I don't mention multiple bugs and absent functionality in the Helium's network server ( this is a good example: https://github.com/helium/router/issues/642 ). I don't mention you need to write off all your investments in 16- and 64-channels gateways. And so on...

• helium-data-traffic

  5 16 0.0 Python

  script to analyse data traffic on the Helium network by accessing the blockchain API

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• lorawan-server

  2 915 0.0 Erlang

  Compact server for private LoRaWAN networks

It's curious that the project they based their server on ( https://github.com/gotthardp/lorawan-server ) supported class C long before Helum decided to be a LoraWAN provider. So, they actually throw out the code they were unable to adopt to their so-called "archictecture", and I'm not sure that they were thinking about (if they were thinking at all) at that moment.

• packet-purchaser

  1 16 6.2 Erlang
  

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.

Suggest a related project