The IDE is a great, feature-rich, powerful environment for configuring and managing systems. It may not be the most intuitive app in places, but it sure brings together everything you need under one roof.
I’m absolutely shocked they would kill that and not have something as elegant and powerful to replace it. It feels like a huge step backwards.
Is there something fundamental about the architecture of everything running locally on the hub that precludes having such a tool?
Your list of what so far is missing in the ED world is excellent. It’s a shocking list and indicates a huge step backward. It is also shocking that Samsung is not clearly addressing the whole migration plan and telling the community which features will not be needed, which will be deprecated, what the new world will look like, etc. I feel like one of the blind me trying to figure out the elephant.
On top of all this, where and how does “Matter” fit in? Does Matter mean yet another such transition will be coming up?
Not to put too fine a point on it, but I think Jasco is the designer and manufacturer. They are not licensing the GE, Honeywell, etc name. Rather GE, Honeywell and others OEM the Jasco products and sell the products under their own brand name.
It’s always been a licensing agreement, where Jasco licenses the names of big brands, including GE and Disney, and then relabels some of the Jasco devices under those names. It’s a common industry practice in HVAC and plumbing, including for water heaters.
They have a similar arrangement with Honeywell:
The other way to do it is what Tuya does, where they are an OEM to client companies like Moes and Zemismart. That’s probably what you were thinking of.
Matter will be another way to integrate other companies’ devices into SmartThings. This will be through Edge Drivers for some devices. There are already a few Matter Edge Drivers in development, although there are as yet no end devices to test them with.
No one has said as yet what will happen to devices that offer both an existing integration AND a Matter integration, like the Philips Hue hub, so no telling how transition might work. It may vary from model to model.
Is there something fundamental. Eh not really. But your hub really isn’t the best place for it. The hub already is memory constrained and some people who have a lot of devices and / or drivers already find they have issues and some blame recent zigbee weirdness on the memory issues.
Either way adding a HTML application server on top with management tools probably wouldn’t help. Instead they gave us the CLI and api access. That’s a good start and how it SHOULD be done(it would allow folks to write thier own tools) but let’s just say the tools they provide end users at the present time are less than adequate. There’s nothing saying they can’t improve…
I don’t see them ever supplying a comprehensive web interface local on the hub itself. I would see it more as a subset of the existing IDE with more device details (fingerprints, routes), some utilities (changing zigbee radio channel, rebooting the hub). The cloud clearly can’t go away - its still being used for all data storage, mobile access relay to the hubs, API requests, rule API execution. No reason that device fingerprints and routes can’t sync and be displayed just like they did in the IDE.
I suspect they will add more of the management side of the existing IDE to my.smartthings.com for things that “fit” better on a web interface vs a mobile app.
I’m still surprised that your hub syncing configuration data to a cloud web IDE-like interface for the services you both describe isn’t part of the v1 rollout. Without that comprehensive view, are we supposed to look at each device individually?