I think I found another bug, and I’m curious to know if anyone else experienced such behavior.
My observation is that when I install a custom EDGE driver from the channel invitation, and right after that I add the device that the driver is for, my hub will still add the device using a generic driver instead.
Of course, later I can change the driver to use in settings, but here’s another problem - with some devices, it won’t work, as they’ve already been configured using the wrong, generic driver.
Restarting the hub doesn’t help, however adding the device again after around an hour since the new driver has been installed - the hub correctly picks up the desired driver.
Unfortunately, I don’t see a place where I could somehow tell ST which drivers to prioritize (neither in the app nor in advanced web UI).
This is a silly observation but it can be really frustrating.
Has anyone else noticed it or is it something with my hardware?
I already tried factory resetting the hub and going through the entire process from the beginning.
I’ve noticed related behaviours messing with drivers while learning how to develop one, there must be a cache of drivers that sometimes take a few minutes to catch up.
Custom drivers are supposed to always have priority, but it sounds like you might just not be waiting long enough for the custom edge driver to be downloaded to your hub.
Are you verifying that the custom driver is on your hub before adding the device? Although it usually happens within a few minutes, there have been some reports of it taking longer in some cases.
Yeah. I did a test during which I was deleting and adding a single device numerous times before SmartThings finally used a custom driver when initiating the device.
It actually took more than two hours this time.
No clue if my old hub just had enough, or if it’s something new, however, it hasn’t been like that before, definitely.
In your tests, did you only install the driver from the invitation link or the CLI as well (I mean using the code to upload it directly to your hub)
By “generic driver”, do you mean it’s connected as Zigbee or Z-Wave thing? If not, which driver was getting matched to the device?
This is important because the Zigbee and Z-Wave generic fingerprints are in the last step of the fingerprint match logic which means that your device couldn’t match any of the generic fingerprints that use its supported Clusters (Zibgee) or Command-Classes (Z-Wave) as a reference to match the device.
Could you help us replicate the issue and share the following info to include in the report, please?
Provide the Hub logs (after replicating the issue) by following these steps:
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
In your tests, did you only install the driver from the invitation link or the CLI as well (I mean using the code to upload it directly to your hub)
I installed the driver from the invitation link, however, I used CLI to create this invitation link, and channel, and to upload the driver.
By “generic driver”, do you mean it’s connected as Zigbee or Z-Wave thing? If not, which driver was getting matched to the device? This is important because the Zigbee and Z-Wave generic fingerprints are in the last step of the fingerprint match logic which means that your device couldn’t match any of the generic fingerprints that use its supported Clusters (Zibgee) or Command-Classes (Z-Wave) as a reference to match the device.
I mean the “Zigbee Switch” driver. The custom driver, however, also has a “Switch” profile.
Could you help us replicate the issue and share the following info to include in the report, please?
Yes, I can do that later today, or during the weekend. I would appreciate it if I could reach out to you via e-mail - I can also provide you with the custom driver code - I think it’s worth mentioning that it also happens with other drivers from different channels, so the issue is not limited to a single driver.
FYI, the account is different than the one here on the forum.