NebraLtd / helium-miner-software

Software for Nebra (and third party) Helium Miners

https://nebra.io/hnt

MIT License

92 stars 48 forks source link

Multiple Vendor Integration #11

Open ryanteck opened 3 years ago

ryanteck commented 3 years ago

Change config and packetforwarder to handle multiple vendors.

EDIT: Status update:

[x] packet forwarder (works with multiple vendors, but may need to handle different configs)
- [ ] handle different global_conf.json for different vendors (rssi_offset settings etc)
- https://github.com/NebraLtd/hm-pktfwd/pull/32
[x] config
- https://github.com/NebraLtd/hm-config/issues/56
- https://github.com/NebraLtd/hm-config/issues/57
[x] diagnostics
- https://github.com/NebraLtd/hm-diag/issues/96
[x] balena hostapps / dbus config
- https://github.com/NebraLtd/helium-miner-software/issues/105

shawaj commented 2 years ago

Added a task list to the above

shawaj commented 2 years ago

105 has PRs that are nearly ready

shawaj commented 2 years ago

Moved this from #105

Also planning to test shortly on:

[x] OG Helium Hotspot
[x] Syncrobit Hotspot
[x] Sensecap Hotspot
[x] Linxdot hotspot

And probably some others...

shawaj commented 2 years ago

@marvinmarnold @vpetersson for this bullet point:

handle different global_conf.json for different vendors (rssi_offset settings etc)

currently, this is not possible, but probably lives more in the sx1301 and sx1302 repos - what do you think?

how would it be best to handle this do you think, should it be needed in future? perhaps some kind of flag in hm-pyhelper hardware definitions that it uses customised concentrator configs and the folder name for them or something?