brendan_muir

Awesome. Thanks for the additional info. I look forward to the future release!

Aha... no internal clock is a problem for what we have been proposing! That helps me better understand why the ISY interfaces with the EZ-Flora like it does. Thanks for clarifying things and for providing some insight that I have more due diligence to do on the mesh topology. Your support and knowledge are top notch - it's refreshing and very cool to find a company and user community that stands behind its product and whose passion for the technology is apparent in the knowledge and assistance it delivers to customers. Thanks for all your help gentlemen. I look for ward to future interactions as we continue to explore and kick the tires on the ISY.

We would like to supplement the features of the irrigation add-ons Universal offers, with our own science, data and irrigation strategy. We have a strategy that is more narrowly focused on water conservation. We are planning on testing our conservation platform in a group of beta-test homes this coming spring. We wanted to write directly to the EZ Flora for instances where the ISY drops offline or is unavailable for some reason - it is really a layer of backup protection since our goals and credibility are dependent on bullet-proof accuracy and reliability of the irrigation functions. If an ISY dies or is misbehaving... or being firmware upgraded, etc... We wanted the EZ-Flora to be self-sufficient for a stint via the internal program functions... kinda like emergency auto pilot.

Thanks for the prompt reply!! I surely understand both the technical and strategic reasons why you would not expose a functionality in the EZ Flora (or other devices) that you have already accounted for with a proprietary solution in the ISY. I see that the ISY provides a much more comprehensive way of extending and orchestrating the composite of devices comprising a smart home or automation network. For my purpose, I need to regularly update the program that controls the sprinklers attached to the EZ Flora from the REST or SOAP interfaces. I've had trouble piecing together how to create or update an irrigation program that would be orchestrated by the ISY - do you have any additional information or examples of the Irrigation programs configured and changed in the ISY using the service interfaces? (variables, etc.). I haven't had my aha moment yet and so things still seem a bit cryptic to me. I've spent some time searching for samples, but to no avail. Thanks again for all your help!

I was wondering if the ISY's REST service layer exposes the functionality required to store/persist new program start and run times in the EZFlora? I have looked, but haven't seen anything yet. If there is not anything native, is there a way to use the ISY to send native Insteon commands to the EZ-Flora and/or any other Insteon device? I can store/persist program start and run times to the EZFlora via the PowerLinc... so I was wondering if there is a way to do this with the ISY. (I have an ISY994i) Preferably I would like to do this via the REST service layer. If this is not possible yet, but could be added, please let me know. Thanks in advance for as prompt of reply as possible.