In 2017, Hurricane Maria, a category-5 storm, severely impacted Puerto Rico, demolishing homes and communication infrastructure. To address this issue, the ClusterDuck Protocol (CDP) was developed in 2018. It utilizes battery-powered Internet-of-Things devices to reestablish essential communication during emergencies, allowing civilians to request assistance, share their locations, and receive vital information from local governments and responders.
The ClusterDuck Protocol runs on a variety of IoT hardware, including many ESP32 Arduinos.
Here is a list of hardware we use, though there may be many others that work. We recommend the Heltec LoRa ESP32 and the TTGO T-Beam ESP32.
For a simple network you will want to make at least two Ducks. For bigger networks you will need more.
To start developing, you will need PlatformIO on your computer.
Download or git clone the CDP library from GitHub.
Follow the installation instructions here
Please Note: With the Release of the ClusterDuck Protocol Version 4 we have different instructions. If you are looking for older instructions please go here
Connect your board to platform IO
Follow the these updates instructions for loading up a Duck to get one running.
Use the pre-built examples or develop custom Ducks of your own.
Deploy!
: A confirmation that a specific interaction flow or "dialog" has been successfully saved or pushed live by a developer.
The updated version focuses heavily on reducing latency, improving multi-turn context retention, and simplifying integration with large language models (LLMs). 2. Key Enhancements in the Updated Version
: The "memory" of the dialog has been sharpened. BotX is now better at tracking complex, multi-step instructions, reducing the need for you to repeat yourself. Enhanced Mobile Experience
Recent updates to dialog-based AI systems focus on three primary pillars: context management, interoperability, and automated status updates. botx dialog updated
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Beyond this specific file-related update, other changes in the botx library indicate a focus on improving the developer experience and robustness of the system:
We have successfully deployed an update to the conversational flow. This update includes optimized response logic and refreshed content to better align with our current service guidelines. Key Changes: : A confirmation that a specific interaction flow
: Dialogues can be initiated by specific customer actions, such as leaving a phone number on an advertisement or article. Information Security
: Highlight seamless connections with existing tools and APIs, such as the PixieBrix + BotX integration for browser-native workflows.
If a returning customer connects, the bot securely recalls historical preferences, past issues, and ongoing tickets. Key Enhancements in the Updated Version : The
"Bot-X: An AI-based virtual assistant for intelligent manufacturing"
BotX is a prominent, no-code generative AI automation platform. It enables companies to build autonomous AI agents capable of parsing heavy documentation, auto-filling digital forms, and engaging users through highly structural, scripted dialogue workflows.
The notification blinked once in the lower corner of the console: [BOTX DIALOG UPDATED] .
: New workflow actions allow systems to automatically update a bot's status (active/inactive) or reassign a specific bot to a contact based on their actions—such as switching from a "Sales Bot" to an "Appointment Bot" after a successful booking.
For hybrid low-code scenarios, the updated BotX dialog allows within dialog nodes. This enables: