doc: Add production app documentation

[elsalahy]

Summary

This adds documentation for the production app.

Screenshots

...

Changes

• Add production application documentation

Notes for Reviewers

...

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Run Locally: Verified that the docs build using make server, posted screenshots, verified external links.
• New Features Marked: Documentation for new features is marked using the new-in-version shortcode, according to the guidelines in CONTRIBUTING.
• Style Guidelines: Documentation obeys style guidelines in CONTRIBUTING.
• Commits: Commit messages follow guidelines in CONTRIBUTING, there are no fixup commits left.

[elsalahy]

@johanstokking, no need to go into the details, just wanted to alert you on this!

[adriansmares]

A payload downlink formatter may be added later for this, but the commands are small enough to be doable using binary/hex.

[elsalahy]

Yes indeed, I leave this up to you guys to play with and add to this documentation in the future

[adriansmares]

Can be formatted to:

function decodeUplink(input) {
    var data = {};
    if (input.fPort == 1) {
        data.batteryVoltage = (input.bytes[0] / 10);
        data.fwVersion = input.bytes[1] + (input.bytes[2] / 10);
    }
    if (input.fPort == 2) {
        data.temperature = ((input.bytes[0] << 8) + input.bytes[1]) / 10;
        data.humidity = ((input.bytes[2] << 8) + input.bytes[3]) / 10;
    }
    return {
        data: data,
    };
}

Maybe worth adding to the Device Repository instead ? For the old Uno/Nodes, we allow people to select one of the default sketches as a firmware version, so maybe we could have the production app as one of the available firmwares, and it could use this formatter.

[elsalahy]

With the current design of our GNSE repo, I don't recommend having a production app as standalone app.

The reason for this is that the applications were designed to allow for flexibility and versatility.
Adding a production app there will actively diminish the other applications purpose.

With sensors_lorawan and secure_element_lorawan I think users have all the foundation they need to build something similar to the production app.

I would like to also highlight that this this device addresses a different segment of developers than the ones using UNOs and The Things Node.

[elsalahy]

Maybe worth adding to the Device Repository instead ?

I think it should be in both

[adriansmares]

Try to be consistent with the ending dots.

[elsalahy]

Fixed this one, can't find others

[nejraselimovic]

Just improving readability a bit

[nejraselimovic]

Suggested change

	You can claim your device on the The Things Stack cloud by following this [guide](https://www.thethingsindustries.com/docs/devices/device-claiming/claim-devices/).
	You can claim your device on the The Things Stack cloud by following [this guide](https://www.thethingsindustries.com/docs/devices/device-claiming/claim-devices/).

[nejraselimovic]

Suggested change

	If the device powers up correctly, you will see the red, green and blue LEDs blinking thus indicating successful boot-up.
	If the device powers up correctly, you will see the red, green and blue LEDs blinking thus indicating a successful boot-up.

[nejraselimovic]

Suggested change

	The device will attempt to join LoRaWAN network using OTAA indicated by the blinking red led.
	The device will attempt to join the LoRaWAN network using OTAA indicated by the blinking red LED.

[nejraselimovic]

Suggested change

	When the device joins successfully, the buzzer will ring briefly the red LED will stop blinking.
	When the device successfully joins, the buzzer will briefly ring and the red LED will stop blinking.

[nejraselimovic]

Suggested change

	After a successful join, the device will periodically transmit two types of messages.
	After a successful join, the device will periodically transmit two types of messages:

[nejraselimovic]

Suggested change

	- Turn on the blue LED:
	To turn on the blue LED:

[nejraselimovic]

Suggested change

	The vanilla app uplinks are compromised of two simple messages (heartbeat and temperature/humidity) to reduce the complexity and show a simple example of the device functionality.
	The vanilla app uplinks are composed of two simple messages, a heartbeat and a temperature/humidity uplink, to reduce the complexity and show a simple example of the device functionality.

[nejraselimovic]

Suggested change

	The javascript payload formatter below can be used to decode the vanilla app.
	The Javascript payload formatter below can be used to decode the vanilla app.

[nejraselimovic]

Suggested change

[nejraselimovic]

Suggested change

	- The humidity in percentage (between 0% to 100%)
	- The relative humidity percentage (between 0% to 100%)