Add DDF for Aqara FP1 presence sensor RTCZCGQ11LM - #6070
Merged
Conversation
SwoopX
marked this pull request as ready for review
May 23, 2022 20:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds DDF for FP1 presence sensor, depends on #6069 and vice versa.
For this device, the new resource item
config/triggerdistanceis introduced, as it apparently can measure the distance when someone is approaching. Valid values are near, medium and far. Furthermore, it offers true detection sensitivity.Also new is the resource item
config/resetpresence, allowing the presence status to reset when set to true. Obviously, this feature is required as the device gets stuck in its current state every now and then (also officially supported by the Aqara app). Note that it takes around 5 minutes for the value to be automatically set back to false.Although the attribute 0x0142 is seemingly intended for presence detection, it was decided not to go with that as it changes quite laggy. Alternatively, attribute 0x0143 was chosen, also represented by the new resource item
state/presenceeventto react faster and more crisp. Time and users will tell if that choice was good or not. However, presence should be automatically set back to false (when nobody is within detection reach) after about 3 minutes.2 detection modes are supported, exposed via
config/devicemode, unidirected and left and right with the first one as default.There is no support for the region or map feature of the official app as this must be investigated further if and to what extend that can be realized at all. Eventually, there will be a future update on the read and parse functions to leverage the special reporting if found appropriate, but this shouldn't have any notable impact.