Known limitations
What the integration cannot do, or only to a limited degree.
| Limitation | What it means |
|---|---|
| Every 5 minutes | The integration polls every 5 minutes, not in real time. After an action it polls again right away. |
| Pro only | Spooly Pro (the trial counts) and the enabled API are required. If Pro expires, the entities report “unavailable” until Pro is active again. |
| Printers with the same name | Spooly delivers no printer ID. Two printers with the same name cannot be told apart. Only the first slot with that name appears, with a warning in the log. Give your printers different names in Spooly. |
| 10,000 calls a day | The limit applies per account across all connections. The integration uses about 1,450. |
| Changes | Per connection at most 60 changes a minute, 500 a day and 100 new spools a day. |
| No events of its own | For low spools there is the Low binary sensor, but no event of its own. |
| No picker for the storage location | You change the storage location with the action spooly.. |
| No forecast | The integration provides no flow rate and no forecast of how long a spool lasts. |
| Deleting and printers | The integration cannot delete anything for good. Printers cannot be controlled. |