- This topic has 1 reply, 2 voices, and was last updated 5 years, 2 months ago by
.
-
Posts
-
Hi guys,
Just say you send an enable command via the api:
http://ip/cm?pw=xxx&sid=4&en=1&t=600then send another one with a new time before the original time runs out:
http://ip/cm?pw=xxx&sid=4&en=1&t=1200is it supposed to turn off the master and then just loop? This is what i’m seeing on my ospi (app v1.8.2 / firmware v2.1.8(2)).
I’ve played with the master delays for both on and off but they dont make any difference. As soon as a new command is issued, the master turns off immediately.
Example attached!
Attachments:
OK, I will check this weekend. It’s probably a bug. With normal programs, the same zone is not allowed to be queued twice, so if it’s already running, a new schedule for it will be ignored. However, for /cm, the firmware accepts the new time and overrides the existing schedule, this may have messed up the time for master zone activation, resulting in the symptom. The corresponding line of code is here:
https://github.com/OpenSprinkler/OpenSprinkler-Firmware/blob/master/server.cpp#L1635
I suppose that instead of accepting the new time, if you ignore the new request (while the same zone is still running) it should not have messed up with master zone activation. In any case, I will check and find a fix soon.
- You must be logged in to reply to this topic.