I own a number of “smart” devices (SmartThings, IP cameras, ISY, MyQ, Insteon, August), some that were even Kickstarter projects - but if I’m honest with myself (and your team), Iro is the least polished of them all. The gen 1 hardware felt amazingly ‘cheap’, seemed to have an inadequate network stack, the flash-up gimmick proved to be just that, and the product lifecycle was just 1 year. For a sprinkler controller that competes with products that last as long as houses - I’d call that less than success.
I like the promise of the product offering, but when smart devices do dumb things - they can actually be more hassle than their non-smart equivalents. For example, if I were to have reinstalled my old dumb sprinkler controller this weekend I wouldn’t be getting hundreds of spam alerts, posting messages on forums, or rebuilding my schedule for the 3rd time to take advantage of the latest shiny as-needed dart toss. Maybe it will be great, and for your sake I hope it is.
Hardware is hard, web services are hard, products in general are tough. But you’ve also made promises to your clients in exchange for actual money. These things are shipping under the banner of “production” ready, not beta or preview (aside from Flex, which was labeled beta but still part of the marketing pitch). Maybe you need to consider soaking releases with a pool of customers who are willing to exchange their time and stability for access to early features?
I’m going to give Iro one more release cycle to get “right”, and if things don’t go well I’ll pitch it. I am rooting for you, but I also value my time and can only fuss with this thing so much. Your team thinks about Iro all day, but your customers buy the Iro to do exactly the opposite.
(while I wrote this post I received 40+ push notifications)