[New device support]: Aqara Presence Detector FP1 (RTCZCGQ11LM; lumi.motion.ac01)

[Otnow]

Link

https://www.aqara.com/cn/productDetail/Aqara-Presence-Detector-FP1

Database entry

{"id":2,"type":"EndDevice","ieeeAddr":"0x54ef44100042d6eb","nwkAddr":13551,"manufId":4660,"manufName":"aqara","powerSource":"DC Source","modelId":"lumi.motion.ac01","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":65520,"inClusterList":[0,3,64704],"outClusterList":[3,25],"clusters":{"genBasic":{"attributes":{"modelId":"lumi.motion.ac01","manufacturerName":"aqara","powerSource":4,"zclVersion":3,"appVersion":48,"stackVersion":2,"hwVersion":1,"dateCode":"20210121","swBuildId":""}},"aqaraOpple":{"attributes":{"247":{"type":"Buffer","data":[3,40,28,5,33,1,0,8,33,48,1,10,33,0,0,12,32,20,16,32,1,18,32,0,101,32,1,102,32,6,103,32,0,104,32,0,105,32,1,106,32,1,107,32,3]},"322":1}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":48,"stackVersion":2,"hwVersion":1,"dateCode":"20210121","swBuildId":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1643135963340,"useImplicitCheckin":true}

Comments

Review:

• appearance and equipment (photos)
• Aqara Home app (screenshots)
• disassembly (photos)
• first acquaintance (video)

Buy:

• https://aliexpress.com/item/1005003772245093.html
• https://aliexpress.com/item/1005003781853869.html
• https://aliexpress.com/item/1005003766378575.html

External converter

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const ota = require('zigbee-herdsman-converters/lib/ota');
const e = exposes.presets;
const ea = exposes.access;

const definition = {
    zigbeeModel: ['lumi.motion.ac01'],
    model: 'RTCZCGQ11LM',
    vendor: 'Xiaomi',
    description: 'Aqara Presence Detector FP1',
    fromZigbee: [],
    toZigbee: [],
    exposes: [],
    ota: ota.zigbeeOTA,
};

module.exports = definition;

[z-x-f]

Wow, you got this new device so fast, I ordered it here and it hasn't arrived yet.

[Otnow]

Wow, you got this new device so fast, I ordered it here and it hasn't arrived yet.

Yes, lucky with the speed this time 🙂

It's good that it's coming to you too, so I hope we (and maybe someone else) will add support for it together, because I can hardly do it alone 🤝

A quick inspection of the exchange protocol again shows the abundant use of Aqara proprietary octet string 🤦‍♂️

[Koenkk]

Added in https://github.com/Koenkk/zigbee2mqtt/issues/11019

[Otnow]

Only the basic functionality of the sensor is presented here, and we still have to work to add a very interesting function for working with regions:

[rdorys]

Hi @Otnow , do you know if the sensor can handle two people or more? Is there one point per people on the map ?

And what about pets? Can it detect it and see it's not human ?

Thx for your work

[Otnow]

Hi @Otnow , do you know if the sensor can handle two people or more? Is there one point per people on the map ?

And what about pets? Can it detect it and see it's not human ?

Thx for your work

Hi. I have not yet figured out the logic of this sensor well enough, so I can’t say for sure right now.

I did not check with several people, but judging by this video review, the sensor displays only 1 person on the map (this is only the first information so far, we will find out more accurately later).

I don't have pets, but it seems to me that the sensor will notice their movement, because. it seems that he reacts to everything that even slightly changes position in space (for example, a very slight swaying of a curtain). Will he be able to understand that this is not a person, I don’t know, but I doubt it.

The sensor has a very peculiar logic of operation, so in the process of adding the function of working with regions, I hope to understand it better.

[qvntra]

Subscribed. Very interested to see the progress here.

[Inrego]

Where can we track progress/discussion of more advanced features?

[Otnow]

Where can we track progress/discussion of more advanced features?

You can discuss here, so write if you have additional information or questions.

[piggydamn]

it cant join z2m,the log:

warn 2022-03-06 10:18:59: permit_join set to true in configuration.yaml. warn 2022-03-06 10:18:59: Allowing new devices to join. warn 2022-03-06 10:18:59: Set permit_join to false once you joined all devices. warn 2022-03-06 10:19:00: Using experimental new availability feature warn 2022-03-06 10:21:21: Device '0x54ef441000473044' with Zigbee model 'lumi.motion.ac01' and manufacturer name 'aqara' is NOT supported, please follow https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html warn 2022-03-06 10:21:22: Received message from unsupported device with Zigbee model 'lumi.motion.ac01' and manufacturer name 'aqara' warn 2022-03-06 10:21:22: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

[z-x-f]

I didn't receive my FP1 until today. Unfortunately, I tried many times, FP1 doesn't seem to support ZigBee 22 channel, changing channel seems to require repairing all devices, there are more than 40 devices in my ZigBee network, changing channel will be a very troublesome thing...

[Otnow]

Unfortunately, I tried many times, FP1 doesn't seem to support ZigBee 22 channel

Just checked, indeed the sensor does not want to work on channel 22.

[Otnow]

RTCZCGQ11LM converter changed for support new functionality in firmware №53: motion_sensitivity and reset_nopresence_status (is now available in the dev branch, and will appear in the master branch at the beginning of next month):

_Important: before updating the sensor firmware to version 53, you must install a zigbee2mqtt version that supports this firmware version, otherwise presence_event will report incorrect data due to the changed logic of the firmware._

[jeezy51]

hello, what progress has been made regarding the integration of the regions? There is an integrated Tuya occupancy sensor on Zigbee2mqtt and the regions are well integrated, the regions on the tuya sensors are so different from the FP1 sensors?

[jeezy51]

Tuya sensor région

[Otnow]

hello, what progress has been made regarding the integration of the regions? There is an integrated Tuya occupancy sensor on Zigbee2mqtt and the regions are well integrated, the regions on the tuya sensors are so different from the FP1 sensors?

At the moment, there is no support for regions and, unfortunately, integration of Tuya sensor will not help in any way, because Aqara has a completely different logic of work.

[jeezy51]

Ok I understand, I wondered if the functioning of the tuya region and the FP1 region were the same or different. thank you for the details, good luck with the integration.

[jeezy51]

what is the logic of the sensor, is it digital data based on X (bottom left) and Y (top right) coordinates like Roborock vacuum cleaners? Data according to the number of boxes (4X7) Or data based on the coupling of approach distance and direction of travel? Do you currently know the key related to the information of the regions? because in debug I see 6 keys which are unknown and if I manage to know the digital info of the region I can process it via my home automation server.

[jeezy51]

if I understood correctly, the region information is indeed uploaded in Zigbee2mqtt but you don't know how to interpret it, is that right?

[Otnow]

@jeezy51, I'm not currently developing region support due to other priorities, so I can't answer your questions 🤷

[jayden-jw]

I'm not sure is my unit still with the old firmware but the sensitivity and resetting nobody is not available. I try to send a message to do OTA firmware check but return available: false.

[Otnow]

I'm not sure is my unit still with the old firmware but the sensitivity and resetting nobody is not available. I try to send a message to do OTA firmware check but return available: false.

First, I think you need to update zigbee2mqtt to the current version (1.25.2).

What version do you have installed?

[jayden-jw]

I'm not sure is my unit still with the old firmware but the sensitivity and resetting nobody is not available. I try to send a message to do OTA firmware check but return available: false.

First, I think you need to update zigbee2mqtt to the current version (1.25.2).

What version do you have installed?

Thanks for the tips, I didn't know since when all my add-on repositories are gone, so I didn't see any new update on zigbee2mqtt, now I have added back and upgraded to the latest version, everything working except the temperature always at 40c.

[Otnow]

Thanks for the tips, I didn't know since when all my add-on repositories are gone, so I didn't see any new update on zigbee2mqtt, now I have added back and upgraded to the latest version, everything working except the temperature always at 40c.

Do you mean device_temperature?

[mihsu81]

I'm having the same issue. Both devices have firmware build date 20210121, and can't find an update available. Z2MQTT is the latest version 1.25.2. Am I missing something in my config?

Thanks in advance.

[mihsu81]

In the logs I can see:

Debug 2022-06-08 20:15:46Got OTA request '{"fieldControl":1,"manufacturerCode":4447,"imageType":8347,"fileVersion":53}'
Debug 2022-06-08 20:15:46ZigbeeOTA: downloaded main index
Debug 2022-06-08 20:15:46Is new image available for '0x54ef4410004d9819', current '{"fieldControl":1,"manufacturerCode":4447,"imageType":8347,"fileVersion":53}', latest meta '{"fileVersion":53,"fileSize":317370,"url":"https://github.com/Koenkk/zigbee-OTA/raw/master/images/Xiaomi/20220124174454_OTA_lumi.motion.ac01_0.0.0_0053_20220124_93246C.ota","sha512":"2d7c7c0d3f3e58dbe2fd5a14224fb7bfcfa51c0763b9d7c3ff3203ab1b8b9ea832b1d619480e660c41d26d9860fbf27ad469670a4b2da424bf929f5f17577e25"}'
Debug 2022-06-08 20:15:46Update available for '0x54ef4410004d9819': NO
Info 2022-06-08 20:15:46No update available for 'MASTER-BEDROOM-PRESENCE'
Info 2022-06-08 20:15:46MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"No update available for 'MASTER-BEDROOM-PRESENCE'","meta":{"device":"MASTER-BEDROOM-PRESENCE","status":"not_available"},"type":"ota_update"}'

It's as if it is not recognized as a newer firmware.

[Otnow]

I'm having the same issue.

Please clarify what exactly is not working?

It's as if it is not recognized as a newer firmware.

You have the latest sensor firmware installed (v.53), so there is no update:

current '{"fieldControl":1,"manufacturerCode":4447,"imageType":8347,"fileVersion":53}' latest meta '{"fileVersion":53,"fileSize":317370,"url": ... }'

[mihsu81]

@Otnow How can it be the same when the firmware build date on my devices is "20210121" and the build date of the ota file is "20220124".

[Otnow]

How can it be the same when the firmware build date on my devices is "20210121" and the build date of the ota file is "20220124".

You need to ask Aqara why they did not update the build date in the latest firmware 🤷‍♂️🙃

[mihsu81]

How can it be the same when the firmware build date on my devices is "20210121" and the build date of the ota file is "20220124".

You need to ask Aqara why they did not update the build date in the latest firmware 🤷‍♂️🙃

My apologies then. I was under the impression that there is a bug not allowing the update. Thanks for your help and for taking your time to explain. 🙂

[mvgijssel]

Does anyone know if it's possible to configure the regions of the Aqara FP1 with the Aqara Hub and move the FP1 with those settings into zigbee2mqtt? I don't have high hopes as you have to reset the device to pair with another controller 🙈, but contemplating getting an Aqara Hub just for being to configure regions in these sensors (as they are really awesome 😍).

[Otnow]

Does anyone know if it's possible to configure the regions of the Aqara FP1 with the Aqara Hub and move the FP1 with those settings into zigbee2mqtt?I don't have high hopes as you have to reset the device to pair with another controller 🙈, but contemplating getting an Aqara Hub just for being to configure regions in these sensors (as they are really awesome 😍).

No, unfortunately this will not work, because I checked this possibility and after re-pairing the sensor resets all settings (including regions).

[jeezy51]

Does anyone know if it's possible to configure the regions of the Aqara FP1 with the Aqara Hub and move the FP1 with those settings into zigbee2mqtt? I don't have high hopes as you have to reset the device to pair with another controller 🙈, but contemplating getting an Aqara Hub just for being to configure regions in these sensors (as they are really awesome 😍). Yes it's possible on Home assistant look this post https://post.m.smzdm.com/p/axlqrmkw/

[Otnow]

Yes it's possible on Home assistant look this post https://post.m.smzdm.com/p/axlqrmkw/

The question was about z2m, but as a workaround, the option you proposed is also possible, assuming that HA is used as a smart home control system.

[ScarletSeven]

Anyone has an issue with this presence sensor not clearing presence state sometimes? It's just stuck until I hit the "reset_nopresence_status" button in Z2M

[Otnow]

Anyone has an issue with this presence sensor not clearing presence state sometimes? It's just stuck until I hit the "reset_nopresence_status" button in Z2M

Unfortunately, yes, rarely, but it happens. I think this button was provided for this situation.

I hope that this problem, as well as the low speed of the start of presence detection, will be fixed in the new firmware.

[Otnow]

@ScarletSeven, by the way, a new firmware version (№ 54) has just been released, so you can update the sensor in z2m on the OTA tab and check if the problem you indicated has been fixed.

[ScarletSeven]

Wow nice thanks, can’t wait to try updating.

I noticed that the presence sensor sometimes glitched when a person comes in and out at the edge of the detection range relatively quickly, that’s when the presence sensor gets stuck and doesn’t clear its status

Regards, Jonathan

Adscelerate.com

On 17 Jun 2022, at 4:42 AM, Otnow @.***> wrote:

 @ScarletSeven, by the way, a new firmware version (№ 54) has just been released, so you can update the sensor in z2m on the OTA tab and check if the problem you indicated has been fixed.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[lst3245]

Anyone has an issue with this presence sensor not clearing presence state sometimes? It's just stuck until I hit the "reset_nopresence_status" button in Z2M

I just experienced the same issue and searching online came across this issue. While I didn't find a solution, I think that I found out how is this reproduced (not 100% sure though).

My sensor is working perfectly fine at far approach distance and high sensitivity before. But yesterday it consistently failed as it stuck at the "approach" and "presence" state, not sometimes, but actually 7-8 out of 10 times. Originally I was running the stock firmware and tried upgrading it (the one Otnow mentioned), and it didn't make any difference for me.

After thinking a lot, I noticed that in my area it is getting much windier, and I have some hanging clothes within the detection area of the sensor. Indeed, after I closed my windows, my sensor started detecting "leave" and "no presence" again. So my hypothesis is like this: When there are interfering objects like moving clothes/curtain, or a fan, the sensor normally won't trigger by those objects alone, but if a human triggers the sensor and leave, the sensor sometimes detects those interfering objects as human, and hence stuck at "presence" state.

I went further to test this: 1) I put a fan in front of the sensor 2) Turned it on remotely, indeed the sensor was not triggered by it 3) I walked in front of the sensor and triggered it, and then leave 4) The sensor was stuck at "presence" 5) Turned off the fan remotely and after a while, the sensor went back to "leave"/"no presence"

So my temporary solution is to set the motion sensitivity to low, which seemed to be helping. But I don't think the approach distance setting will help as it doesn't affect presence detection, but just "how close to the sensor is regarded as approach or away". I wonder if others can reproduce the problem as mentioned. Removing possible interfering objects could help. Also, I don't have the aqara hub in hand, so if you got one, you could see if the official app detects those interfering objects.

[mvgijssel]

Seems folks from deconz have figured out some of the region/area logic of the Aqara FP1! https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5928#issuecomment-1166545226

[Otnow]

Seems folks from deconz have figured out some of the region/area logic of the Aqara FP1! dresden-elektronik/deconz-rest-plugin#5928 (comment)

Yes, this is my comment 🙂

It remains to understand how to add this logic to z2m 🤔

[cook1emr]

hello, what progress has been made regarding the integration of the regions? There is an integrated Tuya occupancy sensor on Zigbee2mqtt and the regions are well integrated, the regions on the tuya sensors are so different from the FP1 sensors?

Which tuya sensor are you talking of? Am I misunderstanding what regions are. I think regions is the device is capable of seeing where I am in a room. I cant see any documents that show any tuya occupancy sensor is capable of this.

[MattL0]

Maybe this one : https://www.aliexpress.com/item/1005004383504894.html?spm=a2g0o.productlist.0.0.438145c4wv5LoU&algo_pvid=d969472a-0625-4398-a686-5be61abdf95e&algo_exp_id=d969472a-0625-4398-a686-5be61abdf95e-3&pdp_ext_f=%7B%22sku_id%22%3A%2212000028986203299%22%7D&pdp_npi=2%40dis%21CAD%21%2146.95%21%21%21%21%21%402101e9d516577663982885374e19c7%2112000028986203299%21sea

or this

https://www.aliexpress.com/item/1005004509845480.html?spm=a2g0o.productlist.0.0.438145c4wv5LoU&algo_pvid=d969472a-0625-4398-a686-5be61abdf95e&algo_exp_id=d969472a-0625-4398-a686-5be61abdf95e-16&pdp_ext_f=%7B%22sku_id%22%3A%2212000029417342788%22%7D&pdp_npi=2%40dis%21CAD%21%2137.25%21%21%212.81%21%21%402101e9d516577663982885374e19c7%2112000029417342788%21sea

[jeezy51]

hello, what progress has been made regarding the integration of the regions? There is an integrated Tuya occupancy sensor on Zigbee2mqtt and the regions are well integrated, the regions on the tuya sensors are so different from the FP1 sensors?

Which tuya sensor are you talking of? Am I misunderstanding what regions are. I think regions is the device is capable of seeing where I am in a room. I cant see any documents that show any tuya occupancy sensor is capable of this.

I speak well of the zones, the tuya sensor manages them on zigbee2mqtt, it also manages the fall detection

https://fr.aliexpress.com/item/1005003461158730.html?spm=a2g0o.productlist.0.0.65ab22f6I9ow3l&algo_pvid=c75bc94c-4c47-4a0c-a7aa-8a96bdded761&algo_exp_id=c75bc94c-4c47-4a0c-a7aa-8a96bdded761-1&pdp_ext_f=%7B%22sku_id%22%3A%2212000025891550789%22%7D&pdp_npi=2%40dis%21EUR%21%21116.87%21%21%21%21%21%402100bdf016581851635038352e6f7b%2112000025891550789%21sea

