Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tuya ZigBee Garage Door Opener #5685

Closed
0rsa opened this issue Jan 20, 2022 · 12 comments
Closed

Tuya ZigBee Garage Door Opener #5685

0rsa opened this issue Jan 20, 2022 · 12 comments

Comments

@0rsa
Copy link

0rsa commented Jan 20, 2022

Device

H3c695045c9e340878439fea02d29c899A
https://fr.aliexpress.com/item/1005003532414239.html

  • Product name: ZigBee Garage Door Opener
  • Manufacturer: _TZE200_wfxuhoea
  • Model identifier: TS0601
  • Device type:
    • Lock (it comes with a radio submodule which communicates with main module, I can see network activity in deconz GUI when I open/close submodule)
    • Other: dry contact

Screenshots

basiccluster
clusterota
clustertuyaspecific
details
nodeinfo

Thank you

@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Feb 11, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

@dustnipe
Copy link

dustnipe commented May 3, 2022

I'm stuck with the same problem. (_TZE200_wfxuhoea) Is there any activity on this?

@Mimiix
Copy link
Collaborator

Mimiix commented May 3, 2022

@Smanar can this be done with DDF?

@Mimiix Mimiix reopened this May 3, 2022
@dustnipe
Copy link

dustnipe commented May 3, 2022

The switch itself is recognized but doesn't work when triggered. I can switch the on-state between false and true but the contact wires at the device stay always open.

"10": {
"etag": "5ce99a67334d7cb2fe41f6a0463094c0",
"hascolor": false,
"lastannounced": "2022-05-03T08:39:16Z",
"lastseen": "2022-05-03T08:39Z",
"manufacturername": "_TZE200_wfxuhoea",
"modelid": "TS0601",
"name": "Garagenoeffner",
"state": {
"alert": "none",
"on": false,
"reachable": true
},
"swversion": null,
"type": "Smart plug",
"uniqueid": "a4:c1:38:be:ee:b3:f2:a1-01"
},

The sensor is not recognized but there is activity in the debug log:

when opened:
14:15:37:629 Tuya debug 4 : Address 0xA4C138BEEEB3F2A1 Payload 00a00301000101
14:15:37:629 Tuya debug 5 : Status: 0 Transid: 160 Dp: 259 (0x01,0x03) Fn: 0 Data 1

when closed:
14:15:39:540 Tuya debug 4 : Address 0xA4C138BEEEB3F2A1 Payload 00a30301000100
14:15:39:540 Tuya debug 5 : Status: 0 Transid: 163 Dp: 259 (0x01,0x03) Fn: 0 Data 0
14:15:39:612 Tuya debug 4 : Address 0xA4C138BEEEB3F2A1 Payload 00a40c04000102
14:15:39:613 Tuya debug 5 : Status: 0 Transid: 164 Dp: 1036 (0x04,0x0C) Fn: 0 Data 2

@Smanar
Copy link
Collaborator

Smanar commented May 3, 2022

0x01 0x03 is probably the on/off

I can switch the on-state between false and true but the contact wires at the device stay always open.

This is not normal ... You switch the device manualy, but the wire stay open ?

This device used the tuya cluster need to try something like for this one #5869
Explanation here #5868

The dpid to use for state/on is 3

@github-actions github-actions bot removed the stale label May 4, 2022
@rafaelcorvalan
Copy link

I'm having issues with this device too. I have 1 device, 2 entities which are sensors, no switch. Any idea ?

    "entities": [
      {
        "entity_id": "sensor.tze200_wfxuhoea_ts0601_0f1e399a_basic_rssi",
        "name": "_TZE200_wfxuhoea TS0601"
      },
      {
        "entity_id": "sensor.tze200_wfxuhoea_ts0601_0f1e399a_basic_lqi",
        "name": "_TZE200_wfxuhoea TS0601"
      }
    ],

@Smanar
Copy link
Collaborator

Smanar commented May 26, 2022

Hello, can you give at least a DDF skeleton ?

  • Configure the basic cluster identification (if not auto filled)
  • Drag and drop a "on off light"
  • Drag and drop a ZHAdoorsensor
  • save the file, and remember the path to edit it later
  • share the DDF.

