With Functions for optional:
- Random-ON & OFF
- Change Profile Icon
Zigbee Contact Mc: Link to devices supported fingerprints.yml
With settings for temperature Reports
With settings for X,Y, Z axis for Garage Door
With settings for Accel threshold
Zigbee Motion Sensor Mc: Link Devices Supported fingerprints.yml
With settings for temperature Reports
SmartThings Zegbee Button Mc:
With settings for temperature Reports
Zigbee Temp Sensor and Child Thermostat Mc
With optional child virtual complete thermostat
For sensors with capability of measuring atmospheric pressure, a Custom Capability is added to display the information in mBar.
In preferences has the options to configure the intervals and precision of the temperature, humidity, illuminance reports, for the sensors that use the default zigbee configuration.
Link to supported devices fingerprints.yml
@Mariano_Colmenarejo Ok, will monitor. I’ll try to re-add Silvanya/Osram bulbs later.
Happy to report that both bulbs work, without any issues. I was able also to add Automation with Zooz Double Switch running on Edge driver, written by @krlaframboise, and as expected it runs Local.
@nayelyz Only issues with bulbs (or probably ST App), initially they were not reporting change status, if i tried to turn them off or change color temperature and dimm - icon was just spinning. After Shutting down ST and clearing cache, everything works normal.
@Mariano_Colmenarejo I have found one issue that is not making bulbs non functional, but device details gets stuck for some time (10-20 seconds). It’s related with Temperature range - bulb capability, that will be different with different models.
Your device allow temperature range from 2000K to 6500K, and Ecismart bulbs are capable of 2700K to 6500K. If move slider below 2700K, it gets stuck for some time. If i hit predefined temperature button for lowest Temperature, in this case some how selects 2450K, it gets stuck for some time. See bellow
This is probably chosen by app, by percentage of driver. If you can somehow query Temperature capabilities of light bulbs or have settings that will alow to set range, that would solve this issue.
Bulbs always go to minimum range, hiwever thise preset buttons are not all useful.
This driver is made with the default libraries according to the capabilities supported by the device.
It does not take into account the operating values of each manufacturer.
If the device is outside the default values, the driver must be customized for that manufacturer, as is done for DTHs.
Sorry, I do not feel qualified to do that now.
Surely when smartthings converts stock DTHs to edge drive it will work fine.
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.
New Version for Zigbee Level ColorTemp Bulb driver finished. I am ending testing it, and will publish it tomorrow if everything goes well:
Bear in mind that the update of the versions is slow, up to 12 hours. As @TAustin said, you may see the new version in your App preferences and it is not yet updated and operational
Added in Settings Preferences::
(Until smartthings fix it, they are shown in random order)
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.
Update 1:
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.
Good work.
Just tested with automation, and it works. Bulb goes On and starts at 1% and finished at 50%, as i have created settings.