I have modified the egge Driver Zigbee Level Color Temperature Bulb to add progressive "ON and / or OFF in preferences.
Is similar to what Tplink has for its bulbs.
It allows to use the function similar to the gentle wake up app but executed locally.
I have tested it with the Osram Classic bulb. When I have tested it with the Lidl bulb too, I will publish it on the channel.
The preferences are ordered as the app wants, until they fix it
This version is not published on the shared channel. It is in debugging, when it is ready I will publish it on the channel, I do not know if I will have time today, I am a bit busy.
I don’t know whether to publish it as a different driver, another name, you would have to install it in the hub and then install it with the App as a driver change for another in the bulbs you want, similar to how a DTH is changed in the IDE, but in the app, device setings → Driver → Select other driver.
If I publish it as a new version of the previous driver, it will be installed automatically in the bulbs that you already have with the driver.
If someone wants me to add another model of light intensity and / or temperature dimmable zigbee bulb that they want to test, I can add it if you send me the model and manufacturer that appears in IDE.
Action to take when the switch is pressed during dimmer:
Go to End level: Go to “End Level selectected” or 0 for turn Off
Stop dimming: Stop dimming in current level
Off: Go to “Off state” and last level is saved.
This option is the best to use with automations and scenes. If device receive one ON then turn on begins. If receive one OFF then turn OFF without dimming
I will notify here when I publish it on the shared channel
There are many combinations to test, if you see any problem, tell me.
Sorry, the new version is going to be delayed, in the last tests with several bulbs in the same driver it does not work well.
Updating of changes in preference settings is not always communicated immediately and other times it works well, as it happens to others who are using this settings function, such as virtual device creator @TAustin
I will make a version just to include the models asked for @Jake_Mohl and Version info in preferences
Version 2.0 of the edge Driver Zigbee Level Color Temperature Bulb is now finished.
I have tested it with 3 bulbs (1 ea switch & level and 2 ea level & color temperature) working at the same time in ON-OFF dimming mode and it already works fine.
The control so that the lifeCycle infoChanged, which seems to be sent by default in the edge drivers every 1 hour, does not stop the dimming cycle in progress. They only stop if a change is made to the preferences and the dimming is in progress.
I remember that version 2.0 preferences may appear in the app and the edge driver may not yet be updated to the new version.
As it has many possible combinations of ON and OFF, if you see any problem, also send me a screenshot of the preferences settings at that moment so that I can reproduce it. There are times when it seems that it is doing something wrong and that is what we have configured.
@Mariano_Colmenarejo I can report that everything works as intended on Ecosmart bulb.
This seems that can be "Gentle wake up” replacement. I’ll have to test it with automation.
I’ll do testing with Osram bulbs later.
Only issue that is still happening is one that i have previously reported - temperature range, and i know that you are looking into subdrivers.
Just tested with automation, and it works. Bulb goes On and starts at 1% and finished at 50%, as i have created settings.
This settings give me following results:
1st click on ON dimmer starts at 5% and ends at 50%
2nd click on ON button anytime (time to get to 50% is set to 5 minutes) before dimmer riches set maximum level of 50% it goes instantly to 50%, for example dimming is going up and it’s at 22% second click on ON brings light to 50%.
When the light is at maximum setting, and i want to turn it off, pressing OFF button blinks for a second and reports status of OFF, than display button as ON but it keep dimming down to 0% (for 1 minute) until it turns Light OFF, and changes status to OFF.
Seccond click during dimming Down will instantly turn Light OFF.
Double click does not work, it needs about 1 second in between 1st and 2nd click.
I would only change order of settings when that becomes available, and maybe verbage on that last option ”If switch pushed Running GoTo" to your own explanation
This sequence semms runs correctly:
Current state = OFF → click switch → start diiming from 5% to% 0% > click switch during dimmin → go to 50% and dimming stoppped.
Current status ON max dimming → click switch → start dimming to 0% in 1 min → click switch → go to 0% and dimming stopped.
Actions Go To: End, Off, Stop only take efffect when dimming current status is “running” If current status of dimming process is “stopped” then diimming process starts in the direction of the received command turn “On” or "Turn Off ".
For better operation with automations, another option Go To : “Change” could be added, which stops the process in progress and starts the opposite dimming from the current level:
Current status 30% dimming to 50% → clich switch → start diiming from 30% to 0% in programmed off time
Current status 30% dimming to 0% → clich switch → start diiming from 30% to 50% in programmed On time
For tthat his to work, you need the option to go to "Change" and put the Off-End-Level setting back that I removed because it could be the case that if the end level off is not 0% the light will never turn off and it could create confusion, but I see that this is what you want
I understand that if “end level is not 0%” it will never turn off. Someone might like that feature, someone might not. I want to be able to eventually turn off the bulb.
Even now that would be achieved by second press (if switch pushed running goto: end/stop/off, if OFF option is selected), but manually only.
If those 3 settings can be exposed to automations, Progressive ON, Progressive OFF, and If switch pushed running goto, than we could call those actions in automations. My understanding from another developer, who creates Edge drivers for Zooz switches, has some device settings available for Automations, that those actions need to be added to device presentation. I don’t know if how easy or hard this is.
For this, it is necessary to create custom capabilities and in that, for now, I only know that they exist.
I am modifying some things to see if it is worth to you and also to the others.
I’ll tell you when I have
I publish the version 2.1 of the edge Driver Zigbee Level Color Temperature Bulb:
Added “Turn OFF End Level” setting
When “Turn OFF End Level” is > 0, then the bulb can be turned OFF with Off command and bulb current level is = “Turn OFF End Level”.
Added Go To: “Change” option, which reverses the direction of the dimming when switch pushed in dimming process.
This allows a simple automation with a progressive Turn ON with x settings and a progressive Turn OFF with y settings, even if the ON or OFF commands reach the device during the dimming process.
Changed the Minimum dimming time from 0.5 min (30 sec) to 0.1 min (6 sec). With different dimming timer increments for times <=40 sec
In order for the actions to be executed more quickly, the recalculation of dimming variables has been restricted to the installation with preference values and when any preference is changed. Let’s hope the infoChange life cycle improves!
With edge Driver, the infoChanged lifecycle is generated when you click save each changeof a preference value. How code is executed with the change of any value, is recommended when more than one value is changed in preferences:
Change a value, click save and exit
Enter again to change another value.
Allow time between changes if several are going to be done
Hopefully this improves after the beta version.
I tested your particular Porch bulb use with these preferences and automations:
You will tell me!
@Mariano_Colmenarejo thank you for creating such a great driver. I have seen something similar like this previously only for some Osram RGBW Lights, that have firmware with some special capabilities (pulsing, random colors, etc.)
Great job. I think that SmartThings should consider this as official “ZigBee White Color Temperature Bulb” driver. I can see from some samples that you can just keep adding other bulbs’ profiles, and they should work without no problems to some extent.
I am not pushing for features that only I need, I am trying to help you to develop driver that will fit almost everyone, or in another words that will cover almost any Zigbee White temperature bulb.
There are still a couple of quirks to fix.
As I have previously mentioned, Temperature range needs to be fixed, as you said possibly with subdrivers. I can’t find post, but if I remember correctly, @nayelyz said that, that issue can be fixed by specifying in device capabilities. All of mine, and i know that others’ can be different like Lidl, White Temperature bulbs have range from 2700-6500K. Maybe @nayelyz can help with this, as in best interest for all SmartThings users.
This is the same bulb, Old Groovy DTH temperature range in Automations
If you see that you make a change and you do not see that they are applied, even if the value is in preferences, it is because sometimes infoChanged does not send the change.
It can be seen in the logcat with the CLI, which print the old and new value when there is a change and sometimes it does not appear in the logcat.
Just change it back.