Why SmartThings has Installed Unnecessary Wemo etc Drivers to my Hubs

Developer Programs Support
21

@nayelyz
Something that I find odd is that if you retrieve the meta info for the Wemo driver in the production default channel you get the fingerprint of a generic Matter lock listed. What’s that doing there? It doesn’t show in the beta channel.

/distchannels/15ea8adc-8be7-4ea6-8b51-4155f56dc6cf/drivers/d9c3f8b8-c3c3-4b77-9ddd-01d08102c84b/meta

The generic fingerprint uses a deviceIntegrationProfile ID that is also in the driver meta info in the default channel but not in the beta channel. It makes no sense to me but it also raises concerns.

{
    "driverId": "d9c3f8b8-c3c3-4b77-9ddd-01d08102c84b",
    "name": "Wemo",
    "packageKey": "com.smartthings.wemo",
    "deviceIntegrationProfiles": [
        {
            "id": "2636d0a3-e2f5-38a9-b4ed-26a22b42a054",
            "majorVersion": 0
        },
        {
            "id": "48473b6b-8a56-3328-a41a-3cf4138b3dd4",
            "majorVersion": 3
        },
        {
            "id": "766c8c25-82ae-33aa-b749-701d52bf1f14",
            "majorVersion": 3
        },
        {
            "id": "7df3bbcd-4be0-361a-b0dd-160ecfd0ace9",
            "majorVersion": 3
        },
        {
            "id": "9884644f-fca9-36eb-a603-9ad22ede97e6",
            "majorVersion": 3
        },
        {
            "id": "c6b0c514-5e47-3811-a0f0-d3e0e5ebb964",
            "majorVersion": 0
        },
        {
            "id": "d0122a79-37ad-33d1-99f4-ee61d5afdf2f",
            "majorVersion": 3
        },
        {
            "id": "d5f4eebf-9ba2-3280-bfaa-a5edf5963999",
            "majorVersion": 0
        }
    ],
    "permissions": [
        {
            "name": "lan",
            "attributes": {}
        },
        {
            "name": "discovery",
            "attributes": {}
        }
    ],
    "version": "2023-05-16T19:19:44.857775629",
    "fingerprints": [
        {
            "id": "matter/door-lock",
            "type": "MATTER_GENERIC",
            "deviceLabel": "Matter Door Lock",
            "matterGeneric": {
                "deviceTypes": [
                    {
                        "deviceTypeId": 10
                    }
                ],
                "deviceIntegrationProfileKey": {
                    "id": "2636d0a3-e2f5-38a9-b4ed-26a22b42a054",
                    "majorVersion": 0
                }
            }
        }
    ]
}
2 Likes
22

I note that Steven has already redeployed the Wemo driver and by the looks of it has identified the root cause and fixed that too.

23

Yes, we shared your comment with them, so, they were checking further details about this and other LAN drivers, but this seemed to be the only one affected.

1 Like
24

Great thanks. That’s rather made my day. It doesn’t take a lot.

25

Bose showed up today, and is alos something my configuration does not have. So I now have 9 drivers. One I enrolled in that is supporting two devices (with 3 more likely to come), 3 that serve no logical purpose for my configuration, and 5 that support the 25% or so devices that have moved over.

26

The driver for Philips Hue has always been there? Noticed it today, but don’t remember ever installing it.

1 Like
27

Some users reported that Hue is in the process of being migrated so if you have hue, it is possible it has been migrated. open the hue hub, tap on three dots and if you see Driver… then it has.

1 Like
28

I’ve just looked and I have it on a couple of hubs. It wasn’t there when I checked from a dump I took a week ago but it is there on one from yesterday. I presume it appeared following Tuesday’s rolling up of beta to production.

That’s now four LAN drivers for things I don’t have. I hope at some stage there will be a way to disable them.

4 Likes
29

Yes, that’s right, the hub now has this driver.

But I didn’t need it to be migrated, as I’ve never had anything Groovy!

30

Philips Hue driver has been installed in both of my hubs.
I do not use and have never used Philips Hue devices.

31

I understand it’s expected that these LAN drivers are installed on the hub but do they count toward the total number of drivers installed? I know once you reach a certain number of installed drivers it can cause hub reboots and other issues.

2 Likes
32

I think the limited memory is the biggest concern, and I was wondering the same thing if we could remove them…

2 Likes
33

Today has been installed a new driver Sonos

34

I know it has been a while. Is there any resolution to these phantom drivers?

I have two hubs in order to handle the memory load of the new drivers and I keep seeing warnings when I go to scan for a new device. I have deleted all these unused drivers but they keep being re-installed on their own. This is frustrating that the memory limitation is bad enough but then you keep filling up my hub with useless drivers.

1 Like
35

No

As you don’t have devices using drivers, drivers won’t be running on your Hub.

36

no but they are taking up space.

martin

37

The hub’s RAM memory is the limiting factor for the number of drivers.
These additional drivers only consume Flash memory if they are not in use.

This is covered in another thread, but I can’t remember where.

3 Likes
38

thanks for clearing that up
martin

2 Likes