New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aqara Vibration Sensor Set Sensitivity #1396
Comments
It is possible to set this via the API. I can't remember how though. Search the issues here. |
Sensitivity is from 1 to 21 where 1 is the most sensitive. |
Great. That worked. |
I just did the same for a Hue motion sensor. |
Hi, where I can find the api key? is the number wrote in the HA integration tab? |
I got it working with help of gpl1998 comment above despite no pre-knowledge. Below some hints that had saved time for me:
The chunc of thxt for my vibration sensor:
No guarante that I have got it right but the response on GET is now at least ""sensitivity":1". I hope this comment (my first on GitHub) is recieved well and can save time for someone. |
Hello Stig and thank you for the explanation. Any thoughts what I might be doing wrong? |
Are you sure for the id ? |
I wouldn’t try and make sense of the error message, but it does indicate an error: you need to PUT to |
Yep, you are using bad url, your is finishing by "sensors/20" |
Thank you guys. |
I spent 2h on testing and this doesn't work! the results are identical. sensitivity 1 = 11 = 21 two options:
|
Put the sensor on a table, and knock the table with different sensitivity. It don't work for mouvement, or frequency. And you will have always the same value, true instead of false. |
Knocking on a table is not precise enough and not reproducible. |
I had the same experience. I set the sensitivity to '1' and '21' but didn't notice any difference. When I looked at the status of the sensor I saw that 'sensitivity' was 'pending'. Then I read a post that you have to press the reset button for a few times for 1 second directly after you set the sensitivity. The pending status disappeared and now the sensitivity appeared to be more sensitive. |
I have just updated my Sensor according to the instructions. However, I have had the same experience than @MHOMEASS and there is not difference in the real sensitivity of the sensor. The sensitivity is 21. Any suggestions? |
Are you testing the vibration or the tilt ? |
I have changed the value to 1 and it is much more sensitive. Not as much as I would like but it works! |
Please help me!
What exactly means "a few times for 1 second"? I can't get rid of the ""pending":["sensitivity"]" regardless how often I press the button :( |
If i m right, you can just set the value you want, and wait for deconz be able to change it, can take 1 hour. |
I also have an Aqara Vibration Sensor. I googled around and they always say, change sensitivity from 2 to 1. Some people had null for sensitivity. sensitivitymax was always 21 If I query the sensor I get this response:
My sensitivitymax is 2 instead 21 and sensitivity is negative -8 instead 2 When I try to change the value
I get success
So I send the command, and pushed 2 times the button on the sensor. The blue LED was flashing short, but the value for sensitivity did not change. I also tied other values like -21, -11, -1, -2, 1, 2 .... Any ideas ? PS: running Gateway 2.24.1 |
From last version, value can be only 0/1/2. The -8 value is more worrying ... Edit:
So you can't have 21 with last version. |
My Gateway is 2.24.1 (pre installed with the raspberry image) I tried again with 0 and pushed the button only once, no change |
I updated to 2.24.2, still not successful. |
These questions don't belong here. Please use the forums. |
Hi,
I just add the Aqara Vibration Sensor (https://www.gearbest.com/goods/pp_009661787808.html?lang=en&wid=1433363) and wonder how I can set the sensitivtiy-value in the phoscon-App. In the original Xiaomi-App there are there values for sensitivity: low, medium and high.
At the moment it is obviously not supported in phoscon-app. Is it planed for future?!
The text was updated successfully, but these errors were encountered: