Starting from the top of the article. I'm not sure if this is a convention around the world when it comes to technical (ish) documents but with my past experience U.S Navy Nuclear Power Plant Operator. There are two different types of tips (what Gitbook calls them) "notes" and "warnings". "notes" are things that amplify some information but doesn't affect you personally overall. "warnings" are ones that if done improperly could lead to you or someone getting hurt. I don't think there are any potential "warnings" in regards to Helium.. however the major difference is a location in the document. "notes" go after the item it's amplifying and "warnings" come before.

TL;DR - I think the tip should go after the table.

The Tip "Rewards Change Over Time" contents might need to be cleaned up a little bit. I understand that HNT rewards are scheduled to change over time, which is currently referenced. But I believe what HIP 10 does can also be seen as the rewards changing.

Recommendation: In the above table you can see the maximum allotted rewards per reward type in accordance with HIP 10.

If you're interested in the current reward type % you can check out the Chain Variables API. (However, I think it would be cool to have a refresh button that taps into the blockchain API)

The next maximum allotted rewards change is currently scheduled for August 1, 2021.

I feel the paragraph under the table could read more like this?

"HIP10 was introduced by Helium Community Member hashc0de and was adopted by the Helium Community, HIP10 ensures that HNT is rewarded at a rate of 1:1 to the amount of Data Credits (DC) routed by any given Hotspot per epoch. In doing so the Data Network Traffic reward is proportional to the DC spent that epoch. This proportional relationship between Data Network Traffic reward type and DC is capped at 32.5% (1113.0145 HNT). Therefore, if the DC burned doesn't equal the value of 1113.0145 HNT the remaining HNT is redistributed to the Proof of Coverage (PoC) rewards groups pro-rata.

Here are a few examples to illustrate how this works in practice:"

My final suggestion is with your examples. I think it would be cool if there were tables that showed the reward break down but by Hotspot types. The reason is to help buyers be a little more educated when buying. If they saw the potential rewards for having only 1 hotspot in the area vice 3 it would help allow them to make a better judgment call when ordering the hotspots.

I think you can just show the difference between 1 hotspot, 3 hotspots (minimum earnings while being a challengee and witness), and the consensus group.

Want This:

Not This:

Following the instructions outlined in https://developer.helium.com/devices/arduino-quickstart/heltec-wifi-lora-32-v2 I receive a compile error trying to deploy the project (https://github.com/helium/longfi-arduino/blob/master/Heltec-WiFi-LoRa-32-V2/longfi-us915/longfi-us915.ino) to my Heltec ESP32 V2 board.

The specific error listed is "libraries\ESP32_LoRaWAN-master\ESP32_LoRaWAN.cpp.o:(.literal._ZL22lwan_dev_params_updatev+0x0): undefined reference to 'userChannelsMask'" on my attempts.

Any suggestions?

Hi,

The following file has a duplicate of the Hotspot table where the Metadata should be documented.

devdocs/console/integrations/json-schema.md

I would submit a pull request if I knew exactly what the documentation should entail :)

Regards,
Marc

helium/devdocs/blob/master/console/integrations/mqtt.md indicates using -m "{"payload_raw":"encoded_string"}" but this fails.
Instead -m '{"payload_raw":"SGVsbG8sIHdvcmxkIQ==","port":1,"confirmed":true}' works for me.

Of course you may what to make it -m '{"payload_raw":"[encoded string]","port":[0:1],"confirmed":[true:false]}'

We need to either remove or stack the header and footer links/text when scaling down.

Browsers that loaded old version of the devdocs with the color mode option are still loading the old colors. We need to remove the other options so the current styles are loaded.

Posted this in the HelTec ESP32 LoRaWAN project page --> HelTecAutomation/ESP32_LoRaWAN#60. Any suggestions? Wondering if any configuration settings or cpp library files might still need to be modified in order to get my board to join...

Menu links do smooth load transition and markdown content links do not, not sure why.

Currently the same color as background

You have a RED BOX around the items that need changing. Nice / Clean / Easy visual, you set me up for failure.
In the Server area, your documentation shows the Server Address is 192,168.2.12
Your text says the address should be the IP Address of your Helium Network Server.

Please delete the IP address of “192,168.2.12” replace it XXX.XXX.XXX.XXX and a NOTE that says
“YOUR HELIUM NETWORK SERVER IP ADDRESS”

I think it may help people who don't follow the instructions.

Hello, have any of the YoLink devices listed here been tested and vetted?
http://www.yosmart.com/products-list
They are "LoRa enabled".

For some reason there is a horizontal scrollbar on desktop browsers with plenty of horizontal space.

Link: https://network.helium.com

In device and hotspot docs, be sure to mention the following:

• look for coverage in your area using the visualizer. if there’s no coverage, here’s how to build your own hotspot
• “if there’s no coverage, you c an either buy a hotspot from the store, or build your own”
  Provide hotspot buy links

Propose that the writeup in https://developer.helium.com/blockchain/mining-token-rewards include an explanation of what happens when a packet from a sensor is received by multiple hotspots. Specifically, which hotspot(s) are rewarded for the routing and how that determination is made.

search for here

Cannot get gatsby-remark-images working
issues thread: gatsbyjs/gatsby#6698

Also, cannot get this working:
https://www.gatsbyjs.org/packages/gatsby-remark-copy-linked-files/

I think this image is wrong:

When you buy a Helium Hotspot, you are buying a Packet Forwarder and a Miner in a convenient package:

https://github.com/helium/devdocs/blob/master/hotspot/developer-setup.md

I presume the rightmost box should say 'Helium Miner', like this:

I'd make a PR but it from the filename I'm guessing these came from Illustrator.

• One large POC image just under "This is a Proof of Coverage Challenge, as seen in the Helium Network Visualizer"
• In the Challenge Failure Modes and Score Implications, one image for each of the the subheadings (showing Target Not Challenged, Failed Challenge, and Not Challenged)
• One nice image for the Console image of the network component section

I'm sure there are others that work here. This should get us started. Feel free to add anything else you feel is relevant and additive.

We need something to kick off the Console docs. Onboard a device and watch packets fly.

Try using typography again
https://dev.to/stoutlabs/speed-tip-use-typefacesjs-in-gatsby-to-locally-host-fonts-6om

The Build a Hotspot docs (1) suggest a a RAK2245 Pi Hat, but:
the linked rak docs (2) say that's outdated (going away Oct 11th 2020).

The rak docs link to (3) as a successor, but:
those does don't appear to show the RAK2245 Pi Hat anywhere.

I feel like the docs should be updated before Oct 11th (to avoid a dead link), but I'm not sure where/what to point to?

(1) https://developer.helium.com/hotspot/developer-setup#example-custom-hardware
(2) https://doc.rakwireless.com/rak2245-pi-hat-edition-lorawan-gateway-concentrator-module
(3) https://docs.rakwireless.com/Product-Categories/WisHat/