scope of this issue involves:

• the routes related to schedule
• the controller and the input received by the endpoints
• the services to implement and send the schedule logic to db and the particular device(s)

The logic for intelligently controlling the pump based on schedule and water level.

• Lower limit
• Upper limit
• Safety operation (turning off after a timeout, turning on based on the reservoir water level

It's a bit neater that way, so that we don't have to modify all the services for updating the implementation

For example, pump_state should not be pushed to water_level.
Just ensuring that generalisation is maintained while doing so

Add the following to this interface and the model:

    online: boolean,
    schedules: [Schedule]

Following are the necessary interfaces:

export interface Schedule{
    schedule_type: ScheduleType,
    trigger_type: TriggerType,
    repeat_on: [WeekDay],
    end_at: Date    //js built-in date class
}; 

Following are the necessary types:

export type ScheduleType = "on" | "off" | "dim" | "and" | "or";

export type TriggerType = "timing" | "device";

export type WeekDay = "monday" | "tuesday" | "wednesday" | "thursday" | "friday" | "saturday" | "sunday"; // note: I am sure there are alternative to this in-built.

Notes:

• only device with a valid linked_chip_id can be used as the external trigger device
• there is controlling device (usually an input device, with a valid linked_chip_id) and there is controlled device (usually an output device)

I am taking up this task