Automations in Cpehub
Automations let Cpehub work for you: instead of repeating tasks manually, you define when something should happen (the trigger) and what should be done (the action).
The trigger → action model
Triggere.g.: TR-069 event
Conditione.g.: manufacturer = Huawei
Actione.g.: apply tag / config
Real automation examples (from the system itself):
- Add tag to all Huawei devices — on the Periodic event, adds the "Huawei" tag to Huawei devices.
- Update C20 — updates C20 units to the ISP-approved version the first time they connect to the ACS.
- CPE Detected / Reset — runs when a CPE is added to the ACS server.
What's in this section?
| Page | What it's for |
|---|---|
| Create an automation | Step-by-step guide to building an automation. |
| Automation examples | Ready-made cases for inspiration. |
| Create and use Scripts (OMCI) | Command sequences applied to CPEs. |
| Tags | Tag CPEs to filter and automate. |
| Manage Firmwares | Upload and apply firmware via TR-069. |
| Execution queue and logs | Track what's running. |
Automation × Script — Which to use?
- Automation: reacts to an event (trigger) and runs an action — ideal for "whenever X, do Y".
- Script (OMCI): a sequence of commands you apply to one or more CPEs, on demand or within an automation.