These are few examples to show how someone can build on top of the ClusterDuck Protocol. It works using the master branch of the ClusterDuck Protocol firmware.
These sensors are tested and confirmed that it works by CDP.
The BMP180 example is a custom MamaDuck that will send sensor data from the BMP 180 (Temperature, Pressure, Altitude) if integrated with the .
The WS2812 example is a Mama Duck, which also brings some light to the world by incorporating some WS2812 LEDs via the FastLED library.
If you have a TTGO T-Beam you can use these custom examples for it.
This example is a MamaDuck, that uses using TinyGPS++ to get and send GPS data with the GPS topic based on the set timer.
Using the TTGO's hardware we can collect all different kinds of live board information such as: onboard temperature, battery voltage (if 18650 installed), and charging.
The papa Iridium Example is built to have an extra Iridium Satelite Backhaul when WiFi breakes down.
This custom PapaDuck keeps track of when it loses access to the internet and for how long.
The Serial Papi Example is a custom papa that will print the incoming data into the Serial Monitor for the PAPI to read.
The WiFi Papi Example is a custom papa that will send the incoming data into the Papi.
You can enable encryption. CDP comes with default settings, but set your own IV and AES256 key when in use. NOTE It is not secure since the keys are hardcoded in the firmware. This is a work in progress.
Decryption is a very fast operation and using this example your messages will be decrypted before sending to the cloud. Remember to set IV and AES256 key to be the same as what you use on other devices.
A custom mama example that uses AES256 to encrypt the messages it generates and relays it. Any message it receives from the network, it can decrypt it.