Firmware for the ATTNode v3
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
seiichiro b173436e54 Use Correct URL for Payload Decoder Generator 1 week ago
.vscode Refactored Sensor Libraries to use Common Interface 3 months ago
include Fix Calibration Routines 3 weeks ago
lib Enable Remote Calibration 2 weeks ago
payload Link to Online Version of Payload Decoder Generator from Readme 1 week ago
src Enable Remote Calibration 2 weeks ago
.gitignore Refactored Sensor Libraries to use Common Interface 3 months ago
LICENSE Add License File 2 months ago Use Correct URL for Payload Decoder Generator 1 week ago
platformio.ini WS2812B Code Cleanup, Configuration via config.h 1 month ago

ATTNode v3 Firmware


The full documentation for firmware options, payload decoders and programming can be found at

Configuration and Programming

This is the code repository for ATTNode v3 compatible firmware. At the moment it supports LoRa communication using OTAA and a BME280 or SHT21 sensor, as well as deep sleep between measurements.

The firmware is developed using PlatformIO. At least version 5.1.0 is needed for ATTiny3216 support.

To set the fuses for clock speed, BOD levels etc., use the "Set Fuses" operation in PlatformIO. This has to be done once for a "fresh" Node or when the Board Config in platformio.ini was changed. Afterwards it is enough to use the normal "Upload" function for Code or config.h changes.

Before programming a node, copy src/config.h.example to src/config.h and set the used sensor, LoRaWAN keys and other options as needed.

Programming is done using a MicroUPDI Programmer, settings in platformio.ini are set to use it. For other pogrammer options see the PlatformIO Documentation

Payload Decoder

You need to specify a Payload Decoder fitting for your configured Sensors for a Node. See payload/index.html in this repository. Open it in your Browser of Choice and select the enabled sensors. It will generate the Payload Decoder fitting for the choosen Sensors. You can also use the Online Version at

It is possible to change the sending interval via Downlink-Packets at runtime. Downlinks for setting the transmit interval have to be sent on port 1. The time between Transmits is specified in minutes (or more exactly, 64 Second intervals) and as a 2 byte value, which will be interpreted as an uint. So for example 0x0001 means 1 Minute, 0x0002 means 2 Minutes and so on. Sending 0xFFFF resets the value to the compiled in default.

Sending an arbitrary value on port 2 will activate the calibration sequence for sensors that support it (like some of the CO2-Sensors).


Parts of this code where kindly provided by @shempe