Activates all jobs saved in the database, will be used when the server was restarted If a non-critical error occurs, for example the failure to setup a job, it will be returned This function will not cancel directly if an error occurs in order to preserve the automation system's uptime.

Creates a new automation which an according database entry Sets up the scheduler based on the provided hour, minute, and days of the week on which the automation should run.

Creates and starts a schedule based on the provided input data.

Stops all jobs in the automation scheduler.

Given an username and id, it returns a matching automation, whether it exists and an error.

Returns a slice of automations which a given user has set up Does not check the validity of the user.

Gets a schedule based on its id and its owner's username.

Checks whether a given Homescript has automations which rely on it Is used to decide whether a Homescript is safe to delete or not.

Initializes the scheduler.

Initializes the Homescript manager.

Returns a slice containing the user's Homescripts Each Homescript also contains its arguments as a slice.

Changes the metadata of a given automation, then restarts it so that it uses the updated values such as execution time Is also used after an automation with non-normal timing has been added.

Modify an already set up schedule After the modification was performed, the schedule is restarted.

Removes an automation from the database and prevents its further execution.

Aborts and deletes a schedule based on its id.

Sets up a scheduler which triggers the flushing of the HMS URL cache every 12 hours.

Given a jobId and whether sunrise or sunset should is activated, the next execution time is modified Used when an automation with non-normal Timing-Mode is executed in order to update its next start time.

X * 1 Megabyte.

Global manager.

Used for listing personal schedules.