nebraltd / helium-rak Goto Github PK

View Code? Open in Web Editor NEW

14.0 13.0 12.0 268 KB

Nebra OpenFleet for RAK v1.5, v2 and MNTD Miners

Home Page: https://nebra.io/rak

License: MIT License

helium-rak's Introduction

Helium RAK - Open Source Firmware for RAKwireless / MNTD Helium Miners

Balena OpenFleet for RAK v1.5, v2 and MNTD Miners

Key features:

local IP diagnostics dashboard
updated regularly (our automated system means this will get updates at the same time as the entire Nebra fleet)
automatic updates (if installed via balenaHub) or option to fork and manage your own fleet
powered by balenaOS which is optimised for edge devices and very secure
access to new features as added to the core Nebra software
fully open source software stack (the only one in the Helium community!)
COMING SOON: access to remote management dashboard (paid extra)

Please note: this repo and the issues section here are not monitored actively, so if you have an issue with this software we would ask that you email [email protected] or start an issue in our main helium software repo. We do not provide support or feature requests for this free software at this time so this should only be used for bug reports.

How to use this firmware

There are two ways you can deploy this firmware to your RAKwireless / MNTD Helium Miner - either using the Balena Hub installation (which gives you auto-updates), or by forking the fleet and starting your own personal fleet (in this instance you will have direct control over your devices but will not get automatic updates).

What you will need

microSD card reader for laptop/computer
OS image file specifically of your RAK or MNTD Hotspot (link in step 4 below)
computer or laptop (Windows or Mac)
RAK v1.5, v2 or MNTD Hotspot

Do not follow this guide if you have a different manufacturer of hotspot!

Balena Hub Installation (preferred - includes auto-updates)

Step 1 - First of all you will need to remove the current microSD card that is inserted into your RAK Hotspot miner. You will need to follow the instructions from RAK wireless in order to see how to do this. Here is a quick video to show you how to remove the microSD card (skip to 3:21):

Step 2 - Insert the microSD card either into an SD adaptor or if your memory card reader takes microSD directly then insert that and connect it to your computer or laptop.

Step 3 - On your computer download and install Balena Etcher from - https://www.balena.io/etcher/

Once downloaded go ahead and open up the balenaEtcher program on your computer or laptop.

Step 4 - Before we move to the next step you will need to download the latest OpenFleet software for your hotspot from balenaHub, which you can find here - https://nebra.io/rak

Click on the link and you will be redirected to the balenaHub page for your hotspot. Click on Get Started.

Important: do not click on Fork this fleet

Step 5 - Select your preferred network connection (Ethernet required on first boot). If you have balenaEtcher already installed (from step 3 above) you can select Flash, otherwise you can select Download from the drop-down box by clicking the arrow.

Step 6 - Click on the Flash from file button in balenaEtcher and navigate to where you saved your downloaded firmware file. Select it to be installed.

In the middle section of balenaEtcher click Select target to select your SD card to install the OS (it may be selected automatically).

Finally, click on the Flash! button to begin installing the firmware to your microSD card (you may need to type your login password here).

Step 7 - Once it has finished flashing you can now remove the SD card from its adaptor and card reader and then insert it back into the RAK or MNTD hotspot.

Step 8 - Finally, connect your Ethernet cable to the hotspot and then the power cable. The hotspot should now boot up with your new firmware installed. It may take up to 30 minutes to do all the updates.

Note: We recommend that you use Ethernet for the first boot of the hotspot, at which point you can configure WiFi using the MNTD hotspot app (for Apple and Android based devices).

This guide is also available on our support site here.

Forking Fleet Installation (requires updating manually / setting up own automations)

If you are more technical and would like to have more control over your devices (including, among other things, command line access) you can also fork the fleet - thereby creating your own fleet on balenaCloud running our software. However, please do note before continuing that by forking the fleet you will lose the automated updates available from the above recommended install method - unless you set up your own automations, the update process will be manual. Additionally, please note that balenaCloud is only free for the first 10 devices, after which you will have to pay for an account with "Microservices" capability (installing via the balenaHub method above is free regardless of device quantity).

Step 1 - To start with you will need to follow steps 1 to 3 in the above recommended install method. Once you have completed those steps, please return to step 2 below.

Step 2 - Before we move to the next step you will need to fork the fleet and then download the latest OpenFleet software for your hotspot, ready to flash onto your SD card. There are two ways you can do this. The first way is to click the Deploy with balena button below:

Alternatively, you can visit the HELIUM-RAK balenaHub page and then click on Fork this fleet button which you can see in the below screenshot.

Step 3 - Select your preferred network connection (Ethernet required on first boot). If you have balenaEtcher already installed you can select Flash, otherwise you can select Download from the drop-down box by clicking the arrow.

https://github.com/NebraLtd/helium-rak/blob/master/balena.yml#L27-L41 data: applicationEnvironmentVariables: - VARIANT: COMP-RAKHM - HELIUM_MINER_HEIGHT_URL: "https://api.helium.io/v1/blocks/height" applicationConfigVariables: - RESIN_HOST_CONFIG_dtparam: '"i2c_arm=on","spi=on","audio=on"' - RESIN_HOST_CONFIG_dtoverlay: '"spi0-1cs","vc4-kms-v3d"' - RESIN_HOST_CONFIG_gpu_mem: 16 - RESIN_HOST_CONFIG_avoid_warnings: 1 - RESIN_HOST_CONFIG_disable_overscan: 1 - RESIN_HOST_CONFIG_disable_splash: "1" - RESIN_HOST_CONFIG_core_freq: 400 - RESIN_OVERRIDE_LOCK: 1 defaultDeviceType: raspberrypi4-64 supportedDeviceTypes: - raspberrypi4-64 version: 0.0.1

Manual updates

Setting up your own automations

Branches

In this repo there are two main branches:

master - the main software branch with production tested docker-compose.yml.
testnet - the testnet branch with bleeding-edge software. As this software can be untested and/or not working we do not recommend you use this in a production environment.

helium-rak's People

Contributors

Stargazers

Watchers

Forkers

arduino43 vanthongtomto ifeign phewwy gradoj nevrrmind veniceinventors pe1mew danstruble crash0v3r1de nargetdev mrbricker

helium-rak's Issues

Onboarding Error and no connecting via Bluetooth

Hello guys,

I am new here and also still with the topic of helium mining.
Unfortunately I am not getting anywhere with the setup. The hotspot does not want to connect to the Helium network and I do not understand why.
I already wrote to the support but didn't really get a solution.
I have created screenshots to show you what I mean exactly.
You are my hope to solve the problem.

I am very grateful for any helpful tips.

Originally posted by @JohnFilz in NebraLtd/helium-syncrobit#3 (comment)

Diagnostics - Device health check: User service 'packet-forwarder' is restarting unexpectedly, count: 166

After running the device health check on my rak v2, I get that error:

Here are the logs:
helium-rak_brave-doorway-15.03.22_12_41_33_(+0100).txt

Here's the device diagnostic log:
4bd2b596ecc33800175d40b8ff48b6b9_diagnostics_2022.03.14_15.40.28+0000.txt

Waveshare Module SX1302

Hello
I have a question.
Is it possible to use Blena Rak with a concentrator SX 1302 module from Waveshare in connection with a security chip ATCC 608 on the I2c bus?
I would be happy if that works. I would also load the $55 on the wallet to start.

Many thanks for the help

Sync question

Hi,

I understand that sync should no longer matter, but I noticed if I shut port 44158 my miner went to a relayed status and eventually was showing offline where I’ve had no activity since. Furthermore, if I leave the port open and looking at my traffic logs it appears the rak unit is moving lots of data over the wire. Which leads me to further confusion.. can someone EIL5 and clear this up for me?

cant compile

Built many versions for my RAKs via Balena hub's fork button (last successful build 19th dec) but now that page is empty (already reported I know), so I tried to push it from github with the 'deploy with balena' icon which links to https://dashboard.balena-cloud.com/deploy?repoUrl=https://github.com/NebraLtd/helium-rak

build starts but fails for the packer forwarder and multiplexer with the following error:

Service: packet-forwarder
[Error] Error: no matching manifest for linux/arm64/v8 in the manifest list entries
[Error] Service: multiplexer
[Error] Error: no matching manifest for linux/arm64/v8 in the manifest list entries

my fleet is set up as rpi4 64bit (aarch64)

thank you for any heads up

Balenahub page empty

I noticed today that all of your fleets have disappeared from Balenahub Has this project been discontinued?

No fleet on balena hub

Hi. Did something happen with Rak fleet? It's not on balena hub anymore 😒
This link nebra.io/rak gives me an error: failed to fetch resource

Failed to download image error with newest release

Hi,

After pulling down and pushing the newest image as of a couple hours ago. I am not seeing the repeated message. Is this a cause for concern?

Failed to download image 'registry2.balena-cloud.com/v2/3a33a7e2c9fa20026037df5ec9e2c000@sha256:29c1c05c9aa2b623e4bdf2e2497a00338322d6c6e952317dd42d0898573f42b4' due to 'layers from manifest don't match image configuration"

Im noticing within the console the components "helium-Miner", "gateway"... The helium miner attempts to download before getting the error message above. The other components look to be sitting in queue. Firmware under the diagnostic service is still showing the device running fw from 6/02/2022. I have attempted to restart the miner but it reverts back to this state. Should I rollback if possible?

Packet forwarder not working

Hi. I have forked the fleet and added my MNTD blackspot hotspot to the dashboard. However, the miner doesn't seem to be working.

Are there any specific variable settings I need to make?

I get this error:

Something wrong with the image

Hi,

I just added my rak v2 to for the test. But apparently two issues:

Major: The hotspot became un-usable. First I could not pair bt to it. When I click the button on the hs, I could not find the device after scanning. I did that in 10min apart and did a couple of restarts of the device nothing help.
Even after 30 min I could not ping the hs at all.

Provide some instructions please

This page says there are detailed instructions: https://www.nebra.com/blogs/news/production-update-firmware-support-for-third-party-miners-spring-sale-existing-customer-discount-and-more --> here: https://github.com/NebraLtd/helium-rak Yet there is nothing there. I'd give this a try if there was at least a hint of how to install it, what to do after booting, how I might know it's actually working, does it really have a dashboard? I already have a miner without a dashboard, and going through this without any gain isn't a good use of my time.

Question about public IP address changing

Hello,

Just a quick question. I noticed that my miner has not really done much of anything for the past 3-4 days now and was starting to scratch my head as to why. I noticed my ISP has issued a new public IP to me and within the balena dashboard it is still reporting my previous public IP.

Will this have a negative impact, should I see what I can do to get my new IP to match up from the balena console?

Thank you in advanced

Where do I find the instant sync option for my rakv2?

I've got access to the dashboard (balena cloud) but can't find the fast sync option.

Nebra Daskboard

Has the dashboard been enabled for RAK's yet? I tried adding my RAK using the serial number and ethernet / wifi mac id and it didn't work.

Image changes MAC address

Using this image changed my MAC address from what it was on the official Rak firmware. Is this normal? I would have never noticed if my hotspot hadn't showed it was relayed and I checked my port forwarding.

Concentrator reset pin on RAK v1.5 different than variant file, causing packet-forwarder crashes

I encountered an issue with an older RAK v1.5 where the concentrator reset pin was 17 instead of 25, which is the default specified in the variant file for COMP-RAKHM. This was causing an endless loop of packet-forwarder crashes.

Using a device variable "CONCENTRATOR_RESET_PIN_OVERRIDE" set to 17 resolved this issue. Wanted to get this out there for any others that might have older RAK v1.5 units that experience the same issue. No issues on my RAK v2s

Log of packet forwarder:

Restarting service 'packet-forwarder sha256:5c3ad980b694a4105f0a8dcfac40d0b4726d2b2de9882df12afaa927c4afa294'
<packet-forwarder> FREQ variable is already set as N/A (Non Nebra Miner).
<packet-forwarder> VARIANT variable is already set as COMP-RAKHM.
<packet-forwarder> All required environment variables have been set.
<packet-forwarder> 2023-02-09 00:50:51,396 - [DEBUG] - __main__ - (__main__.py).validate_env -- /opt/pktfwd/__main__.py:(63) - Starting with the following ENV:
<packet-forwarder>         VARIANT=COMP-RAKHM
<packet-forwarder>         REGION_OVERRIDE=False
<packet-forwarder>         REGION_FILEPATH=/var/pktfwd/region
<packet-forwarder>         SX1301_REGION_CONFIGS_DIR=/opt/pktfwd/config/lora_templates_sx1301
<packet-forwarder>         SX1302_REGION_CONFIGS_DIR=/opt/pktfwd/config/lora_templates_sx1302
<packet-forwarder>         SENTRY_DSN=False
<packet-forwarder>         BALENA_ID=3803ba4779605edd9a0c9314bfdbcf6d
<packet-forwarder>         BALENA_APP=helium-rak
<packet-forwarder>         DIAGNOSTICS_FILEPATH=/var/pktfwd/diagnostics
<packet-forwarder>         AWAIT_SYSTEM_SLEEP_SECONDS=5
<packet-forwarder>         RESET_LGW_FILEPATH=/opt/reset_lgw.sh
<packet-forwarder>         UTIL_CHIP_ID_FILEPATH=/opt/sx1302/chip_id
<packet-forwarder>         ROOT_DIR=/opt
<packet-forwarder>         SX1302_LORA_PKT_FWD_FILEPATH=/opt/sx1302/lora_pkt_fwd
<packet-forwarder>         SX1301_LORA_PKT_FWD_DIR=/opt/sx1301
<packet-forwarder> 
<packet-forwarder> 2023-02-09 00:50:51,398 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).set_variant_attributes -- /opt/pktfwd/pktfwd_app.py:(92) - Variant COMP-RAKHM set with reset_pin 25 and spi_bus spidev0.0
<packet-forwarder> 2023-02-09 00:50:51,398 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).start -- /opt/pktfwd/pktfwd_app.py:(39) - STARTING PKTFWD
<packet-forwarder> 2023-02-09 00:50:51,399 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).await_spi_available -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(340) - SPI bus spidev0.0 Configured Correctly
<packet-forwarder> 2023-02-09 00:50:51,400 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).retry_get_region -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(320) - No region override set (value = False), will retrieve from miner.
<packet-forwarder> 2023-02-09 00:50:51,401 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).retry_get_region -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(324) - Region US915 parsed from /var/pktfwd/region 
<packet-forwarder> 2023-02-09 00:50:51,401 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).prepare_to_start -- /opt/pktfwd/pktfwd_app.py:(74) - Region set to US915
<packet-forwarder> 2023-02-09 00:50:51,402 - [DEBUG] - pktfwd.utils - (utils.py).await_system_ready -- /opt/pktfwd/utils.py:(60) - Waiting 5 seconds for systems to be ready
<packet-forwarder> 2023-02-09 00:50:56,402 - [DEBUG] - pktfwd.utils - (utils.py).await_system_ready -- /opt/pktfwd/utils.py:(62) - System now ready
<packet-forwarder> 2023-02-09 00:50:56,402 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).prepare_to_start -- /opt/pktfwd/pktfwd_app.py:(77) - Finished preparing pktfwd
<packet-forwarder> 2023-02-09 00:50:58,006 - [DEBUG] - pktfwd.utils - (utils.py).is_concentrator_sx1302 -- /opt/pktfwd/utils.py:(89) - Command '['/opt/sx1302/chip_id', '-d', '/dev/spidev0.0']' returned non-zero exit status 1.
<packet-forwarder> 2023-02-09 00:50:58,007 - [DEBUG] - pktfwd.utils - (utils.py).replace_sx1301_global_conf_with_regional -- /opt/pktfwd/utils.py:(155) - Copying SX1301 global conf from /opt/pktfwd/config/lora_templates_sx1301/global_conf.json.US915 to /opt/global_conf.json
<packet-forwarder> 2023-02-09 00:50:58,010 - [DEBUG] - pktfwd.utils - (utils.py).replace_sx1301_global_conf_with_regional -- /opt/pktfwd/utils.py:(158) - Copying SX1301 local conf from /opt/pktfwd/config/lora_templates_sx1301/local_conf.json to /opt/local_conf.json
<packet-forwarder> CONCENTRATOR_RESET_PIN parameter not passed in, using value from the environment (val=25)
<packet-forwarder> CoreCell reset through GPIO25...
<packet-forwarder> CONCENTRATOR_RESET_PIN parameter not passed in, using value from the environment (val=25)
<packet-forwarder> CoreCell reset through GPIO25...
<packet-forwarder> 2023-02-09 00:50:58,766 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).retry_get_region -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(320) - No region override set (value = None), will retrieve from miner.
<packet-forwarder> 2023-02-09 00:50:58,767 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).retry_get_region -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(324) - Region US915 parsed from /var/pktfwd/region 
<packet-forwarder> 2023-02-09 00:50:58,768 - [DEBUG] - pktfwd.utils - (utils.py).retry_start_concentrator -- /opt/pktfwd/utils.py:(238) - Region before starting concentrator US915
<packet-forwarder> *** Beacon Packet Forwarder for Lora Gateway ***
<packet-forwarder> Version: 4.0.1
<packet-forwarder> *** Lora concentrator HAL library version info ***
<packet-forwarder> Version: 5.0.1;
<packet-forwarder> ***
<packet-forwarder> INFO: Little endian host
<packet-forwarder> INFO: found global configuration file global_conf.json, parsing it
<packet-forwarder> INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
<packet-forwarder> INFO: lorawan_public 1, clksrc 1
<packet-forwarder> INFO: no configuration for LBT
<packet-forwarder> INFO: antenna_gain 0 dBi
<packet-forwarder> INFO: Configuring TX LUT with 16 indexes
<packet-forwarder> INFO: radio 0 enabled (type SX1257), center frequency 904300000, RSSI offset -159.000000, tx enabled 1, tx_notch_freq 0
<packet-forwarder> INFO: radio 1 enabled (type SX1257), center frequency 905000000, RSSI offset -159.000000, tx enabled 0, tx_notch_freq 0
<packet-forwarder> INFO: Lora multi-SF channel 0>  radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora multi-SF channel 1>  radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora multi-SF channel 2>  radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora multi-SF channel 3>  radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora multi-SF channel 4>  radio 1, IF -300000 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora multi-SF channel 5>  radio 1, IF -100000 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora multi-SF channel 6>  radio 1, IF 100000 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora multi-SF channel 7>  radio 1, IF 300000 Hz, 125 kHz bw, SF 7 to 12
<packet-forwarder> INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8
<packet-forwarder> INFO: FSK channel 8 disabled
<packet-forwarder> INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
<packet-forwarder> INFO: server hostname or IP address is configured to "multiplexer"
<packet-forwarder> INFO: upstream port is configured to "1700"
<packet-forwarder> INFO: downstream port is configured to "1700"
<packet-forwarder> INFO: downstream keep-alive interval is configured to 10 seconds
<packet-forwarder> INFO: statistics display interval is configured to 30 seconds
<packet-forwarder> INFO: upstream PUSH_DATA time-out is configured to 100 ms
<packet-forwarder> INFO: packets received with a valid CRC will be forwarded
<packet-forwarder> INFO: packets received with a CRC error will NOT be forwarded
<packet-forwarder> INFO: packets received with no CRC will NOT be forwarded
<packet-forwarder> INFO: Reference latitude is configured to 0.000000 deg
<packet-forwarder> INFO: Reference longitude is configured to 0.000000 deg
<packet-forwarder> INFO: Reference altitude is configured to 0 meters
<packet-forwarder> INFO: fake GPS is enabled
<packet-forwarder> INFO: found local configuration file local_conf.json, parsing it
<packet-forwarder> INFO: redefined parameters will overwrite global parameters
<packet-forwarder> INFO: local_conf.json does not contain a JSON object named SX1301_conf
<packet-forwarder> INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
<packet-forwarder> INFO: gateway MAC address is configured to 0000DCA632DCA47F
<packet-forwarder> INFO: server hostname or IP address is configured to "helium-miner"
<packet-forwarder> INFO: upstream port is configured to "1680"
<packet-forwarder> INFO: downstream port is configured to "1680"
<packet-forwarder> INFO: downstream keep-alive interval is configured to 10 seconds
<packet-forwarder> INFO: statistics display interval is configured to 30 seconds
<packet-forwarder> INFO: upstream PUSH_DATA time-out is configured to 100 ms
<packet-forwarder> INFO: packets received with a valid CRC will be forwarded
<packet-forwarder> INFO: packets received with a CRC error will NOT be forwarded
<packet-forwarder> INFO: packets received with no CRC will NOT be forwarded
<packet-forwarder> INFO: Reference latitude is configured to 0.000000 deg
<packet-forwarder> INFO: Reference longitude is configured to 0.000000 deg
<packet-forwarder> INFO: Reference altitude is configured to 0 meters
<packet-forwarder> INFO: fake GPS is enabled
<packet-forwarder> ERROR: [main] failed to start the concentrator
<packet-forwarder> 2023-02-09 00:51:03,774 - [WARNING] - pktfwd.utils - (utils.py).retry_start_concentrator -- /opt/pktfwd/utils.py:(262) - lora_pkt_fwd stopped with code=1.
<packet-forwarder> 2023-02-09 00:51:03,774 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).retry_get_region -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(320) - No region override set (value = None), will retrieve from miner.
<packet-forwarder> 2023-02-09 00:51:03,775 - [DEBUG] - hm_pyhelper.miner_param - (miner_param.py).retry_get_region -- /opt/pktfwd-dependencies/hm_pyhelper/miner_param.py:(324) - Region US915 parsed from /var/pktfwd/region 
<packet-forwarder> 2023-02-09 00:51:03,776 - [WARNING] - pktfwd.pktfwd_app - (pktfwd_app.py).start -- /opt/pktfwd/pktfwd_app.py:(60) - Shutting down concentrator.
<packet-forwarder> 2023-02-09 00:51:03,777 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).stop -- /opt/pktfwd/pktfwd_app.py:(80) - STOPPING PKTFWD
<packet-forwarder> 2023-02-09 00:51:03,779 - [INFO] - __main__ - (__main__.py).start -- /opt/pktfwd/__main__.py:(106) - Stopping and cleaning up pktfwd
<packet-forwarder> 2023-02-09 00:51:03,779 - [DEBUG] - pktfwd.pktfwd_app - (pktfwd_app.py).stop -- /opt/pktfwd/pktfwd_app.py:(80) - STOPPING PKTFWD
Service exited 'packet-forwarder sha256:5c3ad980b694a4105f0a8dcfac40d0b4726d2b2de9882df12afaa927c4afa294'

