I am not sure if this is as much a scripting/plugin question as it is a sprinkler device question. But, here goes...

It seems the only way to turn off a sprinkler zone is trough indigo.sprinkler.stop() which stops all zones, active or not. There is indigo.sprinkler.turnOnZone() but no indigo.sprinkler.turnOffZone().

Is this a limitation of the actual sprinkler controller or an implementation decision in Indigo? If it is the latter, then I would like to request the addition of a means to turn off a single zone like: indigo.sprinkler.turnOffZone() or, if possible, like: indigo.sprinkler.stopActiveZone().

The reason for this request is to reduce INSTEON traffic and log clutter and, mostly, for faster response times.

Thanks.

What's the difference between indigo.sprinkler.stop() and what you want indigo.sprinkler.turnOffZone() to do? Since only one zone can be active at a time, they are fundamentally identical.

indigo.sprinkler.stop() sends an INSTEON command for each output:

[list=] Sent INSTEON "Irrigation Controller #1 - f-lawn" off (ack: all valves off)
Sent INSTEON "Irrigation Controller #1 - f-patio" off (ack: all valves off)
Sent INSTEON "Irrigation Controller #1 - f-hill-lwr" off (ack: all valves off)
Sent INSTEON "Irrigation Controller #1 - f-hill-upr" off (ack: all valves off)
Sent INSTEON "Irrigation Controller #1 - drive-kitch" off (ack: all valves off)
Sent INSTEON "Irrigation Controller #1 - bk-patio" off (ack: all valves off)
Sent INSTEON "Irrigation Controller #1 - bk-yd-outer" off (ack: all valves off)
Sent INSTEON "Irrigation Controller #1 - bk-yd-inner" off (ack: all valves off)[/list]

I would like to just send the appropriate command, not all 8.

For safety (power line noise causing a missed command, etc.), Indigo always turns off all of the valves. There is no way to override this.

Thanks.