Edit:
BTW are you sure you are using deconz ?

@dustnipe
Copy link

dustnipe commented May 27, 2022

Thanks to your comment @Smanar, I managed to get the sensor to work. (Even though I don't really understand what I do :P)

I added the ZHAOpenClose template in DDF to the device with the following parameters
{ "name": "state/open", "refresh.interval": 3, "parse": { "dpid": 3, "eval": "Item.val = Attr.val;", "fn": "tuya" }
DPID 3 is showing the status of the magnetic door sensor and does work now. Which is great!

But I still have no clue on how to really switch the device to open/close the garagedoor. Any further suggestions?

edit: I've worked it out. It took a while for me to really understand that "write" is not yet supported by the DDF Editor. With the following config I can now also kind of control the device.

{ "schema": "devcap1.schema.json", "manufacturername": "_TZE200_wfxuhoea", "modelid": "TS0601", "product": "TS0601", "sleeper": false, "status": "Bronze", "path": "/devices/ts0601.json", "subdevices": [ { "type": "$TYPE_OPEN_CLOSE_SENSOR", "restapi": "/sensors", "uuid": [ "$address.ext", "0x01", "0x0500" ], "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": "config/on" }, { "name": "config/reachable" }, { "name": "state/lastupdated" }, { "name": "state/open", "refresh.interval": 3, "parse": { "dpid": 3, "eval": "Item.val = Attr.val;", "fn": "tuya" } } ] }, { "type": "$TYPE_ON_OFF_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/on", "refresh.interval": 5, "parse": { "dpid": 12, "eval": "Item.val = Attr.val;", "fn": "tuya" } "write": { "dpid": 12, "dt": 0x10, "eval": "Item.val;", "fn": "tuya" }, { "name": "state/reachable" } ] } ], "bindings": [ { "bind": "unicast", "src.ep": 1, "cl": "0xEF00" } ] }

DPID 3 reads out the door sensor.
DPID 12 (0x0C) is the right one to control the door signal.

But now I have an on/off switch and when I trigger it (no matter if on or off) the device will send the door signal which is 3s on and then off. So in principle I want to configure a latching switch. Is there also a function for it in deconz?

@Smanar
Copy link
Collaborator

Smanar commented May 27, 2022

DPID 12 (0x0C) is the right one to control the door signal.

14:15:39:612 Tuya debug 4 : Address 0xA4C138BEEEB3F2A1 Payload 00a40c04000102
14:15:39:613 Tuya debug 5 : Status: 0 Transid: 164 Dp: 1036 (0x04,0x0C) Fn: 0 Data 2

I m not sure, because 0x04 mean the value is a number not a bool, from other project they are using 0x01 but as toggle command not on/off, so will see the result

But now I have an on/off switch and when I trigger it (no matter if on or off) the device will send the door signal which is 3s on and then off

I don't realy understand what happen with the dpid = 12, but it seem perfect, your device just need to send an impulsion, like on real hardware, you don't keep the switch pressed to open the garage ?

Make a try with the 0x01 to check if it s better.

{
  "schema": "devcap1.schema.json",
  "manufacturername": "_TZE200_wfxuhoea",
  "modelid": "TS0601",
  "product": "TS0601",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_OPEN_CLOSE_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0xef00"
      ],
      "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": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/lastupdated"
        },
        {
          "name": "state/open",
          "refresh.interval": 7200,
          "parse": {
            "dpid": 3,
            "eval": "Item.val = Attr.val;",
            "fn": "none"
          }
        }
      ]
    },
    {
      "type": "$TYPE_ON_OFF_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/on",
          "parse": {"fn": "tuya", "dpid": 1, "eval": "Item.val = Attr.val;" },
          "write": {"fn": "tuya", "dpid": 1, "dt": "0x10", "eval": "Item.val == 1 ? 1 : 0;"},
          "read": {"fn": "tuya"},
          "refresh.interval": 300
        },
        {
          "name": "state/reachable"
        }
      ]
    }
  ]
}

@github-actions
Copy link
Contributor

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label Jun 18, 2022
@github-actions
Copy link
Contributor

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants