New version of the Zigbee Light Multifunction Mc driver:
At the request of some users, I have modified the behavior of the continuous color change function so that when this function is executed from the virtual control device of a Mirror Group, all the bulbs in the group change to the same color simultaneously in the same mode and with a single Timer, the same that shows the Mirror Group Control device. This greatly reduces the consumption of Hub resources when making color changes in groups of several bulbs since there is only one timer running for the entire group.
In the previous version, each bulb did a different color change sequence and each bulb executed its own timer even if they all timers had the same value.
The changes in this version regarding the Color Change function:
-
When the Color Changing function is activated:
- Previous version: The function was activated and the selected color change sequence began in the bulb or groups of bulbs
- New version: The function is activated, but the color change sequence only begins if the current state of the bulb is “On”. If the status is “Off” the color change sequence will begin when the “On” switch is pressed manually or with a routine or scene.
-
When you deactivate the Color Changing function:
- Previous version and New version: The function is deactivated and if the sequence is running then the color change sequence selected in the bulb or groups of bulbs is stopped
-
If the color change mode or timer is changed on a bulb that is executing the color change as a group, those changes will not be taken into account and the sequence will continue with the values selected in the Mirror Group Control device.
If you want to use the function independently on each bulb, you must first deactivate the function on the mirror group control device.
NOTE: In both the old and new versions and with firmware 51.02, a random error may occur when changing values while the color change function is running, which causes the driver to restart. What the user will see?: the sequence stops and the devices do not respond until the driver resets, about 30 sec, then the sequence continues, perhaps with different values that were not saved during the error.
The problem was reported and the smartthings team replied that they have been able to reproduce it “The error is experienced if a thread socket is unregistered while it is ready to read” and they hope to correct it in the next version of firmware 52.x
New version will be automatically updated in 12 hour max
───────────────────────────────────────────────────
Name Zigbee Light Multifunction Mc
Version 2023-12-16T22:50:50.910095108
───────────────────────────────────────────────────