Fast Sync not happening

I forked the repo from here - https://hub.balena.io/nebraltd/helium-rak and installed the image on my Rak v2 this morning, it's been a few hours and sync percentage is 0.17%, I was hoping it would fast sync by now. Rak is hardwired.
VARIANT is set to COMP-RAKHM

Enable mux and disable chain sync in sys.config

Upon checking sys.config, it appears two options are not set correctly for the miner:

{gateway_and_mux_enable, false}, {gateways_run_chain, true}, %% if false, gateways will no longer follow the chain

Should be

{gateway_and_mux_enable, true}, {gateways_run_chain, false}, %% if false, gateways will no longer follow the chain

Can't update Wifi connection.

After activating Bluetooth by power cycling the hotspot and connecting, I am unable to change my WiFi connection. When you select a new SSID it just spins.

Edit:
This is with the Helium app and Hotspot Utility.

Helium Status stays Pending

I’ve onboarded a new RAK v2 hotspot a few days ago and flashed it with the Nebra firmware. However, the Helium Status in the Dashboard keeps showing as Pending and the hotspot is not showing up on Explorer.

Are there any more details I can check regarding what it is doing?

Fresh Flash - Packet Forwarder Failure

I don't really know what I can send you but I just flashed the balena helium rak firmware from you guys onto this SD and everything looks solid with the excepton of packet forwarder alling on it's face.

