(EDGE Driver-Mc): Zigbee Light Multifunction Mc

[Mariano_Colmenarejo]

@tmielonen

Using the “progressive” on/off options seems to be more of an emulated effect with noticeable steps up/down in value. Also the minimum of 6 seconds for transitioning is quite a lot longer than what I had with the custom groovy DTH I was using.

I don’t know if I have understood the DTH code correctly, but I think that the main objective of the dth is to smooth the defaults transitions between the on-off state, level and color changes, since the adjustable times for the transitions that can be set between 0 and 10 seconds for each function, on-off, level and color.

The main objective I was looking for making this driver was not to smooth transitions between level or color changes and in fact it cannot.

The progressive on and off was intended to replace the function of the gentle wake up smartapp, in which you choose the initial & end intensity level, and the time it takes to go from the beginning to the end.

I set the minimum time at 6 sec, but it can be lowered.
In the driver, the time between each level change for total transition times less than 42 sec is 0.5 sec.

I have lowered it for a test, to 0.1 sec per step and I can leave it at that value for small transition times, but it does not improve the effect much since the real total times (Hub Process, transmission, reception and execution in device) are greater than 0.1 sec.

The philosophy of DTH seems to change the default transition time or rate argument that is sent in the command and then executed on the bulb itself.

In the default edge libraries it has established default transition or rates times and I cannot find or know how to modify them, sorry

Thanks for your comments!

[tmielonen (Travis Mielonen)]

Thanks for the detailed response!

Yes, I would agree the DTH simply lets you set a device parameter and the actual dimming/smooth cycling for on/off and color/temperature is executed on the bulb(s). At the moment my test bulb with this Edge driver simply turns on/off, or jumps to a dim level/color temp with no smooth transitions. Hopefully, at some point, they enable further arguments to enable the smooth transitions, thanks for looking into it!

[Mariano_Colmenarejo]

Anyway, I’ll look at it to see if I find something in the documentation on how to use the rate argument in the command, I find it interesting.

[sdaltons (Sam)]

Thanks for creating this driver and working to keep it updated!

This is my first time installing it as I somehow managed to overlook the other threads.

Just to be clear: for each zigbee device I’m going to try with the driver, I will first need to remove the device from ST and then reset it in order to link it back to ST using the new driver?

[Mariano_Colmenarejo]

@sdaltons

for each zigbee device I’m going to try with the driver, I will first need to remove the device from ST and then reset it in order to link it back to ST using the new driver?

It’s right.
a single driver can handle multiple devices

[Mariano_Colmenarejo]

(NEW RELEASE) Version 4.0 of the Edge Driver Zigbee Light Multifunction Mc

Improvements and bug fixes:

1. Added new Color Profile Temperature from 2200k to 4000k. At request @JP3000
2. Modified in preferences the setting of Maximum Color Temperature value, since smartthings have fixed those values greater than 999 can be entered.
3. Modified the execution Timer loops for progressive On and Off to achieve smoother changes in times less than 2 minutes.
4. Modified the Random On-Off function so that a device state change is always executed at the end of the random period. Before the on-off state was randomly chosen, this seem confused with the Random Next change time information.
   This modification was also made in the zigbee switch Mc and zigbee Switch Power Mc drivers.
5. Modification that prevents the Random On-Off function stopping if it is active when a hub reboot or driver version update occurs.
6. Added manufacturer impression, model and length of strings in logcat, when running lifecycle Handler infoChanged

As the driver has a new profile and changes in preferences the update will not be done automatically.

To facilitate the update, I am going to change driver version 3.0 to the name Zigbee Light Multifunction Mc-(OLD).
I will publish the new version 4.0 with the original name Zigbee Light Multifunction Mc

In this way, your driver installed will renamed with (OLD), indicating that there is a new version available and you can install the new version with a driver change tool whenever you want

Devices do not need to be uninstalled. Routines, scenes and settings will not be lost

┌─────────────┬──────────────────────────────────────┐
│ Driver Id   │ 1d775bca-be15-4cdd-b942-ce23179c8a92 │
│ Name        │ Zigbee Light Multifunction Mc        │
│ Package Key │ Zigbee_Light_Multifunction_v4        │
│ Version     │ 2021-11-26T15:23:09.492639           │
└─────────────┴──────────────────────────────────────┘

[JP3000]

@Mariano_Colmenarejo

new Color Profile Temperature from 2200k to 4000k