[cook1emr]

hello, what progress has been made regarding the integration of the regions? There is an integrated Tuya occupancy sensor on Zigbee2mqtt and the regions are well integrated, the regions on the tuya sensors are so different from the FP1 sensors?

Which tuya sensor are you talking of? Am I misunderstanding what regions are. I think regions is the device is capable of seeing where I am in a room. I cant see any documents that show any tuya occupancy sensor is capable of this.

I speak well of the zones, the tuya sensor manages them on zigbee2mqtt, it also manages the fall detection

https://fr.aliexpress.com/item/1005003461158730.html?spm=a2g0o.productlist.0.0.65ab22f6I9ow3l&algo_pvid=c75bc94c-4c47-4a0c-a7aa-8a96bdded761&algo_exp_id=c75bc94c-4c47-4a0c-a7aa-8a96bdded761-1&pdp_ext_f=%7B%22sku_id%22%3A%2212000025891550789%22%7D&pdp_npi=2%40dis%21EUR%21%21116.87%21%21%21%21%21%402100bdf016581851635038352e6f7b%2112000025891550789%21sea

is this what "area" is doing? on the MIR-HE200-TY_fall. I.E can you set a zone on a map for instance and it knows if you walk into that zone? sorry looking to buy one of these but documentation is hard to come by.

