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

Still paring are ZLL Dimmer.

I already mentioned to the engineering team that you’re still having issues. I’ll let you know in case I receive more feedback from them.

1 Like

@nayelyz
If I create a generic fingerprint, same as the DTH one?

That could work, take a look at the sample I shared here:

Thanks, @Mariano_Colmenarejo!

@Paul_Oliver,
Try now.
I have put a generic zigbee dimmer with your clusters, Zigbee Level ColorTemp Bulb v3.9

zigbeeGeneric:
  - id: "dimmer-generic"
    deviceLabel: "Zigbee Dimmer"
    zigbeeProfiles: 
      - 0xC05E
    deviceIdentifiers: 
      - 0x0100
    clusters: 
      server: 
        - 0x0006
        - 0x0008
      client:
        - 0x0019
    deviceProfileName: switch-level

If it matches, once it works try to make a driver change to the Zigbee Level ColorTemp Bulb Mc and if it works we delete this so that it does not give problems to other users

IT WORKED!!!
But I can not change it to the driver to “Zigbee Level ColorTemp Bulb Mc”. When I chose “Select different driver” it says “No Results Found” @nayelyz

Thanks

Non-matching Fingerprint?

Also" I can turn the bulb on and off, but I can NOT use the dimmer. When I use the dimmer is spins and spins and I get a error message “A network or server error occurred. Try again later.”

It is 2700-6500, Thank you

@Mariano_Colmenarejo The following are the logs from turning the bulb on and trying to adjust the brightness twice:

? Select a driver. 9
2021-10-21T05:17:10.670310855+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee health poll
2021-10-21T05:17:23.446488856+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler capability
2021-10-21T05:17:23.452068148+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received command: {“args”:,“command”:“on”,“capability”:“switch”,“positional_args”:,“component”:“main”}
2021-10-21T05:17:23.455549981+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Found CapabilityCommandDispatcher handler in Zigbee_Level_ColorTemperature_Bulb
2021-10-21T05:17:23.459704856+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x72A8, dest_endpoint: 0x0A, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2021-10-21T05:17:23.476582731+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> emitting event: {“component_id”:“main”,“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“on”}}
2021-10-21T05:17:23.490808648+00:00 PRINT Zigbee Level ColorTemp Bulb v3.9 circadian_Running ; circadian[device] table: 0x1242d08 Inactive
2021-10-21T05:17:23.496762064+00:00 DEBUG Zigbee Level ColorTemp Bulb v3.9 Zigbee Dimmer device thread event handled
2021-10-21T05:17:23.549293689+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee
2021-10-21T05:17:23.554023439+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x72A8, src_endpoint: 0x0A, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -60, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4E, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2021-10-21T05:17:23.563534689+00:00 DEBUG Zigbee Level ColorTemp Bulb v3.9 Zigbee Dimmer device thread event handled
2021-10-21T05:17:40.680058525+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee health poll
2021-10-21T05:18:00.080519985+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler capability
2021-10-21T05:18:00.086400319+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received command: {“args”:{“level”:10},“command”:“setLevel”,“capability”:“switchLevel”,“positional_args”:[10],“component”:“main”}
2021-10-21T05:18:00.089870319+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Found CapabilityCommandDispatcher handler in Zigbee_Level_ColorTemperature_Bulb
2021-10-21T05:18:00.107686194+00:00 DEBUG Zigbee Level ColorTemp Bulb v3.9 Zigbee Dimmer device thread event handled
2021-10-21T05:18:00.179915402+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee
2021-10-21T05:18:00.184746361+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x72A8, src_endpoint: 0x0A, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xFD, rssi: -59, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x51, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x04, ZclStatus: SUCCESS > > >
2021-10-21T05:18:00.194420527+00:00 DEBUG Zigbee Level ColorTemp Bulb v3.9 Zigbee Dimmer device thread event handled
2021-10-21T05:18:10.690263612+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee health poll
2021-10-21T05:18:40.691231449+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee health poll
2021-10-21T05:18:44.232148741+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler capability
2021-10-21T05:18:44.238384699+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received command: {“args”:{“level”:70},“command”:“setLevel”,“capability”:“switchLevel”,“positional_args”:[70],“component”:“main”}
2021-10-21T05:18:44.241658282+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Found CapabilityCommandDispatcher handler in Zigbee_Level_ColorTemperature_Bulb
2021-10-21T05:18:44.255432616+00:00 DEBUG Zigbee Level ColorTemp Bulb v3.9 Zigbee Dimmer device thread event handled
2021-10-21T05:18:44.329305491+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee
2021-10-21T05:18:44.334030824+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x72A8, src_endpoint: 0x0A, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xFA, rssi: -62, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x52, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x04, ZclStatus: SUCCESS > > >
2021-10-21T05:18:44.344094199+00:00 DEBUG Zigbee Level ColorTemp Bulb v3.9 Zigbee Dimmer device thread event handled
listening for logs
 /

