Hi All,
I’ve recently tried to add a new Frient device which needs edge drivers. I’ve been able to select different drivers in the past but now for all devices when I try to select a different driver I get “No results found”. This is the same for all devices I’ve noticed if I attempt choose select different driver.
The correct drivers are enrolled/installed and show up in the my.smartthings web console.
I’ve tired unenrolling and re-enrolling the drivers. Rebooted the hub numerous times, reset the app, reinstalled the app, signed in and out of the app, removed and re-added the device multiple times.
I also cannot select any other driver in the web interface for any device.
Anyone come across this before? Frient have done some testing and the device behaves as expected their end so suspect an issue with the Hub/account.
It is possible that the new device has a slightly different “fingerprint“ then the previous one you used.
Under the SmartThings Edge architecture, The fingerprint that the device transmits must be exactly the same as the fingerprint in the driver or the driver will not be listed as an option.
You can use the official Web interface to your SmartThings account to check and see what the fingerprint is and if it’s the same as another device of the same model on your account.
Hey thanks for the reply.
I’ve got other Frient devices and the edge drivers all load correctly. The fingerprint is unique for the motion sensor.
The motion sensor identifies as “base-illuminance” which may be why it’s not picking up the motion driver and loading the default zigbee illuminance driver.
I tried forcing it to use the motion driver via CLI but it errored.
I went through some of my devices and I found out that I can’t switch the drivers either. Shouldn’t I be able to switch between the stock and the beta edge drivers?
My Frient smoke detectors should have a fingerprint in the stock driver? I think I have to dig a bit deeper.
Not via the ‘switch driver’ mechanism as the hub can only have one version of a driver installed and the beta and production drivers are different versions of the same driver.
There doesn’t seem to be a documented way for end users to install drivers from the production default channel on demand. I can’t remember if there is an undocumented way.
