General > Irrigation Control

Hydrawise 12 Zone Wifi Irrigation Controller

<< < (3/4) > >>

camryan:
Our local API is in beta at the moment. The commands will be a subset of the API I posted before but in the initial version you'll be able to query zone status and manually start/stop zones which is probably the majority of what you'd want to do anyway.

Cameron

guessed:

--- Quote from: camryan on August 21, 2014, 08:57:47 pm ---Our local API is in beta at the moment. The commands will be a subset of the API I posted before but in the initial version you'll be able to query zone status and manually start/stop zones which is probably the majority of what you'd want to do anyway.

--- End quote ---

Yup, that'd be what an initial Vera plugin (or openHAB Binding) would want to cover, along with the need to express to either disable or delay the schedule for some period of time (if the HA Controller detect the right weather conditions, or switching to "Party mode", as examples)

Do you need new Beta testers?  More than happy to buy a controller to participate in that type of program.

camryan:

Sure - you're welcome to test it out! If you order through our website then you'll get free shipping.

guessed:

--- Quote from: camryan on August 22, 2014, 12:29:07 am ---
Sure - you're welcome to test it out! If you order through our website then you'll get free shipping.

--- End quote ---

Ordered a 12 Zone unit and a flow meter. 

I read through the API doc and the main questions I have so far:

a) Do you have an expected min/max rate of polling?
Some services don't like it when you poll too often, so do you have a min spec on how often we're allowed to poll the service?

b) statusschedule.php/running/water is documented as a String, is this correct?
Also, what is the baseline "date" that's used for the water consumed?   Is it the total amount of water used ever, or each day/week/month?

c) statusschedule.php/master is documented as type "seconds", I think it should be "integer"

d) statusschedule.php/running/water is the only place to 'read' the flow meter.
So it looks like I can only read the attached flow meter when a watering cycle is in process.  How do I go about reading it when the cycle isn't running.
ie. Water leaks due to broken valves (etc) - since a single flow meter will cover all of my valves

This is my primary reason for replacing the system (a $400 water bill a few yrs back, due to a stuck valve)

e) Some of the time fields are EPOCH (integer) and some are string, is this intentional?
If they're String, what TZ and format are they?  In some cases, the units are seconds, and in others they're minutes or something else.

eg. run, time, timestr, nicetime, last_contact, watering_time, time_left

Do you have some sample JSON output that can be used as a reference?  I can work off the live stream, but prefer to work against a documented (vs observed) behavior for this type of stuff - esp when i18n might come into play.

f) Where's the best place to provide API feedback?

camryan:
a) Do you have an expected min/max rate of polling?
We don't but we are considering adding this just in case there are bugs in people's code :)

b) statusschedule.php/running/water is documented as a String, is this correct?
That's correct. It will say something like "50 gallons" or "50 litres" depending on your location. It is the amount of water used for the currently running zone.

c) statusschedule.php/master is documented as type "seconds", I think it should be "integer"
Correct - cut and paste error :)

d) statusschedule.php/running/water is the only place to 'read' the flow meter.
This functionality isn't exposed at the moment. If you email support@hydrawise.com then we will explain how to get this.

e) Some of the time fields are EPOCH (integer) and some are string, is this intentional?
Yes it is intentional - one is just a local representation of the other. String is in your local timezone. I find string useful if you don't want to have to convert timezones, etc - we do this for you :)

e0) Do you have some sample JSON output that can be used as a reference?  I can work off the live stream, but prefer to work against a documented (vs observed) behavior for this type of stuff - esp when i18n might come into play.
We don't - we assumed people would work off the live stream :)

f) Where's the best place to provide API feedback?
Best to open a support case at support@hydrawise.com - that way things won't get lost in my email inbox.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version