Today I received the new fp300 sensors, yay! I couldn’t wait to get these in my hands. I m happy with the first results. I do have some feedback that I would like to share:
I am running firmware 0.0.0_5234 using the Zigbee protocol through a M3 hub with firmware 4.5.20_0019. I am using the iOS Aqara app v. 6.0.4.
I have turned off the temperature/humidity sensor as well as the illumination sensor, and yet I see these values in HomeKit and when exposing over Matter through my M3 hub (in Home Assistant)
Is there a way to disable them also in HomeKit and over Matter? How do I know whether the battery saves power with 30%?
When I tried to configure the detection range in the configuration settings, I was standing in the middle of a room, 1 meter away and in front of the sensor, and yet the ‘current location’ does was not within the range but outside. Proper optimalisation of the settings can therefore not be done.
The ‘Turn off indicator lights’ settings are confusing. You enable the setting to turn off the lights at certain times. With that you would expect that if this setting is disabled, the indicator lights would always be on. And yet it shows as ‘always off’ when the switch is disabled. I would simplify it by saying if the switch is enabled, the indicator light will be on.
In Home Assistant, where my sensor is exposed over matter through the m3 hub), the motion sensor does not see t0 be exposed. I cannot create any automation based on motion. Instead, they seem to be identify configurations:
I recommend plugging your phone into a charger the battery looks very low
I think you set everything up correct and are simply seeing how different software from different companies handle or see the FP300 sensor
Reading your post I am under the impression that maybe you are experiencing a translation issue in the wording used.
For example in 5. There is no “Motion” sensor because it’s actually an “Occupancy” sensor and it shows clear at the screen shot moment.
In example #3 I think you are experiencing the same sort of translation issue
In example #1 that is normal, HomeKit and Home Assistant see those features even though they are disabled in the Aqara app. Aqara I don’t think has any say in those examples, that would be an Apple HomeKit feature and Home Assistant software feature. Aqara is not able to tell Apple nor Nabu Casa or the Open Home Foundation how to interpret software features.
Thank you for clearing up several points. I agree on the translation issues in 3.
Regarding 1. I understand that Aqara can’t control how other platform interprete software features. Yet I would expect that if they are disabled in the Aqara app, they simply would not be exposed over HomeKit and/or Matter. I did discover by now that the values are not updated. So the entities are exposed but simply not updated.
The reason why I mention 5, is that in the Aqara app you can create an automation based on motion OR occupancy. The motion detection is much faster than occupancy, (which makes sense). Therefore, I had hoped the motion detection was also exposed over matter.
Yeah good idea. I did this workaround for several other sensors I found that the signal is not reliable. it is not always triggered when the logs of the sensor show it should have.
