Problems with Vimar Window Covering device

deCONZ General Support
1

Does the issue really belong here?

  • I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

  • I have searched the existing issues and there is none for the bug at hand

Describe the bug

I have 3 Vimar window covering devices paired to Conbee II.
Until today they worked OK.
Today one of them didn’t respond to OPEN commands even if sometimes the circle was blinking blue.
I resetted by F5 and now I have:
image

Normally it’s:
image

Steps to reproduce the behavior

Press F5 and wait

Expected behavior

I expect device working as usual

Screenshots

No response

Environment

  • Host system: Raspberry Pi 3b
  • Running method: Raspbian
  • Firmware version: 0x26780700
  • deCONZ version (not Home assistant Addon version!): v2.26.2-beta
  • Device: ConBee II
  • Do you use an USB extension cable: yes
  • Is there any other USB or serial devices connected to the host system? NO
2

Smanar commented

For me it’s an inclusion problem.
Your device is not full included (the 0xffff), try to re-include it, without delting it.

3

LeoeLeoeL commented

There is no way to fix that manually.
Even resetting the device from the device (very very annoying method). I also paired the device to Zigbee2Mqtt (using another coordinator) and then paired again to Deconz.
Same picture as above.
I had something similar few week ago.
Deconz fixed that after 4 or 5 days. The difference was that last time the device didn’t work until deconz fixed it.

4

After few hours Deconz fixed a little bit:
image

Is that normal?
What happened in these hours?

5

It have just retry, and retry and retry again, up the device finaly send the missing data.
You can help deconz to do that too Xiaomi: Lost devices or functional issues · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

(the procedure is a little different, deconz have evolued since, but the procedure is same, except you don’t need to awake the device for a covering, not a sensor)

6

After Read simple descriptors the list became complete again:
image.
But this is a workaround.
Why deconz do have this kind of problems when pairing?

7

It can come from the device too, deconz ask for information at every inclusion, the device is free to answer or not, can be connexion issue. But i don’t say it can’t be from deconz.
You have 3 coverings, if only one have issues, can be the guilty.
This issue happen generaly on sensor, less talkative and sleepers, realy rare on routers.