Hello @rjwelling thanks for trying the Nebra Helium Light hotspot app from balenaHub.
I tested myself on pi4 and pi zero on RAK2287 (DIY-RAK2287) and it worked (the lora packet fwd) but i don’t recall to see these warnings.
Anyway, you have to know that this hotspot at the moment is not able to be part of the Helium blockchain until the HIP 19 (if i’m not wrong) is deployed.
With the validators running the Light Hotspots will be able to make PoC and DC. Having said that, this will be a DIY light hotspot and we still need to know if Helium will open the blockchain to DIY devices (alpha program).
Feel free to share the logs here and let me know if that you can forward LoRa packets.
@mpous thanks. the IP address mentioned is an AWS one but it can’t be pinged or traced. perhaps the end-point IP is wrong, however that’s “hard” coded in a config file which I can’t edit (easily)
@rjwelling maybe we can involve @Ryanteck here to see if you are trying to do forbidden things or this is just the standard message that the URL can’t validate your devices’ certificate (as it’s a DIY light hotspot) on the blockchain.
The “works for me” refers to the packet-forwarder but I’m investigating a new deploy to see if the helium-miner error shows up again. keep you posted
figured out that a redeploy resolved the issue but I also figured out that get the miner to work I had to some additional step and as such figured at that I’m running a RAK2287 which is not yet supported so ordered a supported RAK2245. waiting for FedEx
@mpous my helium-light-hotspot is working, easy to find as it’s only one (@date) in The Netherlands. downloaded the swarm-key and keeping an eye on the traffic.
Probably yes! they compete for the traffic. Actually you can check if you have a LoRa node and open the Helium console all the hotspots that receive the data sent by the node.