Not sure if this is expected for initial boot up (literally 30 minutes power up time).

Error that keeps looping:
Traceback (most recent call last): packet-forwarder File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main packet-forwarder return _run_code(code, main_globals, None, packet-forwarder File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code packet-forwarder exec(code, run_globals) packet-forwarder File "/opt/pktfwd/__main__.py", line 13, in <module> packet-forwarder VARIANT = os.environ['VARIANT'] packet-forwarder File "/usr/local/lib/python3.10/os.py", line 679, in __getitem__ packet-forwarder raise KeyError(key) from None packet-forwarder KeyError: 'VARIANT'

I don't mind making modifications to the file system however I don't know anything about this python script trying to execute.

Failed to add edge detection - Hardware failure?

Just noticed one of my miners went offline a few weeks ago and the only errors in the log I'm seeing are GPIO related. Wondering if anyone can verify if the concentrator just died or maybe something else?

libmraa[13]: libmraa version v2.1.0-24-gbd91964 initialised by user 'root' with EUID 0

libmraa[13]: gpio: platform doesn't support chardev, falling back to sysfs

libmraa[13]: libmraa initialised for platform 'Raspberry Pi Model B Rev 1' of type 5

2024-02-28 01:08:40,541 - [DEBUG] - main - (main.py).validate_env -- /opt/venv/lib/python3.9/site-packages/gatewayconfig/main.py:(34) - Starting with the following ENV:

SENTRY_DSN=None

BALENA_APP_NAME=xxxx-xxxx

BALENA_DEVICE_UUID=3395aac54ec624a9535e759c6a61xxxx

VARIANT=COMP-RAKHM

ETH0_MAC_ADDRESS_FILEPATH=/sys/class/net/eth0/address

WLAN0_MAC_ADDRESS_FILEPATH=/sys/class/net/wlan0/address

DIAGNOSTICS_JSON_URL=http://diagnostics/json

ETHERNET_IS_ONLINE_FILEPATH=/sys/class/net/eth0/carrier

FIRMWARE_VERSION=v1.3.0

Traceback (most recent call last):

File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main

return _run_code(code, main_globals, None,

File "/usr/lib/python3.9/runpy.py", line 87, in _run_code

exec(code, run_globals)

File "/opt/venv/lib/python3.9/site-packages/gatewayconfig/main.py", line 77, in

main()

File "/opt/venv/lib/python3.9/site-packages/gatewayconfig/main.py", line 30, in main

start()

File "/opt/venv/lib/python3.9/site-packages/gatewayconfig/main.py", line 57, in start

config_app = GatewayconfigApp(

File "/opt/venv/lib/python3.9/site-packages/gatewayconfig/gatewayconfig_app.py", line 46, in init

self.init_gpio(variant)

File "/opt/venv/lib/python3.9/site-packages/gatewayconfig/gatewayconfig_app.py", line 139, in init_gpio

self.user_button = Button(btn, hold_time=USER_BUTTON_HOLD_SECONDS)

File "/opt/venv/lib/python3.9/site-packages/gpiozero/devices.py", line 108, in call

self = super(GPIOMeta, cls).call(*args, **kwargs)

File "/opt/venv/lib/python3.9/site-packages/gpiozero/input_devices.py", line 414, in init

super(Button, self).init(

File "/opt/venv/lib/python3.9/site-packages/gpiozero/mixins.py", line 433, in init

super(HoldMixin, self).init(*args, **kwargs)

File "/opt/venv/lib/python3.9/site-packages/gpiozero/input_devices.py", line 171, in init

self.pin.when_changed = self._pin_changed

File "/opt/venv/lib/python3.9/site-packages/gpiozero/pins/init.py", line 432, in

lambda self, value: self._set_when_changed(value),

File "/opt/venv/lib/python3.9/site-packages/gpiozero/pins/pi.py", line 319, in _set_when_changed

self._enable_event_detect()

File "/opt/venv/lib/python3.9/site-packages/gpiozero/pins/rpigpio.py", line 226, in _enable_event_detect

GPIO.add_event_detect(

RuntimeError: Failed to add edge detection

Packet forwarder shows the correct concentrator.

##### 2024-02-28 01:08:49 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 0
# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 0 (0 bytes)
# PUSH_DATA datagrams sent: 1 (162 bytes)
# PUSH_DATA acknowledged: 100.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### SX1302 Status ###
# SX1302 counter (INST): 60756175
# SX1302 counter (PPS): 0
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
#--------
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# GPS FAKE coordinates: latitude 0.00000, longitude 0.00000, altitude 0 m
##### END #####

On the dashboard it shows radio is operational and ECC is is valid/detected.
Region is set correctly as well as variant.

Not really sure what else to check/verify.

Can't activate Bluetooth via the side button.

I am unable to activate my Bluetooth by pressing the side button