(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

This bulb (Tradfri LED bulb E27 980 lumen) is WS with 2700 -4000K (NOT CWS)
This bulb the color temperature works with:
1.Zigbee switch stock lates driver
2.Zigbee Light multifunction XY
3.Zigbee Light multifunction XY-1
4.Zigbee Light multifunction Mc

The bulb (TRADFRI bulb E27 CWS opal 600lm)

  • Works with Zigbee switch stock lates driver but has no color temperature
  • Works with Zigbee Light multifunction XY all functions except color temperature not working
  • Works with Zigbee Light multifunction XY-1 all functions except color temperature not working

Ok!
it seems that this bulb is equivalent to an RGB bulb, it has no color temperature attribute
RGBW bulbs has color temperature attribute.
That’s why I needed to see the logs.

You should get white color with the combination of rgb.

Tomorrow I will change it to another profile without color temperature like the stock driver.

Now I’m going to sleep, it’s 1 am here. :sleeping:

name: color-bulb
components:
- id: main
  capabilities:
  - id: switch
    version: 1
  - id: colorControl
    version: 1
  - id: switchLevel
    version: 1
  - id: firmwareUpdate
    version: 1
  - id: refresh
    version: 1
  categories:
  - name: Light

Thanks
Report is below. lets do it tomorrow

Summary

PS C:> CD USERS
PS C:\USERS> CD aminhsm
PS C:\USERS\aminhsm> cd documents
PS C:\USERS\aminhsm\documents> cd CLI
PS C:\USERS\aminhsm\documents\CLI> .\smartthings edge:drivers:logcat
? Enter hub IP address with optionally appended port number: 192.168.1.58
.
.
.
.
.
.
» Warning: The authenticity of 192.168.1.58:9495 can’t be established. Certificate fingerprint is 25:94:6C:32:80:82:4E:70:6E:A6:8C:45:81:64:BF:07:5D:6C:9E:DA
? Are you sure you want to continue connecting? No
connecting… failed
» Error: Hub verification failed.
PS C:\USERS\aminhsm\documents\CLI> .\smartthings edge:drivers:logcat
? Enter hub IP address with optionally appended port number: 192.168.1.58
» Warning: The authenticity of 192.168.1.58:9495 can’t be established. Certificate fingerprint is 25:94:6C:32:80:82:4E:70:6E:A6:8C:45:81:64:BF:07:5D:6C:9E:DA
? Are you sure you want to continue connecting? Yes
» Warning: Permanently added 192.168.1.58:9495 to the list of known hubs.
┌────┬──────────────────────────────────────┬──────────────────────────────────────┐
│ # │ Driver Id │ Name │
├────┼──────────────────────────────────────┼──────────────────────────────────────┤
│ 1 │ c411db9e-a042-459a-a145-f005c65412ee │ ST Zigbee Button Mc │
│ 2 │ 981aab30-6f78-4b31-bf0b-b422bef161ec │ Yeelight.Color │
│ 3 │ 3fb97b6c-f481-441b-a14e-f270d738764e │ Zigbee Button │
│ 4 │ ad9f537d-e2d9-4354-8673-471a5306fad8 │ Zigbee Button Groups │
│ 5 │ 1e45a851-8f07-48d1-bcbf-932fb377e95e │ Zigbee Dimmer Remote │
│ 6 │ ccea734e-e56e-4d2c-a259-3b2e1fdebd82 │ Zigbee Humidity Sensor │
│ 7 │ 6b86005f-95b4-49cb-a3d5-d3a17fd94177 │ Zigbee Light Multifunction Mc │
│ 8 │ d5d863c7-40b8-4425-95f2-71080ba40567 │ Zigbee Light Multifunction XY │
│ 9 │ be1fe1fa-b03d-4551-8ef7-134712386dbd │ Zigbee Light Multifunction XY-1 │
│ 10 │ d620900d-f7bc-4ab5-a171-6dd159872f7d │ Zigbee Motion Sensor │
│ 11 │ 00425c55-0932-416f-a1ba-78fae98ab614 │ Zigbee Motion Sensor Mc │
│ 12 │ cf6324c4-22c0-49e0-a761-fa298b510e58 │ Zigbee Switch │
│ 13 │ 27a1cfbe-1d4f-4be1-b803-2feb3a645e32 │ Zigbee Switch │
│ 14 │ 07e8d581-9c59-4c10-9d06-7e1c75c00f5c │ Zigbee Switch │
│ 15 │ 580a4441-7d16-437e-8cdc-97c03f59e2df │ Zigbee Switch Mc │
│ 16 │ f732925a-9ae3-462a-9641-f03f474c661e │ Zigbee Switch Power Mc │
│ 17 │ 026385b3-dfa9-43e5-b443-cfc42123f042 │ Zigbee Temp Humidity Sensor Mc │
│ 18 │ bd79913f-0309-4256-b669-74c489b81140 │ Zigbee Temp Humidity Sensor Mc-(OLD) │
└────┴──────────────────────────────────────┴──────────────────────────────────────┘
? Select a driver. 8
connecting… connected
2022-04-28T23:07:12.893723631+00:00 DEBUG Zigbee Light Multifunction XY driver device thread event handled
2022-04-28T23:07:12.988755298+00:00 TRACE Zigbee Light Multifunction XY Received event with handler capability
2022-04-28T23:07:13.012896298+00:00 INFO Zigbee Light Multifunction XY <ZigbeeDevice: 8c5573ad-d19d-41a9-8df6-16ea6eb70b9a [0x2902] (IKEA E27 Bulb)> received command: {“args”:{“temperature”:3270},“capability”:“colorTemperature”,“command”:“setColorTemperature”,“component”:“main”,“positional_args”:[3270]}
2022-04-28T23:07:13.019354298+00:00 PRINT Zigbee Light Multifunction XY zll_xy >>>>>> yes
2022-04-28T23:07:13.025879632+00:00 PRINT Zigbee Light Multifunction XY zll_xy >>>>>> yes
2022-04-28T23:07:13.032376965+00:00 TRACE Zigbee Light Multifunction XY Found CapabilityCommandDispatcher handler in zigbee_light_multifunctions
2022-04-28T23:07:13.038442632+00:00 PRINT Zigbee Light Multifunction XY handler_Color Temp >>>>>>>>>>>>>> 3270
2022-04-28T23:07:13.046745632+00:00 INFO Zigbee Light Multifunction XY <ZigbeeDevice: 8c5573ad-d19d-41a9-8df6-16ea6eb70b9a [0x2902] (IKEA E27 Bulb)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x2902, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x04 >, < MoveToLevelWithOnOff || level: 0xFE, transition_time: 0xFFFF, options_mask: 0x00, options_override: 0x00 > > >
2022-04-28T23:07:13.131306632+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:13.149584632+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:13.206578965+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:13.274076632+00:00 TRACE Zigbee Light Multifunction XY Received event with handler zigbee
2022-04-28T23:07:13.363780965+00:00 INFO Zigbee Light Multifunction XY <ZigbeeDevice: 8c5573ad-d19d-41a9-8df6-16ea6eb70b9a [0x2902] (IKEA E27 Bulb)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2902, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0x70, rssi: -72, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5C, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x04, ZclStatus: SUCCESS > > >
2022-04-28T23:07:13.503781298+00:00 PRINT Zigbee Light Multifunction XY zll_xy >>>>>> yes
2022-04-28T23:07:13.559687632+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:13.627367632+00:00 TRACE Zigbee Light Multifunction XY Received event with handler zigbee
2022-04-28T23:07:13.650402632+00:00 INFO Zigbee Light Multifunction XY <ZigbeeDevice: 8c5573ad-d19d-41a9-8df6-16ea6eb70b9a [0x2902] (IKEA E27 Bulb)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2902, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ColorControl >, lqi: 0x70, rssi: -72, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x5D, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x0A, ZclStatus: UNSUP_CLUSTER_COMMAND > > >
2022-04-28T23:07:13.963245632+00:00 PRINT Zigbee Light Multifunction XY zll_xy >>>>>> yes
2022-04-28T23:07:13.976170632+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:14.016277965+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:14.143497299+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:14.150947299+00:00 TRACE Zigbee Light Multifunction XY Received event with handler zigbee
2022-04-28T23:07:14.169846299+00:00 INFO Zigbee Light Multifunction XY <ZigbeeDevice: 8c5573ad-d19d-41a9-8df6-16ea6eb70b9a [0x2902] (IKEA E27 Bulb)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2902, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0x6C, rssi: -73, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x5E, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint8, CurrentLevel: 0xFE > > > >
2022-04-28T23:07:14.214778965+00:00 PRINT Zigbee Light Multifunction XY zll_xy >>>>>> yes
2022-04-28T23:07:14.223522632+00:00 PRINT Zigbee Light Multifunction XY zll_xy >>>>>> yes
2022-04-28T23:07:14.236716632+00:00 TRACE Zigbee Light Multifunction XY Found ZigbeeMessageDispatcher handler in zigbee_light_multifunctions
2022-04-28T23:07:14.243657632+00:00 INFO Zigbee Light Multifunction XY Executing ZclClusterAttributeValueHandler: cluster: Level, attribute: CurrentLevel
2022-04-28T23:07:14.256413299+00:00 INFO Zigbee Light Multifunction XY <ZigbeeDevice: 8c5573ad-d19d-41a9-8df6-16ea6eb70b9a [0x2902] (IKEA E27 Bulb)> emitting event: {“attribute_id”:“level”,“capability_id”:“switchLevel”,“component_id”:“main”,“state”:{“value”:100}}
2022-04-28T23:07:14.300222299+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled
2022-04-28T23:07:14.307316965+00:00 TRACE Zigbee Light Multifunction XY Received event with handler zigbee
2022-04-28T23:07:14.325820299+00:00 INFO Zigbee Light Multifunction XY <ZigbeeDevice: 8c5573ad-d19d-41a9-8df6-16ea6eb70b9a [0x2902] (IKEA E27 Bulb)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2902, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ColorControl >, lqi: 0x6C, rssi: -73, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x5F, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0007, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-04-28T23:07:14.365808299+00:00 PRINT Zigbee Light Multifunction XY zll_xy >>>>>> yes
2022-04-28T23:07:14.371942966+00:00 DEBUG Zigbee Light Multifunction XY IKEA E27 Bulb device thread event handled

1 Like

This log response confirms that this bulb does not support the color temperature attribute.

I’ll fix it tomorrow

@Mariano_Colmenarejo

Thank you very much for your help.
This is what I’ve got so far

Couldn’t make powerMeter to show on the dashboard as stock capability doesn’t have it in presentation.
Any idea how to put 2 capabilities into single group?
Thanks again

1 Like

Published new driver MC version in this thread

Hello @ygerlovin

I’m glad it worked for you!!

You can show up to 5 capability attributes in the same group, but you cannot exceed 5 total capabilities attributes.

This is what I saw based on trial and error since I did not find documentation on this

You could make a custom capability to display text, for example as I did with “infoPanel” on the thermostat.

  • This capability makes a presentation that shows its attribute on the dashboard.
    You do not need show this capability in detailView device presentation, only declare it in the profile and init.lua
{
    "dashboard": {
        "states": [
            {
                "label": "{{infoPanel.value}}"
            }
        ],
        "actions": [],
        "basicPlus": []
    },
    "detailView": [
        {
            "label": "Thermostat Next State Change Information",
            "displayType": "state",
            "state": {
                "label": "{{infoPanel.value}}"
            }
        }
    ],
    "id": "legendabsolute60149.infoPanel",
    "version": 1
  • In the code you define a string that contains the value of PowerMeter and EnergyMeter and that value is emitted in the attribute of the custom capability
     -- emit thermostat information for next change state
     local temp_scale = "C"
     if device.preferences.thermTempUnits == "Fahrenheit" then temp_scale = "F" end
     local text = "No Expected Change in Thermostat State"
     if thermostatOperatingState == "heating" then
      text = "T= "..current_temp.."º"..temp_scale..", Next State: Pending Heat, T > "..string.format("%.2f",tempChangeToPendingHeat).."º"..temp_scale
     elseif thermostatOperatingState == "cooling"  then
      text = "T= "..current_temp.."º"..temp_scale..", Next State: Pending Cool, T < "..string.format("%.2f",tempChangeToPendingCool).."º"..temp_scale
     elseif thermostatOperatingState == "pending heat" then
      text = "T= "..current_temp.."º"..temp_scale..", Next State: Heating, T <= "..string.format("%.2f",tempChangeToHeating).."º"..temp_scale
     elseif thermostatOperatingState == "pending cool" then
      text = "T= "..current_temp.."º"..temp_scale..", Next State: Cooling, T >= "..string.format("%.2f",tempChangeToCooling).."º"..temp_scale
     end 
     device:emit_event(info_Panel.infoPanel(text))
  • In this way you make a device presentation with the custom capability that shows you PowerMeter and EnergyMeter in a single Attribute/group of the 5.

In this case I put in “main” gruop, but you mus put in other secundary group in order to icon control by switch atribute capability

1 Like

@Mariano_Colmenarejo

Thank you so much for your help

I still can’t see the updated driver?

driver updated and works very fine. Thanks

Hi again @Mariano_Colmenarejo
Any chance to fix this issue with new updated library??

@Mariano_Colmenarejo

Hi, somwthing happened to your driver this morning. Zigbee light multifunction MC.

I have 3 GLEDOPTO RGBWW/CW controllers and all are unresponsive now.

Thanks

I had similar problem today. I needed to turn lights on/off from switch and they started to work again.

Nothing has changed in my drivers that could make them stop working.

Something happened in the hubs this morning, someone else complained, but from a different driver.

Seeing the information of the Hub in IDE, it has the date of last update this morning. I don’t know if they have updated.

Hub Last Updated 2022-04-29 8:59 AM UTC

For this other user, with a reboot of the hub, everything was solved.
I did not notice anything strange, I have a smartthings special treatment !!! :crossed_fingers: all my devices works with Edge drivers Mc

1 Like

The problem of auto power off after 2 minutes of tuya switches I don’t think it has anything to do with the libraries.

It seems like a protection from being used on other platforms.

We already tried to write the value that the DTH writes in a specific attribute and it did not work

The device responded as attribute written correctly and I don’t know why it didn’t work.

I can’t think of anything new

Power cycling the controllers fixed mine too.

Thanks for the quick responce and updates!

1 Like

I wanted to add Osram rgbw bulbs but it didn’t pick up any edge drivers.

I installed the new zigbee “thing” and many MC drivers, but it didn’t add it either. still adds it as a goovy handler. I thought the zigbee thing driver suppose to add any make and model zigbee device?

Am I missing something here? Thanks in advance…

If it’s paired with a DTH, go into IDE and send me the manufacturer, model and if it’s RGBW or just color temperature.

Did you install the zigbee thing Mc?

Yes, I installed “thing MC” and most all the other zigbee lighting drivers from your channel. I do appreciate all your hard work.

RGBW

  • manufacturer: OSRAM
  • model: LIGHTIFY A19 RGBW

Color Temp only

  • manufacturer: OSRAM
  • model: LIGHTIFY A19 Tunable White

Thanks!

Sorry, I forgot 2 others. I think this covers most of the Osram bulbs.

RGBW

  • manufacturer: OSRAM
  • model: LIGHTIFY RT RGBW

RGBW

  • manufacturer: OSRAM
  • model: LIGHTIFY BR RGBW

Thanks!