As I said in the previous post, for the bulbs that I know these settings do not work with the standard or TUYA attributes.
Even Lidl bulbs, which are TUYA devices, don’t have that setting in their app.
I don’t know how many bulbs will have this setting and what cluster and attribute they would use.
I was thinking of leaving the setting in the switch-level profile, since there are dimmers in this profile that could work with the attributes and cluster of the switches.
I could also leave it for everyone, even if it doesn’t work or works in some isolated case. It does not prevent the proper functioning of the device and the driver. It only gives a message in the CLI log of an unsupported attribute.
If someone knows the clusters and attributes used by Osram or other brands and wants to share it, I will add it.
(NEW RELEASE) Version 6.0 of the Edge Driver Zigbee Light Multifunction Mc
Changes and Improvements:
At the request and tested by @milandjurovic71, I have added newmodes of Continuous color change, using 2 contiguous colors or with a unique color, blue or green. IMPORTANT NOTE: All color change modes are executed in the driver and are not programmed in the device, therefore continuous use or in more than one device at the same time can condition the operation of the hub and the network, since with the frequency of the chosen timer commands are executed, sent and received continuously.
Added capability for information of the signal metric as in the last Hop. By default in history you don’t see the events. In preferences you can enable visibility if you want to perform a troublesooting of the device signal.
Added preference for ATTEMPT Restore State if Power Lost, using the cluster 0x0006 and the attributes 0x4003 (zigbee standard) and 0x8002 (Tuya). I don’t know of any bulb that works with this, but in the switch-level profile there are dimmers that could work. If I manage to discover or know by someone the clusters and attributes used by some manufacturer I will add it
Added a non-visible capability, Driver Version, which will warn in the event history once a day or when running an InfoChanged lifecycle that a new version of the driver is available that needs to be updated manually. It will be activated only when the driver is renamed (-OLD).
I will be adding this function to the other Mc drivers
As the driver has a new custom capability and changes in preferences the update will not be done automatically.
To facilitate the update, I am going to change driver version 5 to the name Zigbee Light Multifunction Mc-(OLD)
I will publish the new version 6.0 with the original name Zigbee Light Multifunction Mc
In this way, your driver installed will renamed with (OLD), and will be notified in the Event History indicating that there is a new version 6 available and you can install the new version with a driver change whenever you want.
New Driver version:
│ Name │ Zigbee Light Multifunction Mc │
│ Package Key │ Zigbee_Light_Multifunction_v6 │
│ Version │ 2022-06-03T15:03:53.155499333 │
I have tested 3 types of ZigBee bulbs currently or previously available in the US with your new “Restore State if Power Lost” setting. The following are the results:
Ecosmart (Home Depot) bulbs work as expected with your new “restore state if power is lost setting”. Unfortunately for most people these bulb are not currently available. Fortunately for me I bought a bunch for of these for $1.75 each on clearance last summer.
Sengled and Ledvance (Sylvania) bulbs do NOT work with that setting. They still turn on when power is restored regardless of the setting chosen.
So, I will move an Ecosmart bulb into our bedroom lamp and that will solve my problem of the light turning on in the middle of the night after a power flicker.
As aways thanks for your help in solving this problem.
I think this RGBW device uses current x,y attributes instead of hue and saturation like Ikea or Lidl.
I would need to know, if possible, if you are using the DTH Sengled RGBW Bulb.groovy, to add it to the Ikea or LIDL x,y color profile, sengled
Driver Zigbee Light Multifunction Mc Updated the presentations of the Custom Capabilities with the alternative values for the state button and I have changed the displayType:ToggleSwitch for displayType:switch, which seems more appropriate, leaving the power button only for on and off.
The driver version is the same and the presentations will be updated when clearing the cache in android and when reopening the app and each device once or twice and it will show the new switch buttons.