Aqara Motor B1 does not report anymore

[wvuyk]

Describe the bug

Related to #3508.

When this issue was originally closed all was working well. But something has changed during the last few versions.
If deCONZ is started sending commands do not get a response on the device anymore. When the Analog Output cluster is read once after starting deCONZ REST API commands start to get response from the Aqara motor. Mainly "lift"=nn commands are sent.
But the REST API does not return any updates of the commands back:

After sending a "lift"=0:

After sending a "lift"=100:

Note that only "lastseen" is changed here. So it looks like reporting is not active anymore.

Steps to reproduce the behavior

Expected behavior

Reporting back in REST API

Screenshots

Environment

• Host system: PC
• Running method: Windows
• Firmware version: 26650700
• deCONZ version: 2.09.01
• Device: ConBee II
• Do you use an USB extension cable: no -- only relevant for ConBee I/II
• Is there any other USB or serial devices connected to the host system? none

deCONZ Logs

Additional context

[ebaauw]

Did you try and power cycle the B1?

[wvuyk]

I think he has done this. The user is having 5 curtain motors and all are showing the same results. I have forwarded your suggestion to him just now so he can try it. Will report back when I have an answer

[wvuyk]

@ebaauw

No, taking out the battery and reinserting does not change anything, still a first read by hand on Analog output is needed here to have the device accepting commands. Anything we can try to understand what might go wrong?

[ebaauw]

Is this only after starting deCONZ, or after not interacting with the B1 for a while? This doesn't make sense to me, as the B1 is reachable, since they can read the Analog Output cluster.

We need to figure out if its the communication between the coordinator and the B1 or the REST API plugin. After starting deCONZ, can they write the Present Value attribute in the GUI to open/close the curtains, or do they need to read the value first?

What commands are they sending? Do they have deCONZ logging or Zigbee sniffing to see what Zigbee commands the REST API Plugin makes of these?

[wvuyk]

I can collect the commands send and webhook returns. He is running windows so tracing as far I know is not going to work out. Would love it if that would someday be enabled as my plugin has many Windows users Same for sniffing I am afraid.

Not executing commands is only after starting deCONZ longer no interaction is not a problem as far we checked. Once communication has been starting by the read, comands are accepted, but no updates are send on the current status as shown in the above JSON samples. Except for lastseen nothing is updated.

Commands send by my plugin are normally only "lift"=nn commands. I am not using open commands here.

[wvuyk]

@ebaauw

User has checked on the Present Value:

Stop - start deConz
Write a value to Present Value, the motor responds correct
Control the motor by JowiHue works now also without a read

But no updates on current position on the lift..

[ebaauw]

So it would seem that the API plugin doesn’t fully restore the resource until it receives a message from the device. Maybe a side effect of the /lights resources now (finally) being available on startup?

As for the updates: does the API update the state when reading the attribute in the GUI? If so, it’s probably a missing binding and/or attribute report configuration. If not, there’s something broken. Does the API update battery and lastupdated of the ZHABattery resource?

[wvuyk]

Attributes are changing in the GUI according to the user. Will check on the battery values

If this would be a side effect, would it not be the same for an IKEA blind? I have one here and it is functioning fine, after a restart of deCONZ commands are executed fine through the plugin.

[SwoopX]

Seems like #4139 is related to that. Interestingly, after a recent restart, the plug came up like this (note the name).

[ebaauw]

Attributes are changing in the GUI according to the user.

Then the reporting by the B1 to the coordinator is working. Definitely a REST API plugin issue.

note the name

Could mean that name wasn't written to the database (could happen if you restart deCONZ too soon after pairing), or that the resource wasn't properly restored. This seems consistent with having to trigger a message from the device to the gateway, so the API plugin initialises the resource in full.

would it not be the same for an IKEA blind

Both my mains-powered lumi.curtain and IKEA FYRTUR work fine in v2.9.0 and v2.9.1.

The Analog Output and Analog Input clusters use a float data type for Present Value. Historically this has been challenging for deCONZ (both core and REST API plugin). The standard Window Covering cluster uses integer data types.

[SwoopX]

Could mean that name wasn't written to the database (could happen if you restart deCONZ too soon after pairing), or that the resource wasn't properly restored. This seems consistent with having to trigger a message from the device to the gateway, so the API plugin initialises the resource in full.

No clue what might have happened here. I just checked the DB entries and it seems as if all resources were in state deleted since 5 days. However, I could swear that the device name turned to its NWK just yesterday... Regardless, I'll keep an eye on that (but that's a different topic).

Anyway, the reference made still shows similarities.

[github-actions]

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.

[wvuyk]

The issue is still in need of a solution? what can we do to get this solved?
How can we deliver a trace through using Windows? Why is this not made possible?

Current status:

When deCONZ is started, a read is needed of Present Value before any command is accepted. From then on commands are accepted, but reporting is not doen, so my plugin does not get the status updates.

The user has a Zigbee sniffer, ordered a China Aqara hub 2 and discovered he can do initial settings with the Xiaomi bridge. For one he found how the curtain can be controlled by hand (in id oxF0000, bit 0x20000. Bit is read only, but the aqara hub seems to have tricks to go around this.... Not sure if this is useful to anyone.

I am sure if sniffing helps for this issue, I can ask him?