Moes AM43 issues with deConz

deCONZ General Support
1

Hey guys, I have a strange issue with 2 motors, I’d like to pickup your brain. With the motors paired to deConz and exposed to HA, I was able to use the motors.

However, since last week, one motor can’t be controlled anymore, it is exposing it’s state to Home Assistant (open, close, position) but any up/down orders are ignored. I’ve tried to delete the node, repairing it, factory default, repairing it, rebooting the deconz add-on, restarting the integration in HA, nothing.

Another motor is seen as disconnected in Home Assistant, but it is well there in deConz, I see it as active, I can read descriptors etc.
I’ve tried to bypass Home Assistant by using API’s, the motor doesn’t do anything.

Any idea what could be going on ?

Thanks !

Johan

2

OK I figured out what was going on, I did generate a new key (hoping that won’t erase the existing key).
Smart plug 24 doesn’t work, 28 is working though. So the method works, something is going on with 24.

So the set position is waorking if you use direclty the API but not on HA ?

Can you share the error message when you make the request for the 24 ? With "reachable": true I don’t see what can block the working mode.

And no, don’t worry you can generate 500 keys (phoscon create a new one at every connexion), the problem is more to delete them after.

3

Strangly enough, i got a 200 return code, no error message.

One thing I’m thinking is to do a power cycle of my HA box, I did reboot the unit a few times, but I’m wondering if the Conbee II radio wouldn’t be the problem. Is it possible it would shun some devices ?

4

OK I did progress, one motor is fixed (the one that was disconnected), I’ve deleted it from deConz and re-paired it. This is the motor Smart Plug 24.

5

Working with the 29, the one that is ignoring my orders but would report status (position), I’ve tried to send it the lift request, I’ve got a HTTP 200 No Error.

6

Just to add on this one, trying the same API call with another motor works, with this one, nothing.

7

All deconz request return a message even sucess one, you are using command line or REST client ?

The other one is working out of HA, so you probably have error message when you use it with HA ?

8

I get this message in deConz 08:14:29:240 Send Tuya request 0xB4E3F9FFFE3C40C4 : Dp_type: 0x02, Dp_identifier 0x02, data: 00000032.

I’m using CocoaClient to generate my rest request, to answer to your question.

9

BTW this morning, I have the same exact behaviour with the motor I have repaired yesterday. It was working fine yesterday. Same message in the deConz logs.

10

image
image1158×948 67.8 KB

11

I m lost here, what are you trying to do ?
So you have the device 24 with json

{
  "capabilities": {
    "alerts": [
      "none",
      "select",
      "lselect"
    ]
  },
  "config": {
    "groups": [
      "0"
    ]
  },
  "etag": "1d3b1aca39987190d7e35a184c0474ac",
  "hascolor": false,
  "lastannounced": "2023-03-15T23:00:39Z",
  "lastseen": "2023-03-16T11:24Z",
  "manufacturername": "_TZE200_zah67ekd",
  "modelid": "TS0601",
  "name": "Smart plug 24",
  "productid": "Tuya_COVD AM43-0.45-40",
  "state": {
    "alert": "none",
    "bri": 0,
    "lift": 0,
    "on": false,
    "open": true,
    "reachable": true
  },
  "swversion": null,
  "type": "Window covering device",
  "uniqueid": "b4:e3:f9:ff:fe:3c:40:c4-01"
}

What is the 26 one ?

It’s the 24 who is disconnected, and the 26 that is working using API but not using HA ?

Can you just make this request on the 24 one (the disconnected, the ID can have moved now)
POST request on http://IP:PORT/api/APIKEY/lights/24/state with the body {"lift":50}
And show me the result pls ?

PS:
On your capture, the request have failed.

12

Sorry I should have mentioned that, as I have reassociated the motors, 24 → 25, 29 → 31.

25 worked for a few hours but not it has the same behaviour as 31.

Here is the lift for 25 :

image
image1374×1112 63.5 KB

13

Here is a get for 25

{
  "capabilities": {
    "alerts": [
      "none",
      "select",
      "lselect"
    ]
  },
  "config": {
    "groups": [
      "0"
    ]
  },
  "etag": "5f98986105fd6b2fbc8d375f99dfd507",
  "hascolor": false,
  "lastannounced": null,
  "lastseen": "2023-03-17T20:53Z",
  "manufacturername": "_TZE200_zah67ekd",
  "modelid": "TS0601",
  "name": "Smart plug 25",
  "productid": "Tuya_COVD AM43-0.45-40",
  "state": {
    "alert": "none",
    "bri": 50,
    "lift": 20,
    "on": true,
    "open": true,
    "reachable": true
  },
  "swversion": null,
  "type": "Window covering device",
  "uniqueid": "b4:e3:f9:ff:fe:3c:40:dd-01"
}
14

Phoscon accepts the request, I don’t know if they are any logs I could see to figure out if the request is well sent over by the radio (Wireshark would be great to do this).
Anyway the motor doesn’t do anything.

15

I could see to figure out if the request is well sent over by the radio (Wireshark would be great to do this)

08:14:29:240 Send Tuya request 0xB4E3F9FFFE3C40C4 : Dp_type: 0x02, Dp_identifier 0x02, data: 00000032

This line mean deconz make the zigbee request, 32 is 50 in hexa.
So up to this, all is fine, no error in deconz logs ?

You are sure it’s not a connexion issue ? Batterie is fine ?

16

As far as I can tell, I can get the status of the motor, if I use the button on the motor, i can see the lift position when I ask Phoscons a status.

When I sent a request :
11:57:30:049 Send Tuya request 0xB4E3F9FFFE3C40C4 : Dp_type: 0x02, Dp_identifier 0x02, data: 00000064

Status :

{
  "capabilities": {
    "alerts": [
      "none",
      "select",
      "lselect"
    ]
  },
  "config": {
    "groups": [
      "0"
    ]
  },
  "etag": "1cb78022b651672b9933f320e412c9c0",
  "hascolor": false,
  "lastannounced": null,
  "lastseen": **"2023-03-18T15:22Z",**
  "manufacturername": "_TZE200_zah67ekd",
  "modelid": null,
  "name": "Smart plug 33",
  "productid": "Tuya_COVD AM43-0.45-40",
  "state": {
    "alert": "none",
    "bri": 0,
    "lift": 0,
    "on": false,
    "open": true,
    "reachable": true
  },
  "swversion": null,
  "type": "Window covering device",
  "uniqueid": "b4:e3:f9:ff:fe:3c:40:c4-01"
}
17

image

18

The RSSI looks to be decent, the unit is like 3m away from the hub.

19

So the connexion seem fine, but the device don’t answer to request …

When I sent a request :
11:57:30:049 Send Tuya request 0xB4E3F9FFFE3C40C4 : Dp_type: 0x02, Dp_identifier 0x02, data: 00000064

You can share a deconz log with APS info_l2 and info after this request ?

And BTW dp = 0x02 is for set position request, the open and close request are broken too ?

20

Here is a few lines of logs after requesting the lift request :

11:41:42:824 Send Tuya request 0xB4E3F9FFFE3C40C4 : Dp_type: 0x02, Dp_identifier 0x02, data: 00000064
11:41:44:776 ZCL attribute report 0xB0CE1814036BDB78 for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
11:41:45:788 ZCL attribute report 0x00158D0007E48B21 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
11:41:45:879 ZCL attribute report 0x00158D0007E48B21 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
11:41:45:945 emit event/tick: 0xb0ce1814036bdb78
11:41:45:981 ZCL attribute report 0x00158D0007E48B21 for cluster: 0x0403, ep: 0x01, frame control: 0x18, mfcode: 0x0000 
11:41:45:988 	0xB0CE1814036BDB78 force poll (2)
11:41:47:099 ZCL attribute report 0xB0CE1814036BDB78 for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
11:41:52:360 SC tick --> StateRead state/on, b0:ce:18:14:03:6b:db:78-01
11:41:52:420 SC state/on: synced
11:41:52:421 SC --> StateFinished
11:41:52:421 SC state change finished: b0:ce:18:14:03:6b:db:78-01
11:41:52:614 ZCL attribute report 0xB0CE1814036BDB78 for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000

I’ve tried a few states available for the motor :
“bri”: 0,
“lift”: 0,
“on”: false,
“open”: true,

None of those works.

I’m trying to think that the problem might with the motor, did I hit a bug on the motor itself ?

Is there any way I could see the version of firmware running on the motor ? When I request the status from the API for the smart switch, the sw field is empty : “swversion”: null, the battery sensor doesn’t have any swversion field.