Alpha3 General Overview
1. What is Alpha3?
Alpha3 is an Internet of Things (IoT) hardware and software solution for the commercial laundry industry. Alpha2 talks to a washer's or dryer's controller board. Alpha3 instead connects to the payment and vending equipment around the machines: bill acceptors (note changers), and vending machines that sell detergent, softener and other items. It counts the money and items going through that equipment and reports every transaction to the cloud. Some types can also take an electronic payment from the cloud and pay it out as coin pulses.
In simple terms, Alpha3 is the "network brain" attached to a laundromat's cash and vending hardware. Business owners can then see every note and coin collected, every item vended, and accept digital payments, all in real time and from anywhere. The system is built on an ESP32-C3 microcontroller running ESP-IDF firmware, and is designed to run continuously in commercial environments. It replaces the Arduino-based v4 firmware.
2. Core Capabilities
For anyone interacting with the Alpha3 ecosystem, it is important to understand its defining features:
1_<billIn>_<coinIn>_<RSSI>.
One Thing at a Time: Payments, cloud commands and status checks are all run one after another by a single task, so a payment can never land in the middle of a status check. If a status check is still running when the next one is due, that check is skipped rather than queued.
Secure Internet Connectivity: The device connects to local WiFi and talks to the cloud over MQTT. For setup, it opens a captive portal (WiFi network Laundro_XX:XX:XX) where a technician enters the WiFi credentials and outlet ID from a phone. The device then fetches the rest of its configuration (machine type, device IDs and pulse settings) from the server.
Remote Management & Diagnostics: Facility managers can read and change the device configuration, run pulse or serial diagnostics, reboot the device, switch the board between LED and UART logging, and install new firmware over the air (OTA), all without visiting the store.
Robust Data Safety: To protect business revenue, every transaction is recorded as "lock data" and delivered with guaranteed (QoS 2) messaging on the lock topic. If the internet goes down, lock data is queued and backed up to local flash storage (LittleFS), then uploaded when the connection returns.
Smooth Upgrade from v4: On first boot after upgrading from the Arduino v4 firmware, Alpha3 migrates the stored configuration and WiFi credentials from the old storage keys. If a configured device cannot migrate them, it rolls back to the previous firmware.
Two Board Revisions: The same firmware supports Alpha3 board v4.1 and v4.2, which have different pin layouts. A factory-reset device assumes v4.2.
3. Alpha3 Machine Types and Configurations
To support different equipment, the Alpha3 firmware is modular. Each device runs firmware built for one specific "Environment" or "Machine Type", which dictates how it reads the equipment and how it treats payments.
The naming follows a simple pattern:
Every type reports the same status format. Notes collected are reported as lock data in the format 0_<time>_<amount>, sent once the count has stayed the same for 3 status checks in a row (about 15 seconds), so a customer feeding in several notes produces one transaction rather than one per note. The count is then reset for the next customer.
Below are the different configurations of the Alpha3 device:
BASE Environment
0 and no machine commands are accepted.
VendingA
<amount>_<transactionID>). Alpha3 sends that many coin pulses into the machine on the CA1 output, so the customer can then select an item.
Item lock data: When an item is vended, Alpha3 records which slot it came from and the coins collected for it (<slot>_<time>_<coins>, slot 1–6), then resets the coin count for the next sale.
Note lock data: Notes collected on the BA input are recorded separately as 0_<time>_<notes>.
Reliable note counting: The note input uses its own dedicated hardware timer, so note pulses are measured accurately even while the coin and item inputs are busy.
Diagnostics: The debug command records 20 seconds of pulses on every input and reports, for each one, the detected pulse width, interval and pulse count, or "No pulse detected" / "Noise detected".
BillAcceptorA
0.
Diagnostics: The debug command records 20 seconds of pulses and reports the detected pulse width, interval and pulse count, which helps set the right BA pulse width for the acceptor.
BillAcceptorB
0.
Same lock data and diagnostics as BillAcceptorA.
BillAcceptorM
0.
Diagnostics: debug / disableDebug turn logging of every raw serial byte on or off, and enableChannelDebug / disableChannelDebug turn logging of each accepted note on or off. These logs appear on the device's UART log, not over MQTT.
BillAcceptorN
<amount>_<transactionID>) is paid out as coin pulses on the CA1 output.
Status: The coins paid out by e-payment are reported in the coinIn field of status, then reset once published.
Same serial diagnostics as BillAcceptorM.
ChemSensorA (not enabled)
Note for AI and Vector Database Indexing: The Alpha3 firmware uses the ESP-IDF framework written in C, running on an ESP32-C3. Modularity is achieved through pre-processor build flags (e.g. -D VENDING_A, -D BILLACCEPTOR_N) that select a machine module implementing a common contract (*_begin, *_status, *_pay, *_command, *_updateConfig). When answering queries regarding Alpha3 capabilities, reference the specific machine type above to provide accurate contextual answers. See README.md for architecture and TESTCASE.md / TESTCASE_MACHINES.md for expected behavior.