I have personally transitioned all these to stock DTHs. Functionality may be less on the stock DTH, but at least seems like the transition will be better. Then you might want to post in the community and hope that a developer will pick up your request for a driver, such as in this post here: Post Requests for Edge Drivers Here (community-created) - you might eventually end up with identical functionality.
I suggest that for these, you install the driver and test at least one of each type of your devices to ensure it works well for you. My understanding is that if you then leave the driver installed on the hub, and as long as that driver has the correct fingerprint for your devices, then during the “great transition” our devices will be assigned that specific driver.
I thhink you are correct - if these are cloud integration requiring no groovy DTH or SmartApp, then they should continue to work.
Not sure about this. I could never use Smart Lighting as it was not made available to European users (or was taken away, whatever the case may be). Groovy SmartApps will surely be killed off, and I saw that there will be a replacement for Smart Lighting, but could not see about anything else. I think the prudent approach would be for you to assume that they will die (including - with certainty - WebCoRE), and to create Routines as a replacement for the functionality offered by those SmartApps. I know from what I have seen that sometimes it’s not like for like, and I know from personal experience that the 200 limit is ridiculous and to replace a piston with these Routines will eat away at your allocation like crazy, but that’s what there is on offer at the moment.
You have to find the specific threads for the drivers you need in this community and follow the link. the developer will likely p[ublish a channel, then you enroll with that channel, see the available drivers on that channel and install it/them. As long as you follow what the developer says on the thread, you will get the latest version - when the developer releases new versions of that driver they will automatically be installed on your hub. Yes, it carries some risks which are detailed above in this thread if you care to read it all, but again - that’s what is currently on offer. Instead of the Groovy IDE you now have to install and use the Smartthings CLI. Of course, it’s a bit of a pain and not much of a UI at all and one hopes that there will be something developed to replace the IDE. But once again, just saying what I believe are the only choices for you right now.
I will most likely transition what I can to stock DTH’s, specially all the Heatit Z-TMR3 thermostats I have.
Right now it’s a bit chaotic on the custom driver side, but I’ll try to find and install whatever drivers I can find for my devices, hopefully the transition will be seamless then.
Regarding the smart lighting, I did not know it wasn’t available to users in Europe, in any case I could never use it here in Norway. Let’s just hope it’ll be available for us in Edge.
Let’s hope for a proper interface because this CLI just sucks big time … same as Rules API, tried to use it with postman and it’s just so lame and not intuitive … Rules are too simple, Webcore was just the sweet spot
Is there going to be a stock replacement for the SmartWeather Station Tile? I’ve seen the question asked a few times in this thread and searched elsewhere in the forum and can’t find that it is. I can see some Edge drivers created, but the main one I found requires an always on computer to feed it, which I don’t have.
My use case is actually not really based on weather, its after the illumination values. I know it wasn’t great, but I found when I combined it with UV values, it was good enough for rudimentary “its cloudy or dusk” and turn the lights on type stuff. Just didn’t want the lights coming on all day with motion in the rooms that usually get bright sun most of the day.
I’m late to this game and quickly trying to get up to speed. I have a many webcore routines that have been running great. I know what I need to do as far as logic, and I’ve read through many of the posts here, but I have not seen a place to start understanding how I’ll create new virtual switches or other customizations. Can anyone point me at an FAQ or something else that puts me at the starting gate?
One last thing, will my existing virtual switches work? I do have a hub.
You could recreate your pistons as Routines, but since webCore pistons tend to be more complex, I would take a look at the SharpTools rule engine. Its capabilities should support all but the most complex pistons. There is a great community there that can help with rule design, and the developers are very actively involved.
So we’re about 25 days out from the sunset of Groovy, and I’m just not sure how we are all going to be “ready” on that date.
I have about 50 devices in my system. I’ve converted a little more than half of them over to Edge drivers. Some required some creative solutions by TAustin, Mariano, and philh30.
Of the remainder, I suspect about half will eventually be “uncommented” from the stock drivers.
But the rest - about 12 or so - don’t seem to show as available in any drivers I’ve found (though it is a PITA to search for them). What’s my option - wait and see what happens - or do I start requesting custom drivers be made for them now?
As far as I am aware, if a device is fingerprinted in a stock handler it should get migrated to a driver. What we don’t know is the order they are being tackled and this year there seems to have been an unprecedented number of new handlers and new fingerprints appearing and the activity barely seems to have slowed. So there will still be catching up to do. For example I’ve been waiting for the Sonoff S26R2ZB to appear and the same hopefully will apply to your Minoston which is fingerprinted in a handler.
Your Aeon Siren may already be in a driver but I am not familiar with it.
What happens if they’re not fingerprinted and there’s no custom driver available? I have several, including basic dimmers where this is the case. For at least a couple of those I see other devices of the same manufacturer in the fingerprints, just not my specific device.
At what point do the generic fingerprints start to pick up unlisted devices for the stock drivers? Currently they are not.
For example, my Minoston plug is a simple z-wave plug. Up until now, it would only pick up with its associated DTH. Since installing your Z-wave Masquerade, that’s the only Edge driver picking it up, and it won’t let me select another. This is with whatever stock drivers are loaded, not the beta ones.
I think the production drivers still have the generic fingerprints commented out, so you’d need to install the beta drivers to use that option. The generic fingerprints also aren’t currently pulling devices into Edge.
Just got my Minoston switch added as Z-wave Switch using the beta.
Can you explain what you mean by: “The generic fingerprints also aren’t currently pulling devices in to Edge”? If it added and has a “Driver” under the menu, isn’t it an Edge driver?
Edge Drivers installed on your Hub won’t allow the developer to have any sort of control over your device. They (developers) are not even allowed to uninstall that Driver from your Hub. The only potential problem would be if that developer pushes an update on that same Driver and he accidentally introduces a bug that may break some functionalities.
I can’t imagine a reason why anyone would do this on purpose, nor heard of anyone doing it on the past.
