Discussions

Could you consider adding API routes to signal when a particular irrigation zone starts/stops, to feed into your detection algorithm and provide some "ground truth"?

I'm thinking something like one resource for irrigation zones, (many irrigation zones per location), with properties like a name, type of irrigation (spray, drip, etc), and maybe some others.

Then you'd expose a POST or something for the zone that would allow an api client to specify an array of (optional start time, optional end time) pairs.

I'd like to use this with my wifi irrigation controller and home assistant, but it could also make for the beginnings of a great IFTTT app for users without their own local hub.

If you provide appropriate permissions, you could perhaps even partner with a handful of smart irrigation controller providers to set up webhooks or something for your shared users.

Let me know if this is something you'd be interested in collaborating on; I'd be happy to provide further ideas.