Error history

Single-file API example

Not connected

The same API login as Cycles. Your bearer session is remembered until logout or expiry; your API key is never stored.

Open this example locally

Save this one file as errors.html. In its folder run python -m http.server 8080 --bind 127.0.0.1, then open http://localhost:8080/errors.html and choose your tenant and environment. Internet access and an updated API are required. Opening the file directly supports the demo only.

Required permissions: Errors2 (17), Bank Read, Location Read, Unit Read and matching resource grants. Acknowledgement also requires Unit Write. Normal manager and tenant checks apply to every page.

Machine events · Errors2

Error history

—

Explore a bank’s machine errors by period and severity. Read the event details or acknowledge an error after review. Acknowledgement keeps the log and does not change the machine’s status.

Not updated yet

Connect and choose a bank, or try the demo.

Error events will appear here.

API operations and limitations

Read access requires Errors2 (17), Bank/Location/Unit Read and matching grants. Acknowledgement additionally requires Unit Write and fresh authorization. All events within 1–70 days can be paged; the legacy four-per-machine limit does not apply. Results are ordered by location, machine and newest event, then source.

Descriptions come from the stored event. The obsolete DatPro2 error-description catalogue and its editor are not exposed. Structured details expose only the error code, Miele count and Miele/Electrolux text. Missing data stays unknown. Current machine type uses only the original packed UnitType. Print is a local, read-only view of the selected detail.

Acknowledgement writes Period=1 and preserves the original event. It does not repair or restore the machine. A 409 response requires a fresh read. If a write response is lost, read the event again before deciding whether to retry. This example never retries a POST automatically.