From my ignorance of the global operation of the system, but seeing that the end of this new stage, in beta phase, is to have many drivers running locally in the hub, which has limited resources, memory, processor, I don’t know if this type of driver fits into the new structure, especially thinking of users with many devices, I choose to make this type of driver an option and explain:
These drivers are small apps that consume hub resources, memory for variables, processor cycles …, this one in particular needs 18 extra table-type variables more than the normal driver. These tables store 18 values for each device installed in the driver, whether its dimmer functions are used or not. These variables are created when the device is installed and must be deleted when it is uninstalled.
They are special functions that are required for specific devices, 2, 3, I use it only in a light bulb, not for all applicable dimmers in our home. It can also be used for zigbee dimmer switches.
With the so simple tool that the app has to change one driver for another, this type of driver can be installed in just 15 sec in the devices we need and in the rest of the devices use the stock driver that consumes less resources from the hub.
That’s why I doubted whether to publish it as a different driver id than the normal one instead of a version.
That way you can only install it on the bulbs or dimmer you need.
Surely professionals who know the smartthings ecosystem have solutions to standardize this type of dimming functions or perhaps what I say does not make sense and the hub can handle this and much more.
I only try to solve my automation needs and those that other users propose in the community, with the tools that I have at my disposal.
It is what I appreciate the most about the smartthings platform and its community, I can personalize, share, ask, they respond to me and by the way I learn, I have fun and I keep up to date.
I know that for others the automation of their home is a necessity not a hoby