@nayelyz, sorry if you are the wrong person, but i see that you are very active in the forum about development subjects and maybe you can take this request to the development team.
One thing that annoys me a lot is the incapability of manual installing drivers from the smartthings official/GA channel.
One situation that this cause a lot of headache is when you already have a custom edge driver installed, and a bunch of devices that use that custom driver, then you want to install and use the official driver for a existing device
or a new device that has its fingerprint in the custom driver, but the official driver is not yet installed.
For example: i have some aqara’s open/close sensors that use “zigbee contact mc” driver. The official “Zigbee contact” driver is not installed in my hub. Now i want to install some smarthings multipurpose sensors and use the oficial smartthings driver for them but, As their fingerprint is included in the custom driver, the official driver is never installed.
There are no way to install the driver from the official channel in this case without remove all the devices that uses the custom driver to uninstall the custom driver itself, install the new device with the official driver and them reinstall the other devices and the custom driver again.
Imagine this with a considerable number of devices and routines already set and you have a huge NO GO!
For me, we need some way to choose the driver that we want to use when adding devices if there are fingerprint match in multiple drivers.
The difference between Beta and Production/Default channels is that the first one gets driver updates before the second one, but both get the same config in the end.
I’ll see if we can put this link in the documentation so you can access it more easily.
thanks @nayelyz! One problem solved!
But, just to extrapolate a little bit about the option to choose the driver when adding new devices.
Edge driver developers aways suggest to “uninstall the device and pair it again with the custom driver, do not perform a driver change”, i think this is related with init/config routines that are not performed when changing drivers that can lead to erratic behavior.
But, if we have multiple fingerprint matchs, chances are that the device will be added with the “wrong” driver, forcing us to do a driver change.
@marcos.scheffler
I shared your concerns with the engineering team and created a ticket about this to see what the team can do to improve this.
For now, it’s suggested that you install only the necessary drivers for your devices and avoid having many that match a single fingerprint.
When at least one device is paired to a driver, it will be active, and consume memory. So, avoid having several drivers that support several devices to install one device for example, this will help save memory in the Hub.
Just following up, and for others reference, we requested the addition of the default/production channel in the documentation and now you can find it in the Tip section here:
