Tumblers are credited only at the end of the cycle. Meaning the logic of scanning for our washers at idle -> busy state to upgrade busy -> running will not work.
This seems like a fundemental limitation, and no other API endpoints seem to give this information until at the end of the cycle.
Attempting to guess our use for tumblers seems extremely fragile. A notify event could be implemented instead for each machine (polling on idle -> busy or busy -> idle defined per machine type). But this makes the idea of running redundant/fragile to rely on. Architectually, this is quite the problem.
Tumblers are credited only at the end of the cycle. Meaning the logic of scanning for our washers at
idle -> busystate to upgradebusy -> runningwill not work.This seems like a fundemental limitation, and no other API endpoints seem to give this information until at the end of the cycle.
Attempting to guess our use for tumblers seems extremely fragile. A notify event could be implemented instead for each machine (polling on
idle -> busyorbusy -> idledefined per machine type). But this makes the idea ofrunningredundant/fragile to rely on. Architectually, this is quite the problem.