So now with the launch of eISY r2 the eISY that is currently broken most cases, plugins that don't work and now you are kicking that to the curb to roll out another $600 piece of hardware that God knows if it will even work?

Is that what this company is coming to?

Well wait a sec...what's not working with yours?

Most of us here are happiily using our controllers. Not everything is perfect, but it does what it does well.

Been using it for YEARS, almost a decade now. ISY, eISY.. Lets go with the basics. Govee and TP-Link Kasa has not been stable for the last 2 years. Home unit has been in such horrible shape using just those 2 has been nothing but a nightmare. Now I can't even login to the Admin via Portal to configure the eISY for the new network at a client location. Then I read you're pushing new hardware. You got a Release version of Kasa and a Beta Version of Kasa, both have the cons that make it un-usable. We have basically stopped upgrading because EVERY time we do something goes ape snitz. That's not a good sales pitch. Honestly we have been Beta Testers for eISY for the last few years. Buy something for $600 and you're a beta tester. I have never heard of such a thing. EVER! And saying Beta is being nice. This isn't even Alpha worthy. To put it into a clear picture. I use to refer people to ISY left and right. I have referred zero (0) to eISY. That's the reality of it.

Edited 3 hours ago3 hr by TRI0N-1
More to add...

With plugins / integrations / whatever, its a cloud service vendor API change epidemic that has nothing to do with eisy/udi in particular.

Here's the victims list of Home Automation controllers affected by unanticipated API changes across Govee, TP-Link and Kasa:

Home Assistant, SmartThings, Hubitat, Homey, govee2mqtt / hacs-govee bridges, openHAB, AND... UDI eisy/Polisy

Go ahead and jump to something else, discover the exact same problems and restart the discussion there.

Edited 17 minutes ago17 min by paulbates