I have a question, I’m trying to detect a baby with the fp1 and it’s not working for me…
Any ideas?
What firmware versions do you have on the FP1’s? Version 35 (first one I bought) have issues, it is now in the back of a drawer. The second one with version 36 works 100% as expected. As soon as I can figure out how to update the firmware on the device itself, my old one can be ‘fixed’.
How can I know which firmware I have?
Have a look under Settings | Devices and Services | Devices:
If you click the three dots next to the ‘Reconfigure Device’ and select ‘Manage Clusters’ check the file version:
My other FP1 that is not behaving (and relegated to the back of a drawe)r is firmware version 35 and file version 53… firmware 36 and file version 54 I have no problem with, it is absolutely rock solid.
1 Like
I’m using Ziggbee2mqtt
In zigbee2mqtt run the ota for your fp1. Click in “Check for new updates”
Then check your zigbee2mqtt logs. There are lines like this:
Zigbee2MQTT:debug 2022-09-04 12:10:24: Is new image available for '0x54ef4xxxxxxxxx7d', current '{"fieldControl":1,"manufacturerCode":4447,"imageType":8347,"fileVersion":54}', latest meta '{"fileVersion":54,"fileSize":317658,"url":"https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20220524105221_OTA_lumi.motion.ac01_0.0.0_0054_20220509_EB279B.ota","sha512":"32174d5bc4abbb7295e7619a1684b0a37a9622dfc4cebbc6a39174e18fa3b9bde9b562cbb34e1eb9c61169c0f1f879245d4e452890dfc0645cd22e6ad36f468d"}'
Zigbee2MQTT:debug 2022-09-04 12:10:24: Update available for '0x54ef4xxxxxxxxx7d': NO
Zigbee2MQTT:info 2022-09-04 12:10:24: No update available for '0x54ef4xxxxxxxxx7d'
The
fileVersion":54
is your firmware. You check the latest firmware here:
2 Likes
Excellent, I build a DEV HA install on a spare RPi4 kicking about and installed Zigbee2MQTT and updated the firmware. Then moved the sensor back into LIVE HA, works a treat - thanks. Note that the firmware upgrade too approximately 40-50 minutes.
debug <small>2022-09-04 14:53:33</small>Is new image available for ‘0x54ef44100053d26e’, current ‘{“fieldControl”:1,“manufacturerCode”:4447,“imageType”:8347,“fileVersion”:54}’, latest meta '{“fileVersion”:54,“fileSize”:317658,“url”:“https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20220524105221_OTA_lumi.motion.ac01_0.0.0_0054_20220509_EB279B.ota",“sha512”:"32174d5bc4abbb7295e7619a1684b0a37a9622dfc4cebbc6a39174e18fa3b9bde9b562cbb34e1eb9c61169c0f1f879245d4e452890dfc0645cd22e6ad36f468d”}`
this is what im getting
“fileVersion”:54 shows your firmware version and this is up 2 date atm.
1 Like
Any ideas how to detect a baby?
So I’ve had 7 FP1 sensors lying around here for 3 days now. Everything is connected properly via z2m, the zigbee channel has even been changed to 25, but unfortunately the most frequent state I get is approach.
Also, the presence sensor rarely switches back to false when I leave the room.
I then noticed that the presence_event changes when I press the reset_nopresence_status button.
So I wrote an automation that triggers the reset_nopresence_status every few seconds via mqtt.
Here is the automation:
alias: Mqtt-send-off-fp1
description: ""
trigger:
- platform: time_pattern
seconds: /3
condition: []
action:
- service: mqtt.publish
data:
topic: zigbee2mqtt/0x54eXXXXXXXXXXXXX/set
payload: "{\"reset_nopresence_status\":\"\"}"
mode: single
Now the presence_event is working very well. I can’t use the presence info anymore, but I get much better values back like left_enter or right_leave.
1 Like
How do you go about changing firmware? Any help would be great.
I’m using HA supervised with zig2mqqt. Can’t find the firmware version anywhere pointed above. One of my FP1’s work perfectly, the other one gets stuck with presence detected.
Just got my FP1 and have the same issue.
Did some tests and seems like the FP1 need to detect proper motion before resetting the presence state.
I had my FP1 facing towards the wall with 10cm distance, no change for fans, moving curtains etc.
I gave it a ‘false positive’ by moving it till presence_event is changed to ‘enter’. It detects presence but it doesn’t reset automatically. (Waited 5+ minutes)
When I wave and move my fingers for 3-5 seconds in front of the sensor, it resets the presence after 40 seconds.
Then I wave my hand again, and it triggers presence and resets by it self.
Did this test a few times, it is an constant behavior.
Guess it make a snapshot or something and will only reset if it has proper differences?
Tried to update it over OTA in Z2M but get cluster errors.
Thank you for your solution. At least it makes the FP1 less useless for me.
1 Like
And your results?
I am a bit sad about my results.
Is it time for a github issue for z2m?
Yeah, basically it works as it should. Light switches off when occupancy is empty and event is away for 5 minutes.
But having to make such a workaround is a waste of time. Luckily it’s not battery powered.
Hi
That’s so greaaat.
You’d say that the sensor detect your position under 1 second, what’s it’s possible?
You update the sensor in the last firmware no ?
Thanks for this, now it works for me too. My presence was never reseted and the event as well, this fixes it. Hope they will release a fw-update soon to mitigate this issue.
I would I update using Deconz ? (I am not using HA)