search

dresden-elektronik / deconz-rest-plugin

deCONZ REST-API plugin to control ZigBee devices
BSD 3-Clause "New" or "Revised" License
1.89k stars 496 forks source link

Aqara Vibration Sensor stopped working after Update to .86 #3455

Open peer69 opened 3 years ago

peer69 commented 3 years ago

Describe the bug

After Update to .86 and FW 26660700 using ConBee II the Aqara Vibration Sensor stopped working. It did not send any commands, at least none of them were visible in Phoscon or deCONZ GUI. I have tried repairing it but it seems like the device is not fully recognized anymore. GUI does recognize it as vibration sensor and it builds the cluster correctly from what I can see but no data is shown via Phoscon or API. I can see the sensor flashing blue in GUI when it is triggered but it never updates. I tried a second sensor but it doesnt work either.

Steps to reproduce the behavior

  1. Pair sensor via Phoscon GUI
    1. Wait for pairing to complete
    2. Click on sensor
    3. No data is shown neither is via API

      Expected behavior

      image image ## Environment
      • Host system: Ubuntu 16.04
      • Running method: ESXI 6.7
      • Firmware version: (26660700)
      • deCONZ version: (2.05.86)
      • Device: (ConBee II)
      • Do you use an USB extension cable: (yes) -- only relevant for ConBee I/II
      • Is there any other USB or serial devices connected to the host system? If so: Which? no.

      deCONZ Logs

      Additional context

Mimiix commented 3 years ago

What happens if you click the button on it?

peer69 commented 3 years ago

Device in GUI flashing blue. Nothing to see in phoscon or via API.

peer69 commented 3 years ago

I have just downgraded to .83. It works again. Seems to be a bug with the newer build.

image
Agratam commented 3 years ago

2.05.84 works too. I have the same issues with 2.05.86.

Host system: Ubuntu 20.04 Firmware version: (26660700) deCONZ version: (2.05.86) Device: (ConBee II) Do you use an USB extension cable: (yes) -- only relevant for ConBee I/II Is there any other USB or serial devices connected to the host system? If so: Which? Yes. Aeotec Zwave Stick

Mimiix commented 3 years ago

@Agratam Do you specifically mean that everything works EXCEPT the vib sensor?

Agratam commented 3 years ago

Yes, everything else works. i.e.: Tradfri Lights and Switches Aqara Temperature and Motion sensors

Mimiix commented 3 years ago

Alright, thanks :)

Mimiix commented 3 years ago

I've created a internal issue. I'll have this addressed.

SAOPP commented 3 years ago

Yes guys still broken vibros...

FunkOdyssey2001 commented 3 years ago

I have this issue in 2.05.85 and 2.05.86.

SAOPP commented 3 years ago

@FunkOdyssey2001 yes dat right, it's begin from 95th beta.

FunkOdyssey2001 commented 3 years ago

I am not really a developer, but in 2baf9573f18035fc182fa67fa8c4662e2fa50bd2 there were several lines deleted. I could not find similar lines in the current code for lumi.vibration. But again: I don't know if this is right or wrong. :-)

nikbr998 commented 3 years ago

Just confirming that I also have the issue. 2.05.85/26390500/Conbee1 (Marthoc container).

Mimiix commented 3 years ago

No need for others adding "i have it too". It is known

ebaauw commented 3 years ago

For reasons only known by Xioami, this sensor uses the Door Lock cluster. Probably adding support for one of the locks broke support for the vibration sensor.

manup commented 3 years ago

I'll make some tests later on with debugger to see where it fails.

Mimiix commented 3 years ago

Will be fixed in new beta! :)

SAOPP commented 3 years ago

Thanks guys for quick fix it.

FunkOdyssey2001 commented 3 years ago

Is this fix working for you? I don't see any new values.

Mimiix commented 3 years ago

NEed to wait for the new release or compile it yourself @FunkOdyssey2001 ;)

FunkOdyssey2001 commented 3 years ago

That's what I did. A current checkout, compiled and copied.

SwoopX commented 3 years ago

With the change made by @manup, you don't need to compile the plugin. Just replace the general.xml from the pulled repo with the version running on your system. Otherwise, that file will just be overwritten with by a new release package.

FunkOdyssey2001 commented 3 years ago

I am sorry. You are absolutely right. It is working fine with the fixed xml. Sorry.

SwoopX commented 3 years ago

Np, glad we got confirmation.

cracyfloyd commented 3 years ago

i was going back to version 84 and now it works again.

sophof commented 3 years ago

Thanks for point me to this thread. I replaced the general.xml file and can confirm that the sensors are currently working. One sensor is not currently picked up by Home Assistant, but that could be due to my previous tinkering, I expect it to work once I re-add it.

timbru31 commented 3 years ago

While my sensors initially showed data again after repairing them (I’ve had the very very binding), the stop working after a while (time ranges from hours to days). It seems the same as #2581 and #2591 - I suspect the sensitivity values changes and thus breaks my use case (window open detection)

They remain available in the GUI and the API shows a lastseen timestamp, however the updated value does not match, nor detects it the correct vibration.

manup commented 3 years ago

Is this with a version v2.5.87 or later? The vibration sensor got a fix in there, just checked mine with v2.6.0 it is working.

timbru31 commented 3 years ago

I could've sworn that I was on .87, but apt says it's still .86. Going to test v2.6.0 and will report back (once it either works fine for a longer period or when one becomes buggy again).

Btw ConBee II with FW 26660700

aberkeley commented 3 years ago

Hi i am on 2.0.8 with FW 26680700 Conbee ii. my sensor appears in deconz but isnt recognised nor is it appear in Phoscon (as you would expect)

image

image

SwoopX commented 3 years ago

The device is not paired correctly/completely.

aberkeley commented 3 years ago

The device is not paired correctly/completely.

thx swoop - removed and re-pair all working now thx

Mimiix commented 3 years ago

@peer69 As others reported it works again, can you confirm that it was fixed for you too?

aberkeley commented 3 years ago

Hi - as of today i can report i now have the same issue. Having got the item working (thx swoopX) with a re-pairing. I had to move the device (so i deleted it and then attempted to re-add) - this is successful- now i get the same as the original poster:

image

the sensor is fine on deconz vnc view:

image

2.0.8 with FW 26680700

SwoopX commented 3 years ago

Your device node descriptor looks odd. You might want to give this a try: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Xiaomi:-Lost-devices-or-functional-issues

bcutter commented 3 years ago

Still not tracked down/fixed? Will implement one of those sensors shortly and don´t want to spend hours to find out "jap, same issue" :-)

jjdave2002 commented 2 years ago

Hi, just saw this post and want to ask if there is any solution to the fact, that sometimes vibration sensor is detected as "door lock" and then does NOT update the status in Deconz. My system was running without any failure, with FW x26680xxx, then I had to update to due some issues with zigbee 3.0 sensor to x26700700 or x26720700 - after the update, all vibration sensors did no longer work. No update on their status in deconz. So what to do??

Thank you!

bcutter commented 2 years ago

Two of those are working just fine related to this issue.

They sometimes trigger without an actual movement/vibration ("phantom vibration" if that issue got not a name yet) which is pretty annoying.

But nothing substantial to add for this issue.

jjdave2002 commented 2 years ago

I do not have that phantom trigger, mine are once triggering and then always stayed in "vibration" mode, so they do NOT reset the vibration detection after the vibration was gone. Everything was fine until the update of the FW (which is neede for the zugbe 3.0 sensors). Any other ideas? Curious as they sensor are named as "door lock", or not? Maybe anything I could check and or change in the ClusterInfo ???