GuitarBuilder Posted June 24, 2015 Posted June 24, 2015 Would it be possible to support the Blossom Smart Watering Controller in the future? It seems like an innovative product: http://myblossom.com/
Teken Posted June 24, 2015 Posted June 24, 2015 Is the blossum insteon-enabled? No, I believe the OP is asking for native support via their API protocol. This would require the network module to perform any kind of integration with the two systems. Sadly, I don't believe we will ever see any third party vendors making Insteon enabled products. NOTE: Just took the time to read their FAQ. It appears there is no API ready for third party vendors so this will make ISY integration impossible until they do. They also indicate it uses power line Ethernet along with WiFi so that's a nice plus for connectivity.
Jimbo.Automates Posted June 25, 2015 Posted June 25, 2015 I have one of these and it works really well on its own. I emailed the company before purchasing about the api and they said it will be coming soon. I can ask again to see if they have a better idea when it will be available. Sent from my Nexus 7 using Tapatalk
oberkc Posted June 25, 2015 Posted June 25, 2015 So....given all these things, what can be done with an API? Does this mean, simply, that it is easier to write commands through the network module (don't have to try to figure such things out so much)? Is this what it means to have "native support"?
Teken Posted June 25, 2015 Posted June 25, 2015 So....given all these things, what can be done with an API? Does this mean, simply, that it is easier to write commands through the network module (don't have to try to figure such things out so much)? Is this what it means to have "native support"? In the truest form of the meaning native if we relate to Insteon for example. If this device had an embedded Insteon chip and the ISY supported it. It would have native support because all of the requirements would be met to allow connectivity. With a open API data sheet the availability of such would still require someone to figure out what commands were required to make certain functions operate. In the above that is not considered native per say but allows device access and the possibility of integration and interaction with a controller etc. This is how I see and use the phrase *Native Supported* but I am sure others would differ so I digress. Ha . . .
Recommended Posts
Archived
This topic is now archived and is closed to further replies.