(EDGE Driver-Mc). New Zigbee Device Config Mc driver

Developer Programs Writing Edge Drivers
1

(EDGE Driver-Mc). New Zigbee Device Config Mc driver

Similar to Z-wave Device Config Mc, it is a tool to configure options or atributes settings in devices that do not exist in the edge drivers.

It has integrated almost all the standard clusters from the lua libraries and several custom clusters, lumi, ikea libraries,… to be able to offer information on the device’s responses to the commands sent.

It is also useful to use the CLI logs simultaneously to see response messages or errors in the commands that are not captured by the driver.

It has three selectable profiles from the preference settings:

Screenshot_20241123-115351
Screenshot_20241123-115351864×1920 95.1 KB

  • Device Fingerprints Info: This is the default profile and is the same as Zigbee Thing Mc. It shows the device’s fingerprints, clusters, and endpoints.

Screenshot_20241123-120424
Screenshot_20241123-120424864×1920 93.8 KB

Screenshot_20241123-120446
Screenshot_20241123-120446864×1920 107 KB

  • Device Attribute Read or Write: This profile allows you to read or write values ​​from clusters and their attributes to be able to configure operating options, such as:
    • Restore device status after a power loss.
    • Configure the status of the LED indicator, child lock or any other cluster, attribute, data type and values ​​that we know.
    • some Tuya examples:

DP38 Relay status

Direction Cluster ID Command/Attribute ID Value
server 0x0006: On/Off 0x8002: Tuya-specific attribute
Data type : enum8 (0x30)
  • 0: Off.
  • 1: On
  • 2: Last on/off state|

DP40 Indicator mode

Direction Cluster ID Command/Attribute ID Value
server 0x0006: On/Off 0x8001: Tuya-specific attribute
Data type : enum8 (0x30)
  • 0: Off.
  • 1: Indicates status. The indicator comes on when the switch is turned on.
  • 2: Indicates position. The indicator comes on when the switch is turned off.|

DP41 Child lock

Direction Cluster ID Command/Attribute ID Value
Client to server 0x0006: On/Off 0x8000: Tuya-specific attribute * 0: Release* 1: Lock
Data type : boolean (0x10)
  • In devices with battery, which are asleep, we normally have to wake them up before sending the read or write command so that they respond.

Screenshot_20241123-115155
Screenshot_20241123-115155864×2104 112 KB

Screenshot_20241123-115034
Screenshot_20241123-115034864×1920 96.3 KB

Screenshot_20241123-115115
Screenshot_20241123-115115864×1920 92.7 KB

  • For custom cluster and attributes you need write the Manufacturer Code in Hexadecimal format

  • For standard zigbee clusters and attributes the manufacturer code field must be nil

  • Device Attribute Configure Reporting: This profile allows reading and writing the configuration of cluster report intervals and their attributes.

    • This configuration report should not be changed in devices that work with drivers that have the Health_Check function activated.

    • With firmware version 55.x smartthings have announced that in the stock drivers they are going to disable the Health_check function,
    • In my Mc drivers I am also going to disable it, for the moment, in devices with battery, in which it never served any purpose.
      In several Mc drivers already have preferences to customize the report configuration to save battery and in general to unload the zigbee network from repetitive messages and reduce the work of the Hub and therefore it is not necessary to use this driver.
      You can modify interval reports from preferences and since when you go back to the Mc driver, the settings in preferences will be reset or may become out of sync

The easiest way to use it is:

  • Write the cluster and attribute fields you want to configure in hexadecimal format.
  • Select the Read Attribute option
  • Click on execute action

Screenshot_20241123-115658
Screenshot_20241123-115658864×2898 201 KB

  • With the device’s response you will know the current configuration, minimum interval, maximum interval, reportable change and data_type and the Success or error status.
  • If you want you can change any value
  • Select Write Attribute and click on action.
  • The new values ​​will be sent and the SUCCESS status or an error will be displayed if there is one.

Screenshot_20241123-115747
Screenshot_20241123-115747864×2856 210 KB

  • For custom cluster and attributes you need write the Manufacturer Code in Hexadecimal format
  • For standard zigbee clusters and attributes the manufacturer code field must be nil

Screenshot_20241123-115911
Screenshot_20241123-115911864×2846 201 KB

When Cluster info capability remains in Waiting…Info then and error message and does not captured by driver, you can see it in cli logs

If you detect any operating error I will try to solve it.

This is the driver version

───────────────────────────────────────────────────
 Name         Zigbee Device Config Mc
 Version      2024-11-23T12:32:32.575573315        
───────────────────────────────────────────────────

My Beta Drivers channel link: SmartThings. Add a little smartness to your things

As some users have asked me, if you find these Mc drivers useful and wants to invite me to a coffee, Thanks

13 Likes
2

Awesome! This driver looks like a game changer for devices that should work as documented but simply don’t. Reduces the turnaround time to a few clicks. I wish I had it a week ago.

3

A week ago it didn’t exist and if smartthings hadn’t announced that they will disable the health_check feature in stock drivers I wouldn’t have done it, since it would generate unnecessary work for the hub and an increase in network traffic polling devices if it doesn’t receive messages at the default intervals.

Therefore, if you extend more of 1.5 x max interval report the intervals in the standard or custom capabilities with respect to your driver configuration and monitoring values, you have to disable health_check in the driver.

Setting health_check = false in your driver template.

1 Like