Unfortunately no one else seems to know what he is referring to, or at least no one has acknowledged that they do. He might not be in a position to say, or it might not be in his interests to do so, so that is fair enough. It just doesn’t help the understanding of the wider community.
The ‘API Only’ / OAUTH apps are a somewhat different kettle of fish to the endpoint apps. At least they seem that way to me as I’ve had no involvement with them.
Endpoint apps of the complexity of the old ‘market place’ Groovy apps have been live for years now, there just doesn’t seem to have been much interest in them, or at least not in sharing them. They are pretty easy to install by numbers if they are already being hosted, the real problem can be in having somewhere to host them and an understanding of what that entails.
Well how about we ask th ST community to write a new version of LUM so we can get on with it.
We could ask ST users what top five smart apps we want and get some developers to write and host them .
Let’s get proactive.
One community member already has an endpoint smartapp for lock management, you might take a look at that and then talk to him to see if there are features missing.
Or start a new topic for any specific app you would like to see transition to the new platform and see who’s interested. But keep it to one smartapp per topic or it’s going to get really confusing.
I was adding lockmanager.io to my setup and noted I still have a list of IDE apps installed. I can’t seem to delete them from the app. Smart apps are no longer listed in IDE. How do I get rid of them?
I’ve noticed Hue appeared as a driver - and in the Hue hub device once the app refreshed - no noticeable effect on behaviour. In the (old) web GUI all bulbs except one show as placeholder.
Has anyone found a way to BATCH force (or script) Thermostats to change from DTH to Edge?
We have about 200 GoControl Thermostats across a dozen hubs. Doing a z-wave exclusion + inclusion per device is cost and time prohibitive. We ran one thermostat through the process, and indeed SmartThings picks it up as an Edge Driver.
How can we force all hubs to switch to Edge Drivers for this make/model.
Seems like the problems started for me. All hue devices no longer work. I made a mistake:I went into the hue hub and tried to change the drive. I put that drive back and now nothing works
Sounds like he may be using a Hue Hub as well as a ST Hub. I have my Hue bulbs connected directly to my ST Hub (I don’t have a Hue Hub) and have no problems.
I’ve seen hue hubs appear with edge drives, but all hue devices stay connected with device handlers. I then tried to change the edge drive to the hue hub, to see if they still worked, to understand if there is a connection between the hub and the hue device in the SmartThings app. After switching drives to bose drive , the hues obviously no longer worked. What got me confused was that when entering and exiting the drive selection, it indicated The correct one but nothing worked. This morning in the same menu I looked again, and it indicated bose drive in hue hub, I changed it to hue drive and now everything works
With bulbs connected via a V2 Hue hub no issues noted (note https://support.smartthings.com/hc/en-us/articles/9339624925204#h_01GCZRYTHHAK3X0P31WS7SQ2YE V1 hub not supported)
I’d rather keep the Hue hub rather than connect bulbs directly to ST, but for Alexa not having the Hue skill (so just the ST skill) avoids duplicated bulbs.
One bulb wasnt showing as placeholder in the old web GUI - so just for tidiness deleted and re-added it (as done before with some other partly migrated devices) - adding deleted devices back into scenes is much easier in the app these days.
I talk about it here but correct me if I have to make a new post, it seems to me related to the SmartThings transaction, that’s why I write here:We’ve all seen hue changes these days, and the appearance of the hue hub between devices. Nonetheless, the devices always seem to be connected as before, in fact they are still in the hue.
However, if I try to add a new device, by searching for hue, it comes to this page
I select hub, I get duplicates of all the lights. They have more functionality than what I have now, but then the automations are in the cloud. How do you behave? Are you waiting for the automatic switch? I don’t know which hue to keep anymore
Perhaps things are slightly different, I have reconstructed how things are, I would like you to tell me if you think this is the case:
Many spoke in this post Why SmartThings has installed unnecessary Wemo etc drivers to my hubs useless drives appearing in their hub.
Perhaps the new edge hue drive available in beta mode on the samsung drives page has now been added in a non-beta version to hubs without it? After trying to install the beta hue drive, I no longer see the standard hue drive. It has been overwritten, although It has been overwritten, even if I thought the drive was exactly the same, I notice that in addition to the date, the number also completely changes:
Beta 2023-05-02T19:26:15.23063733
not beta 2023-05-23T18:29:49.565838074
now i have the beta drive, because i have no way to install the new one that was installed automatically
It looks like it was rolled up from beta to production on Tuesday 23rd May. My understanding is that as part of that process they deploy a new package which is why the version number is different.
They presumably have to do something extra in order for LAN drivers to be installed on hubs where they have to be for discovery to work. Whatever that something is would appear to have happened last week.
