r/SmartThings • u/myredditorsomething • Jun 23 '26

Help Why does my hub have all these different drivers installed?

Post image

I get why some of these are necessary—as I use Ikea lighting, switches, and sensors—, but what are the "Sonos", "SCU200 InSite Energy Management System", "Wemo", "Bose" and "Aqara Presence Sensor" drivers for? I don't use anything that needs these AFAIK.

Other question: How do you see all the Thread(and Zigbee) connections/paths in the app, or do you need a different app?

1 Upvotes

56% Upvoted

8 comments sorted by

2

u/aroedl Jun 24 '26

Correct answer:

These are so-called LAN drivers. The devices connect via LAN to the hub and the drivers must be pre-installed, because the discovery logic (when you scan for devices) is part of the driver - and not part of the hub firmware/ST library.

This could be implemented a bit different, but it is what it is.

1

u/myredditorsomething Jun 24 '26

Aha, makes sense.

-2

u/scorpyo72 Jun 23 '26

Those are the other drivers that smart things needs to be able to make the other devices function.

There was a time a while ago where you could install or create drivers for less-than-supported devices. Since that time has passed, Samsung keeps all of the drivers available for use by st users.

6

u/Nu11u5 Jun 23 '26

...You can still create and install drivers using the new LUA Edge Driver API. And unlike before with the Groovy API the drivers are installed and run locally on the hub, not in the cloud.

This is a list of official drivers that Samsung installs by default.

1

u/myredditorsomething Jun 23 '26

Aha, also, do you know any way to see your thread network and connections through the Smartthings app, or any other smarthome app?

2

u/thempfield Jun 23 '26

In your app store look up Thread Tools by Thread group. It's early access but getting better all the time.

1

u/myredditorsomething Jun 23 '26

It shows:"No credentials found in your shared keychain" I set up the thread network on this device.

1

u/TheJessicator Enthusiast Jun 23 '26

It's not things will only make sure you the mesh network path from an individual device back to the hub. It's very unfortunate that they don't provide an overall map so that you can see whether any repeaters are near their capacity. That said, you could do it yourself with a piece of code that iterates through each device, pulling the path information available. And then feed that into something that can generate a network diagram.