I suppose it’s time to just say it.
I’ve given up. Their engineers are great, smart people, but engineering leadership is, in my opinion, completely failing them. Do you recall the promise of an August general release? We’re almost to October… Promises made and broken again and again and again. Bugs and holes. I’ve lost my will to chase and press for what I need to get an eZLO version of Reactor done. I stopped in July, after three months of reporting bugs and holes, literally begging for changes, and waiting months for fixes, which came piecemeal or not at all (but “it’s on the roadmap”). The quality of what I can produce is limited by what they produce, just as it is with current firmware. After more than two years, they’re still not ready, and IMO it’s simply because of leadership failure. I can’t see that there’s any forethought to anything, from the start to today. They’re playing whack-a-mole when they need to be playing chess.
Still no sign of that. No sign of any mechanism to build GUIs for configuration like Reactor’s configuration editors. But there’s effort on 100 other things. Following these threads of late, it’s clear they are building something with so many moving parts that it’s fragile beyond belief… if it’s not a firmware bug, it’s a mobile app bug; if not that, it’s a problem with the cloud infrastructure. Distribute work across multiple controllers? How about something reliable on one?
I’m off building for other platforms now. I’ll support the current firmware as long as that’s a thing, but I won’t touch the new stuff again until I think it’s ready, I’m guessing at least another year still until it’s an equal to the current legacy firmware and a viable platform where third-party developers can build good quality products for it.
P.S. If I end up getting banned for sharing this opinion, you can use Github issues for each plugin for questions and problems; there’s also an email address in the Troubleshooting section of any ReactorSensor’s tools tab.