@nayelyz
This is a problem with the driver change tool.
The software selects compatible drivers by searching for the “deviceLabel” field in the hub’s fingerprints.yml files and should search for the manufacturer and model.

The deviceLabel field is a free text and whoever makes the driver chooses the text.

Then you can choose the driver you want by clicking on the search magnifying glass, all the drivers installed in the hub will appear.
Choose the “Zigbee Level ColorTemp Bulb Mc” and it should work as it matches the manufacturer and model.

This the link to the post with the problem device change tool

Before making the driver change, open two windows for the CLI logcat:

  • In one select the driver “Zigbee Level ColorTemp Bulb Mc”
  • In the other select “Zigbee Level ColorTemp Bulb v3.9”

In this way we see the pairing logs of the bulb to the new driver. Let’s see if there is any warning.

When you paste the logs to send them, give developer </> format to make them look like this.

2021-10-21T05:17:10.670310855+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee health poll
2021-10-21T05:17:23.446488856+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler capability
2021-10-21T05:17:23.452068148+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received command: {“args”:,“command”:“on”,“capability”:“switch”,“positional_args”:,“component”:“main”}
2021-10-21T05:17:23.455549981+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Found CapabilityCommandDispatcher handler in Zigbee_Level_ColorTemperature_Bulb
2021-10-21T05:17:23.459704856+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x72A8, dest_endpoint: 0x0A, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >
2021-10-21T05:17:23.476582731+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> emitting event: {“component_id”:“main”,“attribute_id”:“switch”,“capability_id”:“switch”,“state”:{“value”:“on”}}
2021-10-21T05:17:23.490808648+00:00 PRINT Zigbee Level ColorTemp Bulb v3.9 circadian_Running ; circadian[device] table: 0x1242d08 Inactive
2021-10-21T05:17:23.496762064+00:00 DEBUG Zigbee Level ColorTemp Bulb v3.9 Zigbee Dimmer device thread event handled
2021-10-21T05:17:23.549293689+00:00 TRACE Zigbee Level ColorTemp Bulb v3.9 Received event with handler zigbee
2021-10-21T05:17:23.554023439+00:00 INFO Zigbee Level ColorTemp Bulb v3.9 <ZigbeeDevice: 4716d035-2b0b-4a62-9815-f6a3151a4e63 [0x72A8] (Zigbee Dimmer)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x72A8, src_endpoint: 0x0A, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -60, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4E, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >

@lalooprasad,
It works well?
to update the list

Thanks for the suggestion.
When I try to change the driver using the magnifying glass I get a “check network connection” error and nothing changes.

Interesting
:thinking:, please, allow me some time to check some details about this behavior.

Update:
Ok, I installed two drivers which had the same fingerprint and it appears in “Select a different driver”. In the case of “Zigbee Level ColorTemp Bulb Mc” and “Zigbee Level ColorTemp Bulb v3.9”, both have the same generic fingerprint that allowed the connection of the CREE device? @Mariano_Colmenarejo

It is true that is confusing to display the name of the device instead of the Driver. Remember that is also important that the new driver has the same capabilities in the profile.
I will create a report to have more details about how this tool works so we can know the restrictions. For now, based on the current results we need to make sure that:

  • Both drivers contain the device’s fingerprint
  • The profile called in the new driver’s fingerprint should have the same capabilities.

This is because the model and / or manufacturer of the bulb does not exactly match the one in the driver.

If I can, then I add a print to the logcat so that it prints the model, manufacturer and length of the string.

If I find how to do it, before I tried device: get_manufacturer () and it returned an empty value.

then I will look at it more calmly, or if @nayelyz give me some better suggestion

Check the driver in use in your device now.

Some times get Network error, butthe Change is made good.

Still using driver v3.9. I will get you logs later today.

NO, The Zigbee Level ColorTemp Bulb Mc does not contain the generic fingerprint, therefore it does not find it compatible.
But from my experience in other drivers, it does not find it as compatible because the devicelabel is different.
In Zigbee Level ColorTemp Bulb Mc: it is CREE A-19 60W
In Zigbee Level ColorTemp Bulb v3.9: it is Zigbee Dimmer

I couldn’t replicate that, maybe they weren’t appearing on the list for another reason or if it happened a while ago, a recent change could have been applied.
I had two drivers, first with the same deviceLabel and then I changed it (I even delete completely the package and created it again), in both cases, the driver appeared on the list.
I already reported the request of showing the driver’s name instead and the need for more info about this tool. :+1:

1 Like