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 Wednesday at 08:12 PM1 day 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 Wednesday at 11:21 PM1 day by paulbates

As Paul mentioned, cloud dependancy is an entirely different problem, and would be the same problem with integrations on another platform. There seems to be a slight shift towards some manufacturers recognizing that and the frustrations caused. Some like Somfy have opened up local access as a developer mode. Yolink's new hub has local access. Others like the MyQ garage door opener have cut out local access, keeping it only for certain chosen integrations. I hope a general trend towards opnness develops. Time will tell.

8 hours ago, Guy Lavoie said:

There seems to be a slight shift towards some manufacturers recognizing that and the frustrations caused

We have to keep in mind that us Home Automation controller types are not the main market for the products in question. It's the customer base of hundreds of millions of potential buyers who could use the product via the vendors' apps on their phones.

The priority for those manufacturers is keeping their own product ecosystem whole. Or, the major ecosystems that Matter is being designed and built for: Apple, Google, Amazon, Samsung. Probably one of the best table scraps has been Apple's HomeKit Accessory Protocol (HAP) that a number of vendors have adopted as simpler, easier to support interface. It's typically lacking in complexity, but numerous vendors have adopted it.

However, Apple announced a while back that it's done updating HAP and their integration direction is Matter. If you have something that uses HAP now, nothing should break it. If you're looking to future proof against this kind of problem, matter & thread is the kind of direction you have to think about now. It's still in its infancy IMO and other problems for things like lighting are lurking in there.

So when we say "I'll stop buying product X and start buying Y because their changes broke my house", we're likely to be jumping from the frying pan into a different fire. We also don't help ourselves by demanding a subscription-less yet complex products and want them supported for years. That creates the "Sell once, support forever" business model for the manufacturer, they give up and there's a growing pile of stranded products in our homes as a result.

The grass is always greener when viewed from an acute angle.

My home runs on a combination of my Polisy and Home Assistant. I usually find that what one doesn't control, the other will.

90% of what I have is controlled by my Polisy. I access it only on my PC as I find it easier to make changes on the big screen.

Mrs. Athlon prefers the 'Home Page' I created in HA on her phone to control stuff like individual zones for heat and A/C.

1 hour ago, Athlon said:

My home runs on a combination of my Polisy and Home Assistant. I usually find that what one doesn't control, the other will.

90% of what I have is controlled by my Polisy. I access it only on my PC as I find it easier to make changes on the big screen.

Mrs. Athlon prefers the 'Home Page' I created in HA on her phone to control stuff like individual zones for heat and A/C.

I use EISY for all my Insteon lighting, nothing comes close for functionality. I have a couple of Zooz switches on the EISY as well.

However, I use HA for all my utility needs like zigbee sensors and smart plugs. I find EISY support very limited and/or clunky compared to HA for these devices.

28 minutes ago, mmb said:

I use EISY for all my Insteon lighting, nothing comes close for functionality. I have a couple of Zooz switches on the EISY as well.

However, I use HA for all my utility needs like zigbee sensors and smart plugs. I find EISY support very limited and/or clunky compared to HA for these devices.

Pretty much the same here. Definitely HA for sensors - their equivalents to Polyglot seem to react to manufacturer API changes/firmware updates and upgrade often in a timely manner.

I do prefer my Polisy for scenes (routines) however - probably because it's what I'm used to, they work great and are easy for me to program.