deconz-rest-plugin
deconz-rest-plugin copied to clipboard
dresden-elektronik
Aqara Vibration Sensor stopped working after Update to .86
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
- Pair sensor via Phoscon GUI
- Wait for pairing to complete
- Click on sensor
- No data is shown neither is via API
Expected behavior
Vibration events should be recognized and shown.
Screenshots
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
I have just downgraded to .83. It works again. Seems to be a bug with the newer build.
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
@Agratam Do you specifically mean that everything works EXCEPT the vib sensor?
Yes, everything else works. i.e.: Tradfri Lights and Switches Aqara Temperature and Motion sensors
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. :-)
Just confirming that I also have the issue. 2.05.85/26390500/Conbee1 (Marthoc container).
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.
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.
I am sorry. You are absolutely right. It is working fine with the fixed xml. Sorry.
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.
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.
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.
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
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)
