Connected Devices & IoT
Connected Laundry Device: IoT, Program and Payment Architecture
Prototype approach combining program selection, remaining time, payment, machine telemetry and user notifications across a commercial laundry fleet.
Short answer
Self-service experience from machine screen
Connected laundry software shows the user the available machine, program, price and remaining time; it starts the program safely after payment. Availability and completion notification can be provided via mobile web or application. The operator monitors usage, income, error and maintenance status from a single panel.
Machine control and protocol layer
The touch panel or gateway communicates with the machine control card via Serial, RS485 or manufacturer protocol. The common model includes door_closed, schedule, phase, remaining_time, temperature, payment_ready and error_code states. Safety-critical controls such as the heater, drum and door lock remain on the device's own control card; the application only sends the allowed program launch request.
Reservation, payment and status machine
The machine goes through the states AVAILABLE, RESERVED, PAYMENT_PENDING, RUNNING, COMPLETED and OUT_OF_SERVICE. Short-term booking prevents the same machine from being sold to two users. When the payment provider reports success, the backend generates initiation authorization with the unique transaction ID. If the program does not start, the automatic reconciliation, refund or operator review flow is activated.
IoT telemetry and maintenance
Run time, number of programs, water temperature, door status and error codes can be collected via MQTT or HTTPS. Events and summary metrics are sent instead of continuous raw data. Repeated imbalance, drain or heating errors become maintenance indicators. Predictive maintenance should be added only after sufficient and accurate historical data has been accumulated.
demo scenario
The demo consists of two machine simulators, user screen and operating panel. The user selects the available machine, completes the program and test payment; the remaining time flows live on all screens. Startup is inhibited when the door is open. When the program ends, a user notification occurs, appears on the panel, and the work counter is updated. In case of connection loss, the machine is shown to continue the current program safely.
Field pilot and security
Payment–initiation consistency, device online rate, notification latency, and service time are measured during the pilot. Power outage, door sensor failure, payment repeat and gateway restart are tested. Audit logging should be implemented for device identification, signed update, kiosk lock, and admin actions.
Frequently asked questions
Can existing washing machines be made smarter?
If the control card has a secure communication or dry contact interface, it may be possible with the gateway; Technical approval from the device manufacturer is required.
If the internet is interrupted, will the running program stop?
It shouldn't stop. Real-time control of the program should remain on the local control board, while the cloud should only support operation and user services.