Laundry IoT: online does not mean ready to use

Knowing that a machine is online is useful, but it does not answer the customer’s question: can I start a service now? An IoT integration needs to present information with its context, source and time. Separate communication status from operational status and avoid decisions based on an old signal. This matters especially when selling a service depends on remote activation.

Define what each signal means

A periodic signal may show that a device is connected. A start event means the machine acknowledged a cycle. A completion event represents another stage of the journey. Document which signals each model supplies and which states are inferred. Different equipment may provide different information; a consistent interface should not hide that limitation.

Show when information arrived

Each event needs an equipment reference and a time. Distinguish the time reported by the device from the time the server received the message. If the last contact exceeds the agreed limit for that integration, mark the information as stale. The limit depends on the equipment and its expected behavior; there is no universal interval suitable for every installation.

Plan disconnected behavior

Decide which actions are blocked, what guidance customers receive and how operators find pending transactions. Messages may arrive late or out of order after reconnection. They must not overwrite a newer state or trigger an action that has already completed. Test recovery through a supervised connectivity-loss pilot while respecting the installation’s technical limits.

Use data to make decisions

A useful view combines reliable availability, confirmed cycles and incidents needing action. Track the age of the latest information, periods without communication and payments waiting for an operational response. For example, a connected machine that does not acknowledge commands belongs in a different incident category from an entire site without internet. This distinction helps teams investigate the right cause and inform customers without inaccurate promises.

Implementation checklist

• Document the signals available for each model.
• Display information time and quality.
• Test delayed, repeated and out-of-order messages.
• Separate connection status from operational availability.