anything listed in the Driver section is Edge drivers
API browser+ is a good way to identify which devices are using legacy DTH or Edge. Anything that shows DTH is only legacy groovy DTH. All devices that do not display DTH are Edge or the new architecture.
Okay, thanks. I don’t see any devices that say DTH.
I think this will be my stopping point for tonight. Tomorrow, I’ll go through my devices and do an inventory of which devices are using which drivers and then go through and see which drivers I can remove.
Okay, I know I said I was done for the night, but I did one more thing, I clicked through all the devices and:
Devices listed as GE, I switched the switched the driver
I found there were actually a few devices where type was “DTH,” so tomorrow I will force remove those and re-add them (many of them are offline, which was a problem I was going to tackle after the lag, but I’m guessing that’s the problem now)
In the API Browser+, go to Locations->Hubs-> Installed Drivers. This will show you all the drivers installed to your hub. Then highlight a driver and click on List Devices. This will show you all devices, if any, that are utilizing that driver.
Devices-> Drivers is a list of any drivers you have created.
In addition to Z-Wave and Zigbee Edge drivers, there are LAN Edge drivers for devices like Sonos and that have been used to create virtual devices that run on your hub instead of the cloud. There are also Matter Edge drivers that support both Wi-Fi and Thread devices. Cloud to Cloud device integrations are identified as Viper devices. Samsung appliances and TVs are OCF devices.
The filter feature in the Devices list is a quick way to see how many devices of the various types you have in your ST setup.
Okay, so a huge thank you for your help so far. I’ve cleared up unused devices, deleted some old virtual switches that I forgot were, in fact virtual, restarted my hub, ran the Zwave repair (with a few error messages, screenshot below), cleared up old routines and now every device listed in ST is online.
However, I’m still getting the same lag. After more clicking, I found the filter in the API to see my 19 DTH devices. A few of them are switches that I’m not sure if they’re GE or not, so later I’ll remove the switch plate to check the brand. But many or random sensors and scene controllers. I tried to “Change Driver,” but I get a message that it’s an “Ineligible Device.”
Is my best approach here to one-by-one remove those devices and re-add them?
Are all devices experiencing the lag including both Edge driver devices and DTH devices?
Either from the API Browser+ or the legacy IDE, you should be able to see the fingerprint of the devices using DTHs and we can probably figure out what they are without you having to physically inspect them. Even if you don’t know what manufacturer they are, if you remove and re-add them to your network, they should pick up a stock ST Edge driver, barring any custom DTHs installed in the legacy IDE.
You can only use the Change Driver function in the API Browser+ once a device is on an Edge driver. To convert from a DTH to Edge, you have exclude the device from your network, delete any custom DTHs from the IDE if present for that device, and then re-install the device. The only other way is to wait for ST to migrate them at some point in time.
Unknown device during the Z-Wave repair seems troublesome to me. The app doesn’t give you a lot of info, but I think the hub log in the legacy IDE may show you more info such as Z-Wave network ID that could help you track down what devices are the issue.
Just an update to let everyone know where I’m at…the short version is - apparently the state of my Smart Home is a mess!
I started with 18 DTH devices, I’ve been going through and removing/re-adding them one by one. In doing so, I also discovered that two of the switches aren’t working and the Lighting Automation SmartApp I was using was deprecated alongside Groovy.
I’ve still got another 7 devices to go through and then an Amazon order to replace old stuff. Everything is running slow still, but many of the devices I’ve re-added are giving a message that “all the statuses haven’t updated, check back later,” so I’m assuming it’s like updating all your apps on a factory reset phone and my poor hub is struggling to keep up with all the updates.
Thanks to everyone who has helped guide my way. I guess now it’s time to research Matter switches so I can start the transition with the stuff that needs to be replaced.
It was the “Lighting Automation” Smart App. I moved it all to routines.
I got everything moved, ran Zwave Repair and restarted my hub, but the lag isn’t better. I still had fewer, but a few Unknowns on the Zwave repair, and now I have devices randomly going offline - it’s not a constant online/offline thing, but it just seems every hour or two some of the devices come online and a different two or three go offline.
So if there’s any guidance on the next step of troubleshooting, I’d appreciate it.
I’m officially off DTH drivers, so they are all on Edge. It looked like a lot of the ones I removed a re-added, but they all seem to be up and running now, except for a lone door sensor that’s the old SmartThings PGC313 Multi Sensor. The batteries were dead at the start of this escapade, but I did replace the batteries, removed the device and re-added it. It was connected for a while, but now it’s offline.
That is the mobile app attempting to tell you that the devices have null values for one or more attributes. It has never been clear why it can’t just work with the ones it does have instead of getting its knickers in a twist.
Conventionally integrations create synthetic events to initialise the attributes but I noticed that these were temporarily disabled in stock Edge drivers last year. I presumed they confused the issue when migrating devices with the trade off being confusing the issue when installing devices instead. Why the app can’t just say which attributes it is waiting for is another mystery, as then you might be able to help it out by ‘playing’ with the devices.
A couple of other things to check using API Browser+:
Check the fingerprints of all your Z-Wave devices to be sure they registered properly and that you don’t have any with all zeroes
If you have Z-Wave Plus devices, did S2 security properly authenticate or does it show failed? Edge architecture is more finicky about S2 security
Check that the Provisioning State is Provisioned
After all that, it might be time to start doing some driver logging to get a sense of how commands are being processed and received. That is done with the ST CLI tool from a Linux/Windows/Mac computer. We can go further into that later if necessary.
Did you add Plus devices via QR code or Search Nearby? If you did Search Nearby and didn’t provide the DSK, it would fail. Not saying this is the problem, but trying to eliminate as many variables as possible.
All that device info is in the Details for a device. Forgot fingerprints isn’t the term anymore. It’s Mfg Code.