I have run into the following issues when the adjustment is 0%
in order to adjust the watering time I manipulate the settings in gv.rs so in the following example station 1's watering time is reduced from 60 seconds to 0 seconds and the start and end times are now the same:
This however leads to the program being "stuck" in scheduling status (see screenshot), but according to the logs the program timer seems to be active (see code) :
Seems to be an issue in sip.py line140/141?
in order to adjust the watering time I manipulate the settings in gv.rs so in the following example station 1's watering time is reduced from 60 seconds to 0 seconds and the start and end times are now the same:
Code:
before [[1712903940, 1712904000, 60, 1], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0]]
after [[1712903940, 1712903940, 0, 1], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0], [0, 0, 0, 0]]
This however leads to the program being "stuck" in scheduling status (see screenshot), but according to the logs the program timer seems to be active (see code) :
Code:
::ffff:127.0.0.1:55828 - - [12/Apr/2024 06:39:07] "HTTP/1.1 GET /api/log" - 200 OK
::ffff:127.0.0.1:40388 - - [12/Apr/2024 06:40:07] "HTTP/1.1 GET /api/log" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:43] "HTTP/1.1 GET /" - 200 OK
::ffff:127.0.0.1:46308 - - [12/Apr/2024 06:40:43] "HTTP/1.1 GET /api/status" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:43] "HTTP/1.1 GET /api/log" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:44] "HTTP/1.1 GET /api/status" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:45] "HTTP/1.1 GET /api/status" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:46] "HTTP/1.1 GET /api/status" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:47] "HTTP/1.1 GET /api/status" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:48] "HTTP/1.1 GET /api/status" - 200 OK
::ffff:127.0.0.1:46292 - - [12/Apr/2024 06:40:49] "HTTP/1.1 GET /api/status" - 200 OK
Seems to be an issue in sip.py line140/141?