Skip to content

Add profile for Aqara FP2#3854

Merged
bramstroker merged 6 commits into
bramstroker:masterfrom
jdambacher:aqara-fp2
Jan 11, 2026
Merged

Add profile for Aqara FP2#3854
bramstroker merged 6 commits into
bramstroker:masterfrom
jdambacher:aqara-fp2

Conversation

@jdambacher

Copy link
Copy Markdown
Contributor

Device information

https://www.aqara.com/en/product/presence-sensor-fp2/

Home Assistant Device information

PS-S02E
von Aqara
Firmware: 1.3.3
Hardware: 1.0.0

Checklist

  • I have created a single PR per device. When you have multiple submissions please create separate PR's.
  • For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
  • For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

@bramstroker

Copy link
Copy Markdown
Owner

Could you change model name to PS-S02E please, and add PS-S02D under aliases.
Also see https://chatgpt.com/share/6963cc6e-4130-800b-b6f4-99a27f293cd3

@jdambacher

Copy link
Copy Markdown
Contributor Author

@bramstroker I could, but I think the product is more known under the name "FP2". What about leaving it as FP2 and add PS-S02E and PS-S02D as an alias?

@bramstroker

Copy link
Copy Markdown
Owner

Using PS-S020E is preferred as we avoid ambiguity. Aqara would probably also use FP2 for a second generation of the precense sensor for example, and then this profile shouldn't be applied.

FP2 is part of the name in model Presence Sensor FP2 so users will be able to find it that way when searching in the profile library.
I'll also make some changes in the future to add the name to the discovery flow (besides the current manufacturer and model_id info), so it's 100% clear for the user which exact device was discovered.

@jdambacher

Copy link
Copy Markdown
Contributor Author

Got it! One question: Do I need to rename the directory, the name in model.json or both?

@bramstroker

Copy link
Copy Markdown
Owner

Only the directory name, the name is fine as is, and it only uses for displaying purposes.
The model id (directory name) is also used to match against HA device info for discovery.

@jdambacher

Copy link
Copy Markdown
Contributor Author

@bramstroker Thanks for clarification on that. I didn't think about the directory name for matching the correct device. Changed!

@bramstroker bramstroker merged commit 5d333d4 into bramstroker:master Jan 11, 2026
6 checks passed
@bramstroker

Copy link
Copy Markdown
Owner

@bramstroker Thanks for clarification on that. I didn't think about the directory name for matching the correct device. Changed!

Thanks. It's merged already.
You can find some more info about the discovery routine here: https://docs.powercalc.nl/library/discovery/.
Have been doing some cleanups on the library lately to get more consistency in model identifiers and naming etc.
But it's a very hard topic as there are so many vendors and so many different naming schemes and inconsistencies.

@Thorsten1982

Thorsten1982 commented Jan 26, 2026

Copy link
Copy Markdown
Contributor

Hello, I also measured the power consumption of my Shelly 1PM Gen4 presence detector over 24 hours. I got an average consumption of 1.7 watts. I'm not sure which value is more accurate, 1.7 watts or 2 watts. Actually, you should also subtract the power consumption of the power supply, since it probably also has a power draw and isn't part of the device. Different power supplies can be used.
Screenshot_20260126-202312

@Thorsten1982

Copy link
Copy Markdown
Contributor

Hello, what is the current status? I was supposed to get in touch because I measured slightly lower values ​​during my test.

@bramstroker

Copy link
Copy Markdown
Owner

Hi @Thorsten1982 I didn't have this on my radar anymore. Thanks for chiming in.
I would suggest to go with your figures as they seem more accurate, and based on average over longer time.
Could you go forward and make a PR to update the current values?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants