disk91 / helium-chirpstack-community Goto Github PK

• Allow to increase the DC numbers by admin for any entity
• Manage a possible negative DC authorization for monthly invoicing
• keep track of DC consumption day after day for each entity

Detect new devices to register them into the helium API, eventually count some DCs consumed for this action

Self create and Self manage user account within an OpenID environment

Manage message duplicates with eventually a specific DC consumption, make sure they are identified and correctly process

When an entity now have DCs balance back to positive, the Devices are allowed to communicate

• reactivate the nwksKeys
• re-enable join
  by updating the Helium APIs

When an entity reach DCs to 0, devices are deactivated

• No possible Join
• No more NwkSKey
  Update the Helium Db dynamicalyy

Detect device join to update the devaddr authorized ntwSKey to Helium

Detect inactive devices and invoice a "certain amount of DCs" per "non activity period"
This is basically cleaning inactive accounts.

Like for limiting a device going crazy

Objective is to detect the message received, attribute them to the right owner and identify the number of DCs consumed