Awesome, thanks for clarifying.
1 Like
My Aqara app is showing a firmware update is available for 1 of my FP2s. I knew this was coming as Iād seen something in the tech news about a new sleep monitoring function for FP2s used in bedroom settings. The app is showing the firmware update (from 1.2.2_0002.0056 to 1.2.3_0002.0059) is currently available for our kitchen FP2 so Iām reluctant to update for 2 reasons:
- We donāt sleep in the kitchen, but perhaps more importantly
- My FP2s have been rock solid since the last firmware update and we all know what might happen with this one.
So, is anyone else seeing this update is available for their devices and has anyone implemented the update?
1 Like
No update showing for the uk, still .0056
Er, Iām in the UK!
Just this minute checked again and its not made it to Bristol.
The firmware update has now disappeared from the app 
Iām glad I didnāt update it.
1 Like
I came across this and thought i share.
The new firmware update just appeared for me after todayās Aqara app update, and I applied it. It came with the following notes:
Latest firmware version:1.2.3_0002.0059
Update Log:
- Added Sleep Monitoring Mode, requiring FP2 repositioning and reinstallation.
- Improved Detection Precision and Stability: Enhanced accuracy and resolved known issues.
This enables an additional detection mode called Sleep Monitoring which says ālimited freeā, implying that the new capabilities might end up having additional costs.
Thatās not a good sign.
1 Like
Can you rotate the room map now so that the sensor is placed in a corner?
I donāt see such a capability.
While checking, I found that between yesterday and today they have released a new firmware update: 1.2.3_0005.0066. The release notes are unchanged.
I hate that they obviously work on features, which were not even announced (if I remember correctly), but those promised are still not implementedā¦
Hi all,
Iām currently facing challenges with the integration of my Aqara FP2 sensor into Home Assistant. The primary issue is intermittent connectivity, which is evident from ping timeouts. Iām reaching out for advice or solutions from anyone who might have encountered and resolved similar issues.
Here are the details:
- Device: Aqara FP2 sensor
- Firmware Version: .0066 (latest)
- Network Setup: Static IP assigned to the sensor
- Problem: Intermittent connectivity (ping timeouts)
- Ping Results:
PING 192.168.0.131 (192.168.0.131): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 192.168.0.131: icmp_seq=4 ttl=255 time=44.329 ms
Request timeout for icmp_seq 5
...
(Additional results showing intermittent responses and timeouts)
Steps Iāve already taken:
- Ensured network stability and sensor range.
- Restarted both the sensor and my Wi-Fi router.
- Checked and confirmed the Home Assistant configuration for the sensor.
- Assigned a static IP to the sensor.
Despite these efforts, the connectivity issue persists. Iām currently on the latest firmware version (.0066), but the problem remains unresolved. Has anyone in the community experienced similar issues with the Aqara FP2 sensor, especially with this firmware version and a static IP setup? Any insights, suggestions, or troubleshooting tips would be greatly appreciated.
What 2.4GHz WiFi channel is your router using? Disable any āautomaticā 2.4GHz Channel Optimization that your WiFi router might be attempting. I would recommend using WiFi 2.4GHz channel 1, 6, or 11 on your router, with a 20MHz channel width. If you love in a congested area (e.g. an apartment complex) then you may want to look and see which of those three WiFi 2.4GHz channels have the least congestion.
This configuration will also work best if you use any Zigbee devices at your house. Zigbee channels 15, 20, and 25 are ideal as they do not conflict with the 2.4GHz WiFi channels I listed above, as long as the 2.4GHz channel width is kept to 20MHz.
2 Likes
Hi @ogiewon,
Thank you for the recommendation. I have updated the router and
~ % ping 192.168.0.131
PING 192.168.0.131 (192.168.0.131): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 192.168.0.131: icmp_seq=2 ttl=255 time=107.692 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 192.168.0.131: icmp_seq=5 ttl=255 time=50.133 ms
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
^C
pinged the FP2. Can you please advise on what else I can do to resolve the issue? Thank you in advance!
What type of power supply are you using for your FP2? Perhaps the one youāre using is slightly underpowered? Just another hypothesisā¦
@ogiewon ,
please have a look at the picture. Also, FP2 continuously is flashing from yellow to blue color :(.
Ty!
If you have a different power supply, preferably one that can output more than 1W, you may want to give that a try.
As for the LED lightsā¦ looks like the FP2 is struggling to connect and stay connected to your WiFi router. Have you tried moving the FP2 much closer to the WiFi router, to see if distance between the two devices may be a contributing factor?
