Robert Cook

The `next_start` attributes along with `next_name` and `next_duration` are dynamically displayed. If there is no next schedule then they are not displayed. It may be best to use the `next_zone`...

Here I have used your config and disabled zone 1. Notice the `next_start`, `next_duration` and `next_name` fields are missing. Compare that to zone 2 which is enabled.

Struggling to reproduce this. I need the log entries in particular the service calls i.e. ``` 2023-05-26 22:55:21.212 INFO (MainThread) [custom_components.irrigation_unlimited] CALL [2023-05-27 08:55:21] service: disable, controller: 1, zone: 1,...

Unable to reproduce this on my development machine. It may have been fixed as part of some other work in this area. A lot of the parameters to the service...

What about creating a sequence and then firing it as a manual run? Just remember the `time` is the total duration so you would need to run the sequence for...

At the moment you would have to create three sequences. There is no limit to the number of sequences.

All sequences are independent of each other. They may overlap in which case a zone will be on if one or more schedules turn it on and off when all...

Changes have been made to allow manual runs to be queued. You can queue individual zones or entire sequences. The code is in the repository but not yet released, please...

This feature is available in the current release.

What parts did you want to integrate? Please provide some background on what you would like to achieve.