Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeline information #173

Open
han-alink opened this issue Jul 29, 2024 · 4 comments
Open

Timeline information #173

han-alink opened this issue Jul 29, 2024 · 4 comments

Comments

@han-alink
Copy link

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@han-alink
Copy link
Author

When pausing a schedule, the timeline is immediately filled with the time of the complete schedule. Lateron when the schedule is resumed, again the complete time of the schedule is added to the timeline. So, the timeline indicates double the value of the intended time. Not a big deal, but it would be nice if the states of the schedule could be taken into account.

@han-alink
Copy link
Author

I have to add that a resumed schedule is not generating a " irrigation_unlimited_finish" event when it ends.

@rgc99
Copy link
Owner

rgc99 commented Aug 14, 2024

I have eliminated some doubling up between history and the running schedule.
The irrigation_unlimited_finish event is firing and the end of a resumed sequence. Perhaps it was fixed in the latest update.

@han-alink
Copy link
Author

Thanks; solved my issues ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants