I bought 3 from a different seller on Taobao yesterday, but it still needed to verify my Alipay identity info (despite having the account list late 2019, but not buying anything yet). The process thankfully took less than 24 hours they estimated. Before completing payment again, I searched again and was able to find this one pop up for 30 yuan cheaper than the one I bought! I cancelled the old order and ended up saving about 100 yuan after final international shipping estimates, and I expect it to arrive at my new place a little after I move in a few weeks. My total was $169.38 to the US.
Donāt forget to use a credit card without foreign transaction fees (if you have one)! Thatāll also save some money I assume (havenāt tested with other cards, but Iām going to assume this is the case since itās in a different currency).
1 Like
Heās built and compared a DIY version now too!
He references this thread.
Good coverage of the proās and conās as well
1 Like
Forget Taobao, thereās a bunch back in stock on AliExpress and for reasonably cheaper! Bought 4 from this store for well under the price of my (thankfully failed) Taobao orders where I ordered only 3! Donāt forget the coupons on the store too if you reach the price thresholds!
3 Likes
emontes
June 3, 2022, 12:45pm
47
Nice one, just bought 4 too! Thanks for the heads up.
1 Like
Anybody here have any success using the FP1 with another non-Aqara Zigbee3 hub?
emontes
June 3, 2022, 9:16pm
49
I use mine with Zigbee2MQTT on a Conbee I, no issues here.
tube0013
June 4, 2022, 1:33am
50
Zha should get support for this in next HA release. Dev got one today.
1 Like
Anyone have one of these with pets? Particularly cats since they jump around? My biggest challenge with presence lights is downstairs since we spend most of our time there and have an open floor plan with cats. Thereās basically no place to put a motion sensor thatās cat proof which leaves me with even worse options for presence detection.
Curious if this device has any way to separate pet from human besides aiming it away from them.
1 Like
If you are having a ceiling fan then most likely this sensor is not for you at least for now, it pick up the fan movement, it will always keep the presence state as True until you switch off the fan. I have been trying to place it on different location and height but result still the same.
tube0013
June 4, 2022, 9:06pm
53
Mine hasnāt picked up my dog (a lab on smaller side) at all. And she spends most of the time in the same room as the FP1
3 Likes
Hedda
June 8, 2022, 8:23am
54
FYI, a ZHA integration developer has draft pull requests for work in progress on Aqara FP1 support:
home-assistant:dev ā dmulcahey:dm/zha-aqara-fp1
opened 01:00PM - 04 Jun 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO Nā¦ OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
No
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Add config entities for the Aqara FP1 mmWave presence sensor
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [X] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] š„ Silver
- [ ] š„ Gold
- [ ] š Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
It depends on a quirk which is to be added to the ZHA Device Handlers (a.k.a. zha-quirks) library, see:
zigpy:dev ā zigpy:dm/aqara-fp1
opened 09:26PM - 03 Jun 22 UTC
PR for Home Assistant core will add ZHA config entities for the Aqara FP1 sensor similar to P1 sensor:
home-assistant:dev ā dmulcahey:dm/aqara-p1-config-entities
opened 12:11AM - 25 May 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO Nā¦ OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
No
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This PR adds config entities for the Aqara P1 motion sensor. The triggering time, Visual feedback and sensitivity are all configurable.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [X] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [X] The code change is tested and works locally.
- [X] Local tests pass. **Your PR cannot be merged unless tests pass**
- [X] There is no commented out code in this PR.
- [X] I have followed the [development checklist][dev-checklist]
- [X] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [ ] No score or internal
- [ ] š„ Silver
- [ ] š„ Gold
- [ ] š Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [ ] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
For the Aqara P1 motion sensor, triggering time, visual feedback, and sensitivity are all configurable, ex:
PS: More ZHA discussion on Aqara Presence Detector FP1 (RTCZCGQ11LM; lumi.motion.ac01) here:
opened 06:57PM - 26 Apr 22 UTC
closed 05:13PM - 08 Jul 22 UTC
**Is your feature request related to a problem? Please describe.**
New Aqara FPā¦ 1 sensor is only partially compatible with zigbee2mqtt at this time. I say partially because they haven't figured out how to expose the zone part of the sensor to zigbee2mqtt. I would rather stick with zha so it would be nice if we can get it to work with zha potentially piggybacking off what zigbee2mqtt did as a start.
https://github.com/Koenkk/zigbee2mqtt/issues/11019
https://www.aqara.com/cn/productDetail/Aqara-Presence-Detector-FP1
I don't have the device physically to paste anything here.
Everything Smart Home YouTube Video on this new device: https://youtu.be/Leru0rCS8b0
2 Likes
Hedda
June 8, 2022, 8:34am
55
FYI, Tuya also has several āZigbee Human Presence Detectorā using similar microwave/millimeter wave motion sensor technology to that in the Aqara FP1 sensor.
See example Tuya product models: MSA050-Z1, MIR-HE200-ZB, MYQ-ZHFD02, MSA042D-Z1, MSA035-Z1, and MYQ-ZHFD01.
These are used for either smart human body presence (a.k.a. occupancy/vacancy detection), breathing sensor, or fall-down sensor.
https://expo.tuya.com/smart/sensors/infrared-sensor/occupancy---vacancy-sensor/CT9cn94ki9rh36-CT9cn9la1lzi8j-CT9cndvh3x4xle
https://expo.tuya.com/product/842246
https://expo.tuya.com/product/952001
https://expo.tuya.com/product/1031059
https://expo.tuya.com/product/902056
https://expo.tuya.com/product/804011
https://expo.tuya.com/product/1031058
PS: Note that all of those are listed for global worldwide sale, unlike this competing Aqara FP1 product.
2 Likes
Rusty_nl
June 8, 2022, 11:59am
56
I just received mine and added it in Deconz (as of yesterday its supported) and it seems to work, but so far only basic presence detected or not.
(edit) actually it seems to always show detected and never anything else regardless of presence, so doenst seem to work correctly at the moment
(edit 2) It does work, just with a slow response (as was already known.) Will try to measure how long it takes for the state to change.
1 Like
Been following Tuya for quite some time now in the mmWave space. Iāll be interest to read reviews as they are further distributed. Very interesting applications here for monitoring wellness / safety of elderly individuals.
Stam
June 11, 2022, 9:47am
58
How do we add those new config for FP1 to our HA?
I just got one of these. I have it hooked up via zigbee2mqtt. I am not too impressed. Getting a lot of false positives. The presence status says someone is there even as the presence_event properly tracked that someone left.
18 left , but a bit more expensive than my last link at $50 a pop.
Mine still havenāt even shipped from that last link I sent (anyone get theres from Mi Homes Online Store yet??) and the friggin rep is telling me itāll probably be July 20th even though they told me June 20th and asked me to extend it since it was due to ship earlier. Ready to cancel at this pointā¦
Edit: More found here too. The links seem to hide when you try to search for the actual product, but more always appears under recommended products. Itās like they donāt want our money.