Thank you for adding ’ new Color Profile Temperature from 2200k to 4000k’

The color temperature slider is now from 2200 to 4000k, but if I try to set 2200k the app thinks about it for couple of seconds, then throws Network Error or sets it to 2202k. Also setting to 4000k is bit random, it either accepts it or give network error and sets it to 3984. I have not looked the logs yet to see if there is any errors there.

Adding any routine to control the lights the color temperature can be set between 1k and 30 000k. Where does this come from? Has anyone else noticed this when creating routines to control color temperature light bulbs?

[Mariano_Colmenarejo]

@JP3000

The color temperature slider is now from 2200 to 4000k, but if I try to set 2200k the app thinks about it for couple of seconds, then throws Network Error or sets it to 2202k. Also setting to 4000k is bit random, it either accepts it or give network error and sets it to 3984. I have not looked the logs yet to see if there is any errors there.

Adding any routine to control the lights the color temperature can be set between 1k and 30 000k. Where does this come from? Has anyone else noticed this when creating routines to control color temperature light bulbs?

The error of setting a color temperature value and showing another, in some values, is due to an error in the lua edge libraries when converting the ºk units to mireds and vice versa.

@Mariano_Colmenarejo

local temp_in_mired = math.floor(1000000 / command.args.temperature)

Here is the error we saw between the selected color temperature and the one received from the device with the default libraries:
In this example:

2021-10-13T21:58:47.793566999+00:00 PRINT Zigbee Level ColorTemp Bulb v3.5  Last Color Temperature =    4219    table: 0x1e3a220
2021-10-13T21:58:47.801812666+00:00 PRINT Zigbee Level ColorTemp Bulb v3.5  colorTemp   4019
2021-10-13T21:58:47.810869666+00:00 PRINT Zigbee Level ColorTemp Bulb v3.5  colorTemp Mired     248
2021-10-13T21:58:48.089938333+00:00 INFO Zigbee Level ColorTemp Bulb v3.5  <ZigbeeDevice: 9e628be9-f0bc-4839-9072-2b691d3e914e [0x75F2] (Lidl Bulb)> 
emitting event: {"state":{"value":4032},"attribute_id":"colorTemperature","component_id":"main","capability_id":"colorTemperature"}

Value to send 4019 k
converted to mireds without rounding 248.8181139586962
converted with math.floor = 248

Converted to K = 4.032.258064516129 k
Rounded with math.floor = 4032 k shown in app

The conditions view → actions, does not replace the stock presentation and does not present the custom presentation. It is also a known error. It affects other capacities as well, temperature, thermostat setpoints

These two errors are already reported to @nayelyz and they will solve them over time, I don’t know what order of priority they will have.

[nayelyz (OOO - Please contact @AlejandroPadilla or @Ivan_Luis_Falleau)]

@Mariano_Colmenarejo

These two errors are already reported to @nayelyz and they will solve them over time

Actually, the engineering team mentioned this will be solved by the 0.41 firmware version but there’s no ETA yet for its release.

[Mariano_Colmenarejo]

@tmielonen

If there’s anything I can provide to give more insight, I’d love to help and get the smooth effect back. For reference here is the thread and Groovy DTH I was/am using - [UPDATED] Osram Lightify RGBW A19/BR30 US version (HA) DTH

@Mariano_Colmenarejo

The philosophy of DTH seems to change the default transition time or rate argument that is sent in the command and then executed on the bulb itself.

@Mariano_Colmenarejo

Anyway, I’ll look at it to see if I find something in the documentation on how to use the rate argument in the command, I find it interesting.

Hi @tmielonen,

I haven’t found much information on how to use the “transition_time” argument in MoveTo commands (level, color, colortemperature)

I have made a TEST version of the driver Zigbee Light Multifunction and Tr-Time that sends the argument “transition_time” in the commands sent to the device to turn on, turn off, color level changes and color temperature.

This does not work on all bulbs.

The DTH you gave me as a reference is only for the Osram A19/BR30, which is not in the driver’s list, I don’t know which bulb you tried it with.

In Preferences there are settings to choose between 0 and 10 sec the transition time from off-on-off, color level and color temperature changes. These values ​​have been adjusted by looking at the logcat, since I have not found how to correctly scale the seconds to the transition_time value. I have multiplied by 4 the seconds, that I found in a chat for hue bulbs and it seems the most approximate in the tests that I have been able to tets with my bulbs.

I have only been able to test it on an Osram classic ZLL bulb, switch-level and it works well and on a Lidl switch-level-Color temperature zigbee 3.0 and it works, but in a different way than the Osram classic. It does not meet the established times the same or does not meet them directly for color temperature.

I don’t have rgb or rgbw zigbee bulbs to test, @milandjurovic71 tried it and some seem to work and others don’t work at all well, if not bad.

What is seen in the app is slower than what the light bulb does, the information comes to the app from the cloud and there are several events and very fast changes in a few seconds.

To install it in a bulb that already uses an edge driver, all you have to do is change the driver. Clearing cache memory could be good, as it has new preferences.
If it malfunctions, which may malfunction, switch back to the driver that worked well.

In a bulb that is using DTH, you have to install the driver in the hub, uninstall the bulb, and install the bulb by searching nearby. If you are using the custom DTH you may have to delete it or disable the fingerprint lines.

│ Name │ Zigbee Light Multifunction and Tr-Time
│ Version │ 2021-12-03T16:37:26.203627

You will tell me how it works for you

[Mariano_Colmenarejo]

@Mariano_Colmenarejo

@tmielonen

If there’s anything I can provide to give more insight, I’d love to help and get the smooth effect back. For reference here is the thread and Groovy DTH I was/am using - [UPDATED] Osram Lightify RGBW A19/BR30 US version (HA) DTH

@tmielonen,

You tried this driver that I made for you, with time and transition settings for on, off, level, color and color temperature.

It works well for me on the Osram classic bulb with dimmer.

Zigbee Light Multifunction and Tr-Time

[tmielonen (Travis Mielonen)]

Hey @Mariano_Colmenarejo,

Sorry, I haven’t had time yet (silly I know it takes about 5 mins) hopefully this week though as Christmas break will start soon.

Cheers,

[Mariano_Colmenarejo]

(NEW RELEASE) Version 4.5 of the Edge Driver Zigbee Light Multifunction Mc

Improvements:
At the request of @niquini, for the GLEDOPTO, model GL-C-008S

1. Added new Color Profile Temperature from 2000k to 6500k for RGBW

2. Modified in preferences the setting Change Profile for Color Temperature 2000k to 6500k or 2700k to 6500k. Default profile is 2700k to 6500k

As the Color Temperature in the RGBW devices for Led strips, depends of the strip type that we connect to the device, the change of profile can be chosen in Preferences.
For the profile change to take effect in the details view, you have to close the App and clear the Cache of the App after change Color Temperature Profile.

As the driver has a new profile and changes in preferences the update will not be done automatically.
To facilitate the update, I am going to change driver version 4.0 to the name Zigbee Light Multifunction Mc-(OLD).
I will publish the new version 4.5 with the original name Zigbee Light Multifunction Mc
In this way, your driver installed will renamed with (OLD), indicating that there is a new version available and you can install the new version with a driver change whenever you want.

[Sylvain]

@Mariano_Colmenarejo

For the profile change to take effect in the details view, you have to close the App and clear the Cache of the App after change Color Temperature Profile.

Hi @Mariano_Colmenarejo
What i do is move my device to another room and the change will take place.

[niquini (Wanderson Niquini)]

Very good. Tomorrow when I get home I will test it. Thank you so much again

[niquini (Wanderson Niquini)]

Hello my friend, how are you?

I’m still having problems with the driver for gledopto lamps. It keeps looping when I change the dimmer or color temperature.

Other times when I open it, a cloud appears

[milandjurovic71 (Milan)]

Reboot your hub, clear app cache, and restart the app. It should be fine after

[niquini (Wanderson Niquini)]

I’ve already tried this and it didn’t work for me (I use ios)

[Mariano_Colmenarejo]

@niquini

I’ve already tried this and it didn’t work for me (I use ios)

Hi Niquini,

It is a symptom that something has not been installed correctly and is usually fixed with the reboot of the hub.
You can switch to the driver - (OLD), close the device and reopen it. Allow more than 1 minute to finish the installation, it is a driver with several custom capabilities and profiles and it takes longer than it seems in the app.

-Erase the new driver from your Hub in app.
-Re-install the driver in the Hub from the channel and wait a minute
-Open the device and make a change from Driver to the new one.
-Close the device in the app, reopen it and wait about a minute for the installation and configuration to be carried out.
-Perform a refresh, sliding your finger down

It should work

[niquini (Wanderson Niquini)]

I did the procedure 2 times, I restarted the hub and the same error remains.