Hi @sdgood
Send me the exact model and tomorrow i Will add
And color temperature range
The previous ones were the E12 white Chandelier bulbs and a GU10 bulb with colour capability as well as shades of white.
Sounds like you have the previous version of an Ikea bulb i bought recently which refuses to pair with my SmartThings hub.
I had to pair it with Hubitat to find out exactly what it was.
endpointId: 01
application: 20
softwareBuild: 2.0.022
inClusters: 0000,0003,0004,0005,0006,0008,0300,1000,FC7C
outClusters: 0005,0019,0020,1000
model: TRADFRI bulb E26 WS opal 1000lm
firmwareMT: 117C-4204-20022623
manufacturer: IKEA of Sweden
This does highlight an overall platform issue; if a product from a known manufacturer, (platform partner i believe) won’t pair with the hub because the exact fingerprint isn’t in the base driver or recognised by the hub (not even by the Zigbee Thing driver), how is the general public going to deal with these types of problems?
Hmmm looking in the code for the white-color-temp-bulb, I do see “TRADFRI bulb E26 WS opal 1000lm” but it didn’t pair.
That’s the trouble, mine are identical except they’re 980lm. I don’t think it’s the same ones you had before because I’ve never had issues with them pairing with ST. Getting onto an Edge Driver is the issue. I probably reset one of them 20-30 times last week trying to figure out what I was doing wrong and it paired up every time without issue. It just repeatedly grabbed a DTH instead of a driver…
I have the same ikea bulbs tradfri E26 WS Opal 1000lm and they only pair as groovy. Never edge drivers.
@sdgood @BlackRose67 @Shanapadila
Added three ikea model to this driver version
┌─────────────┬──────────────────────────────────────┐
│ Name │ Zigbee Light Multifunction Mc │
│ Version │ 2022-09-04T08:38:58.458796529 │
└─────────────┴──────────────────────────────────────┘
- id: "TRADFRI bulb E26 WS opal 1000lm"
deviceLabel: IKEA Bulb E26 WS
manufacturer: IKEA of Sweden
model: TRADFRI bulb E26 WS opal 1000lm
deviceProfileName: level-colortemp-2200-4000
- id: "E26 WS Opal 1000lm"
deviceLabel: IKEA Bulb E26 WS
manufacturer: IKEA of Sweden
model: E26 WS Opal 1000lm
deviceProfileName: level-colortemp-2200-4000
- id: "TRADFRI bulb E26 WS opal 980lm"
deviceLabel: IKEA Bulb E26 WS
manufacturer: IKEA of Sweden
model: TRADFRI bulb E26 WS opal 980lm
deviceProfileName: level-colortemp-2200-4000
Hi all,
I have a several questions/concerns regarding the forceful transition and shutting down of groovy on the 30/09:
- I have a several devices that can be used with a standard/stock DTH but I’m using custom DTH. What will happen to those? Transition to standard edge driver (with less functionality like the standard DTH) or the devices will stop working?
As an example here, I have 4 Heatit Z-TMR3 thermostats with custom DTH, I know I could also use a standard “Z-Wave thermostat” DTH on my previous attempts. Other examples are generic Zigbee dimmers
- I have a several devices that use custom DTH and I couldn’t find a standard DTH for. For some of those custom drivers have been made, what happens to those, automatic transition?
As best example here, I can mention several Aqara devices I have. Seems like custom drivers have been developed for those. I have several cubes, buttons, motion, humidity/temp sensors
- As I understood, all of the integrated devices should just continue to work
Wiz, Shelly, Ring …
- What about smart apps? I know that groovy based are going to die. So RIP Webcore … I use Trend Setter for the moment for grouping my lights and it works just fine. Will it die as well? Is there any replacement? I could see someone mentioning that smart lightning app will continue to work, but I couldn’t even install this in the first place, any other way for the lights grouping?
… and for the very end, how do you even proceed with the Edge drivers? Where do you see which is the current driver used and chose a custom one if wanted? Using Groovy IDE now, but as per my understanding, this will die as well!
Thanks!
All DTH’s, custom or otherwise, will deprecate. For your custom DTH, I would see if whoever wrote it is planning on developing a comparable edge driver. It’s going to depend on the device. Some custom DTHs are used with switches, for example, from mainstream companies. For the most part, they have developed their own Edge drivers as replacements. Those drivers will incorporate the added capabilities not found in the stock Edge drivers.
If an Edge driver is loaded for your device, open the device’s card and click on the 3 dot menu top right. Select the “Driver” menu. A lot of devices have yet to be migrated, so that menu may or may not be present.
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 Zwave 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.
Good luck!
Thanks a lot for all the answers!
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
The fastest Way to find custom edge Drivers is usually to check the quick browse lists in the community – created wiki. 
How to Quick Browse the Community-Created SmartApps Forum Section - Things That Are Smart Wiki
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.
Here is an Edge virtual device creator thread
If they are Groovy based, no.
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?
Some examples:
Monoprice z-wave garage door sensor
Monoprice z-wave door/window sensor
Minoston z-wave smart plug
Aeon siren
GE/JASCO switch
ZOOZ switch
Ecolink z-wave motion sensor
Zooz is creating their own Edge Drivers. Here’s that thread:
[ST EDGE] Zooz Edge Driver Channel
If your device isn’t already there, ask in that thread to see if they have plans to add it.
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.
There are generic fingerprints that should catch the basic devices that aren’t specifically listed:
Bry, thank you so much for this… exactly what I was looking for!
Bill