MS-105Z integration broken

I do have access to the deconz gui. My only problems are:

  • using phoscon / deconz: not recognized as a dimmable light
  • using zha with conbee: state, including brightness, is reporting ok as dimmable light, but commands are not executed
  • using zigbee2mqtt with conbee: state, including brightness, is reporting ok as dimmable light, but commands are not executed

Really strange, there isn’t any magic to send on/off brightness commands as it’s generic.
Perhaps the problem is something we’re not looking in yet like interference.

A few questions to get a more detailed picture:

  • Do you use an USB extension cable?
  • Do other devices in the network accept commands?
  • What is the ConBee II firmware version? (shown in Phoscon App > Menu > Gateway) The latest recommended version is 0x26720700.
  • In deCONZ > Help > Debug view
    Enable logging for INFO and APS, and try to exec on/off commands, this should show errors status codes.
  • I’m not using a USB extension cable
  • Other devices: not yet installed.
  • Conbee firmware 26660700
  • Exec commands not working, only using ZHA or Zigbee2Mqtt, i.e. deconz is not in use in those cases.

To answer your question 2: I just added a regular Tuya switch _TZ3000_npzfdcof TS0001 with ZHA (i.e. no deconz) via ConBee2 and the exec commands from the HA UI are working just fine.

I also paired it with deconz (ZHA desactivated) and excec commands from the HA UI work fine.

Debug info when I’m trying to turn on _TZE200_la2c2uo9 from the UI (paired with deconz)
Copy/Paste not working, here’s a screenshot, command executed at 14:53

Same debug, with APS checked, starting at 15:41

Phoscon will always display a “fairy light”, to known if it have worked you need to check the type in the json.

@manup the issue is “normal” there is that in the code

// dimmer switches
if (R_GetProductId(&lightNode).startsWith(QLatin1String("Tuya_DIMSWITCH")))
{
    lightNode.addItem(DataTypeUInt8, RStateBri);

    ResourceItem *type = lightNode.item(RAttrType);
    DBG_Assert(type);
    if (type)
    {
        type->setValue(QString("Dimmable light"));
    }
    lightNode.setNeedSaveDatabase(true);
}

It’s a tuya device (Smart plug type like all tuya), with no Level Control Cluster, it use the tuya one. The inclusion is event based (need to know the product name during the announce), so it don’t work in 100% of tries. It generaly work with making 2 successives inclusions.
It work at first try using DDF (I have this device too, was my first tuya one)

Not seen as a dimmable light!

{
“etag”: “475006c5a159c39ed1a6731f694da2d2”,
“hascolor”: false,
“lastannounced”: null,
“lastseen”: “2021-12-06T11:41Z”,
“manufacturername”: “Unknown”,
“modelid”: null,
“name”: “Smart plug 3”,
“state”: {
“alert”: “none”,
“on”: true,
“reachable”: true
},
“swversion”: null,
“type”: “Smart plug”,
“uniqueid”: “cc:86:ec:ff:fe:0f:a4:77-01”
}

Interesting, that’s a new error never seen this one before. The 0xAE status in the logs means “APS Table full” I think the outgoing request queue is meant.

A few things:

  • It’s highly recommend to use an USB extension cable, since without it poor signal is very common and causes all sorts of problems.
  • Updating the firmware to 0x26720700. This version has quite some bug fixes compared to older versions. The update is described in https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually
  • It might be worth to double check that only one integration is active (deCONZ, z2m or ZHA).

Since the firmware seems to have a hard time to send anything I’d recommend to get an USB extension cable first to rule out any interference problems.

All right! I guess updating to the new firmware and adding a USB extension fixed all my problems.

My only problem now is that my device MS-105Z (TS0601__TZE200_la2c2uo9) keeps loosing its connexion regularly…

1 Like

Well, I’m trying to pair another TS0601__TZE200_la2c2uo9 device, double inclusion, and still isn’t showing as a dimmable light… It will take me days to pair correctly my 50 devices… I think it’s instable and probably will have to wait for your next release, due in a week or so?

Here you have the DDf I have used on my side

{
  "schema": "devcap1.schema.json",
  "manufacturername": "_TZE200_la2c2uo9",
  "modelid": "TS0601",
  "vendor": "Tuya",
  "product": "Tuya_DIMSWITCH MS-105Z",
  "sleeper": false,
  "status": "Bronze",
  "path": "/devices/dimmer_module.json",
  "subdevices": [
    {
      "type": "$TYPE_DIMMABLE_LIGHT",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/alert",
          "description": "The currently active alert effect.",
          "default": "none"
        },
        {
          "name": "state/bri",
          "refresh.interval": 5
        },
        {
          "name": "state/on",
          "description": "True when device is on; false when off.",
          "refresh.interval": 5
        }
      ]
    }
  ]
}

Hello, any release date for the new firmware?

Where do we need that for?

Actually, it’s the deCONZ update for HA that I’m waiting for…

It is already available as far as i know.

The deConz application in latest HA has a version number v.2.12.6. I don’t see how to enter a ddf file.

In that case you need to ask them.

I just checked, i’ve installed the addon and 6.11.1 seems to be 2.13.4

I’m running:

  • core-2021.12.7 / supervisor-2021.12.2 / Home Assistant OS 7.1
    And the official add-on for deCONZ is version 6.10.0.