Edit: purchased one of these 100% does not have regions. It has scenes for different rooms that change detection sensitivities.

[mvgijssel]

This person https://percy10442.pixnet.net/blog/post/563851354-aqara-fp1-人體存在傳感器整合入home-assistant使用 integrated the FP1 into home assistant using the Aqara gateway integration. The article describes how the different regions and their states are represented by numerical values.

Thought that this might help figuring out how to integrate this into Z2M!

[Otnow]

@mvgijssel, thanks, the logic is already known: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5928#issuecomment-1166545226

[Almaz58]

Hello. There is a sonoff dongle plus stick (version 20220219), Zigbee2MQTT (1.26.0) and aqara fp1 device (made in June 2022). Zigbee2MQTT cannot detect the device in any way, writes that it is not supported. Tried everything:

1. Installed different versions of sonoff dongle plus, deleted data (erase).
2. Reinstalled Zigbee2MQT several times, cleared the folder, tried the EDGE version. I did everything with a reboot.
3. Changed channels.
4. Changed chargers for Aqara FP1. In general, I tried everything that is possible. The logs say: ... 2022-07-26T11:52:57.513Z zigbee-herdsman:controller:device:log Interview - node descriptor request failed for '0x54ef44100051847e', attempt 5 2022-07-26T11:52:57.514Z zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - nodeDescReq - {"dstaddr":5164,"nwkaddrofinterest":5164} 2022-07-26T11:52:57.514Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,2,44,20,44,20,35] 2022-07-26T11:52:57.520Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,2,0,102] 2022-07-26T11:52:57.521Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,2,0,102] 2022-07-26T11:52:57.521Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 2 - [0] - 102 2022-07-26T11:52:57.522Z zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - nodeDescReq - {"status":0} 2022-07-26T11:52:57.523Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] 2022-07-26T11:53:07.525Z zigbee-herdsman:adapter:zStack:adapter Node descriptor request for '5164' failed (Error: AREQ - ZDO - nodeDescRsp after 10000ms), retry 2022-07-26T11:53:07.525Z zigbee-herdsman:adapter:zStack:adapter Discovering route to 5164 2022-07-26T11:53:07.526Z zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - extRouteDisc - {"dstAddr":5164,"options":0,"radius":30} 2022-07-26T11:53:07.526Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,69,44,20,0,30,66] 2022-07-26T11:53:07.537Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,69,0,33] 2022-07-26T11:53:07.537Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,69,0,33] 2022-07-26T11:53:07.537Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 69 - [0] - 33 2022-07-26T11:53:07.538Z zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - extRouteDisc - {"status":0} 2022-07-26T11:53:07.538Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] 2022-07-26T11:53:10.540Z zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - nodeDescReq - {"dstaddr":5164,"nwkaddrofinterest":5164} 2022-07-26T11:53:10.541Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,2,44,20,44,20,35] 2022-07-26T11:53:10.547Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,2,0,102] 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,2,0,102] 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 2 - [0] - 102 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - nodeDescReq - {"status":0} 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] 2022-07-26T11:53:20.550Z zigbee-herdsman:controller:device:log Interview - quirks check for 'undefined'-'undefined'-'Unknown' 2022-07-26T11:53:20.552Z zigbee-herdsman:controller:device:log Interview - quirks did not match 2022-07-26T11:53:20.552Z zigbee-herdsman:controller:device:log Interview - node descriptor request failed for '0x54ef44100051847e', attempt 6 ...

[Almaz58]

Hello. There is a sonoff dongle plus stick (version 20220219), Zigbee2MQTT (1.26.0) and aqara fp1 device (made in June 2022). Zigbee2MQTT cannot detect the device in any way, writes that it is not supported. Tried everything:

1. Installed different versions of sonoff dongle plus, deleted data (erase).
2. Reinstalled Zigbee2MQT several times, cleared the folder, tried the EDGE version. I did everything with a reboot.
3. Changed channels.
4. Changed chargers for Aqara FP1. In general, I tried everything that is possible. The logs say: ... 2022-07-26T11:52:57.513Z zigbee-herdsman:controller:device:log Interview - node descriptor request failed for '0x54ef44100051847e', attempt 5 2022-07-26T11:52:57.514Z zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - nodeDescReq - {"dstaddr":5164,"nwkaddrofinterest":5164} 2022-07-26T11:52:57.514Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,2,44,20,44,20,35] 2022-07-26T11:52:57.520Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,2,0,102] 2022-07-26T11:52:57.521Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,2,0,102] 2022-07-26T11:52:57.521Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 2 - [0] - 102 2022-07-26T11:52:57.522Z zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - nodeDescReq - {"status":0} 2022-07-26T11:52:57.523Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] 2022-07-26T11:53:07.525Z zigbee-herdsman:adapter:zStack:adapter Node descriptor request for '5164' failed (Error: AREQ - ZDO - nodeDescRsp after 10000ms), retry 2022-07-26T11:53:07.525Z zigbee-herdsman:adapter:zStack:adapter Discovering route to 5164 2022-07-26T11:53:07.526Z zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - extRouteDisc - {"dstAddr":5164,"options":0,"radius":30} 2022-07-26T11:53:07.526Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,69,44,20,0,30,66] 2022-07-26T11:53:07.537Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,69,0,33] 2022-07-26T11:53:07.537Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,69,0,33] 2022-07-26T11:53:07.537Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 69 - [0] - 33 2022-07-26T11:53:07.538Z zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - extRouteDisc - {"status":0} 2022-07-26T11:53:07.538Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] 2022-07-26T11:53:10.540Z zigbee-herdsman:adapter:zStack:znp:SREQ --> ZDO - nodeDescReq - {"dstaddr":5164,"nwkaddrofinterest":5164} 2022-07-26T11:53:10.541Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,4,37,2,44,20,44,20,35] 2022-07-26T11:53:10.547Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [254,1,101,2,0,102] 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [254,1,101,2,0,102] 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:unpi:parser --> parsed 1 - 3 - 5 - 2 - [0] - 102 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:znp:SRSP <-- ZDO - nodeDescReq - {"status":0} 2022-07-26T11:53:10.548Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [] 2022-07-26T11:53:20.550Z zigbee-herdsman:controller:device:log Interview - quirks check for 'undefined'-'undefined'-'Unknown' 2022-07-26T11:53:20.552Z zigbee-herdsman:controller:device:log Interview - quirks did not match 2022-07-26T11:53:20.552Z zigbee-herdsman:controller:device:log Interview - node descriptor request failed for '0x54ef44100051847e', attempt 6 ...

Problem solved. You have to press the button for 10 seconds. (until it starts flashing). Then turn on the search in z2m. Then press the button again until it starts flashing (about 5 seconds).

[Romario1972]

Hello! I've just received my new one FP1 and trying to add it to my HA Z2M add-on. But it joined as "Unsupported". I have in my logs:

Warning Received message from unsupported device with Zigbee model 'lumi.motion.ac01' and manufacturer name 'LUMI'
Warning Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html. 

But it should connect without any external converters. Zigbee2mqtt: Current version: 1.18.1-1 Zigbee module: ZigStar LAN Gateway (RF-STAR RF-BM-2652P)(CC2652P)

What should I do next?