Hi @kkossev. Many thanks for your reply.
I did try to add it the way that you described but unfortunately it did not work. It only worked when I added generic motion sensor. Will keep that in mind for future devices though.
Hi @kkossev. Many thanks for your reply.
I did try to add it the way that you described but unfortunately it did not work. It only worked when I added generic motion sensor. Will keep that in mind for future devices though.
Are you sure that you have Aqara P1 motion sensor? Can you post a screenshot of the device details 'Data' section? (I need to check model/manufacturer and application version).
The only reason that comes to my mind is that the HE inbuilt 'Generic Motion Sensor' driver may be needed if your device uses the IAS zone (Intruder Alarm System), but Aqara P1 are not such type of sensors.
I see that your P1 motion sensor has an older firmware version (05), while mine is application version 0.5
If it works now, and after a hub reboot, and after a hub is switched off for 30 or more minutes -better leave it as it is.
Upgraded from C7 to C8 hub using Hubatit cloud process. Everything went fine except my 5x of my 7x RTCGQ14LM Aqara motion sensors no longer function. Two work as before, but the 2x of the five worked on the C7 hub [3x were new], but not the C8.
Attached log of one of the two that did work before on C7, but does not now work on the C8.
Have the C7 hub running [but did a soft reset] thinking if it is a Zigbee issue, should I move them back to the old hub - assume I will also have to transfer the dimmers / switches they are controlling as I assume I cannot have them on both hubs.
There are a lot of hiccups with various Zigbee devices (not just Aqara) that follow the big internal changes in HE from ZHA 1.2 to Zigbee 3.0 .. If you can, just wait some more time for the system to stabilize. Or check this, which worked for another user.
In all cases, I would not recommend moving everything back to C-7. If you decide to move just the Aqara P1s, you can always use the Hub Mesh and just change the names of the networked sensors on the main C-8 hub.
Thanks for the comment, I’m trying the radio reset.
If that does not work, can you point me to the procedure to use the Hub Mesh and just change the names of the networked sensors on the main C-8 hub?
I have also ordered 2x Sonoff motion sensors to use, but I like the form factor of the Aqara units. Any other motion sensor recommendations?
Update - the Zigbee reboot radio - had no apparent effect; my 5x P1's can be easily added, but drop off after a few hours. Happily [or maddeningly], the 2x P1's who have been online from the initial transfer remain OK thru this mess. Also I have 2x older RTCGQ11LM Aqara motion sensors that also transferred and have been OK thru this change.
See chatter on the community board on Zigbee / C8's, so I think there is an issue with the current configuration and will try and be patient for a fix.
Need to break mu habit of being an early adopter and suffering the consequences ....
There is an even newer HE platform version 2.3.5.112 in beta testing with some good feedback on problems like this one, wait until it is rolled out and try again.
Others report just the opposite - Aqara P1 staying stable connected to C-8 (P1 uses a newer 3.0 Zigbee stack), wile there are problems with the older Aqara sensor... go figure!
Update (2)
With 2.3.5.113, everything seems to be working with all my Aqara P1’s online and functioning. Have even learned the hub mesh system and have both my C7 & C8 linked.
Next challenge will be the Aqara FP1 I just received & setting modes.
When I look in HPM I see that I have V1.2.2 but this thread says it is up to V1.2.4. HPM Update check says this V1.2.2 is current. Am I missing something?
Yes, the current situation with this driver version is a bit messy at the moment... : (
There are 3 versions in use:
Unfortunately, I forgot to increase the version to 1.2.4 in HPM when I merged the latest code at that time... And now, the differences between 1.2.4 and the latest development branch version become too big. Before pushing any automatic updates from HPM, I need to find the time to test how the update will go.
There are potentially breaking changes in the latest version 1.4.1 - the previously misused Presence attribute is now replaced with another custom attribute, synchronized with the roomState/roomActivity attributes names in the new Aqara FP1 driver, that is currently in a beta testing stage. So I think that the best time to push the latest version via HPM will be the time when the new FP1 driver w/ regions support will be published.
If you are using this driver with the P1 motion sensor, any previous driver version should work. However, if any bugs are found or new features are needed - this will be done based on the latest development version.
Thank you for the information. I understand what I am seeing now.
I am on a C8 and have the Aqara P1 it operates correctly for a few hours and then stops working. I tried the same with another Aqara P1 with the same results.
To make sure there is no issue with the Aqara P1 in install it on my Smartthings Hub where it works without any issues.
Aqara drive installed
TODO: Regions
*/
def version() { "1.2.4" }
def timeStamp() {"2023/01/26 7:32 PM"}
My C8 hub is running version: 2.3.5.131
here is the the Hub for the Aqara
current state info
log info
dev:292023-05-04 04:25:39.469 PMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 03:25:39.407 PMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 02:25:39.334 PMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 01:25:39.264 PMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 12:25:39.195 PMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 11:25:39.112 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 10:25:39.053 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 09:25:38.982 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 08:25:38.886 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 07:25:38.786 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 06:25:38.702 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 05:25:38.627 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 04:25:38.539 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 03:25:38.448 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 02:25:38.334 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 01:25:38.244 AMwarnAqara P1 motion #2 Aqara P1 motion #2 forced battery to '0 %
dev:292023-05-04 01:25:38.228 AMwarnAqara P1 motion #2 is not present!
dev:292023-05-04 01:25:38.214 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-04 12:25:38.149 AMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-03 11:25:38.081 PMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-03 10:28:32.259 PMinfoAqara P1 motion #2 Motion reset to inactive after 60 s.
dev:292023-05-03 10:28:02.338 PMinfoAqara P1 motion #2 Motion is active 30s
dev:292023-05-03 10:28:02.208 PMinfoAqara P1 motion #2 illuminance is 44 Lux
dev:292023-05-03 10:28:02.199 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E1201232C000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:0001002C, clusterInt:64704, attrInt:274]
dev:292023-05-03 10:28:02.190 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E1201232C000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 2C000100
dev:292023-05-03 10:27:32.695 PMinfoAqara P1 motion #2 Detected motion
dev:292023-05-03 10:27:32.461 PMinfoAqara P1 motion #2 illuminance is 42 Lux
dev:292023-05-03 10:27:32.443 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E1201232A000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:0001002A, clusterInt:64704, attrInt:274]
dev:292023-05-03 10:27:32.431 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E1201232A000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 2A000100
dev:292023-05-03 10:25:38.018 PMdebugAqara P1 motion #2 pollPresence()
dev:292023-05-03 09:53:20.616 PMinfoAqara P1 motion #2 Motion reset to inactive after 60 s.
dev:292023-05-03 09:52:50.652 PMinfoAqara P1 motion #2 Motion is active 30s
dev:292023-05-03 09:52:50.578 PMinfoAqara P1 motion #2 illuminance is 44 Lux
dev:292023-05-03 09:52:50.571 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E1201232C000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:0001002C, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:52:50.562 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E1201232C000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 2C000100
dev:292023-05-03 09:52:20.888 PMinfoAqara P1 motion #2 Detected motion
dev:292023-05-03 09:52:20.842 PMinfoAqara P1 motion #2 illuminance is 104 Lux
dev:292023-05-03 09:52:20.835 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E12012368000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:00010068, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:52:20.827 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E12012368000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 68000100
dev:292023-05-03 09:52:13.182 PMinfoAqara P1 motion #2 Motion reset to inactive after 30 s.
dev:292023-05-03 09:51:43.199 PMinfoAqara P1 motion #2 Detected motion
dev:292023-05-03 09:51:43.146 PMinfoAqara P1 motion #2 illuminance is 104 Lux
dev:292023-05-03 09:51:43.140 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E12012368000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:00010068, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:51:43.129 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E12012368000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 68000100
dev:292023-05-03 09:51:41.394 PMinfoAqara P1 motion #2 Motion reset to inactive after 30 s.
dev:292023-05-03 09:51:11.427 PMinfoAqara P1 motion #2 Detected motion
dev:292023-05-03 09:51:11.350 PMinfoAqara P1 motion #2 illuminance is 102 Lux
dev:292023-05-03 09:51:11.346 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E12012366000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:00010066, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:51:11.340 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E12012366000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 66000100
dev:292023-05-03 09:51:09.284 PMinfoAqara P1 motion #2 Motion reset to inactive after 60 s.
dev:292023-05-03 09:50:39.312 PMinfoAqara P1 motion #2 Motion is active 30s
dev:292023-05-03 09:50:39.247 PMinfoAqara P1 motion #2 illuminance is 104 Lux
dev:292023-05-03 09:50:39.241 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E12012368000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:00010068, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:50:39.221 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E12012368000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 68000100
dev:292023-05-03 09:50:09.574 PMinfoAqara P1 motion #2 Detected motion
dev:292023-05-03 09:50:09.512 PMinfoAqara P1 motion #2 illuminance is 102 Lux
dev:292023-05-03 09:50:09.506 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E12012366000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:00010066, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:50:09.499 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E12012366000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 66000100
dev:292023-05-03 09:50:09.411 PMinfoAqara P1 motion #2 Motion reset to inactive after 30 s.
dev:292023-05-03 09:49:55.878 PMinfoAqara P1 motion #2 LED is Disabled (0)
dev:292023-05-03 09:49:55.867 PMinfoAqara P1 motion #2 (tag 0x6A) sensitivity is medium (2)
dev:292023-05-03 09:49:55.854 PMinfoAqara P1 motion #2 motion retrigger interval is 30 s.
dev:292023-05-03 09:49:55.817 PMinfoAqara P1 motion #2 illuminance is 106 Lux
dev:292023-05-03 09:49:55.810 PMdebugon/off is 0
dev:292023-05-03 09:49:55.809 PMdebugAqara P1 motion #2 unknown tag=14 dataType 0x20 rawValue=0
dev:292023-05-03 09:49:55.807 PMdebugAqara P1 motion #2 unknown tag=13 dataType 0x20 rawValue=0
dev:292023-05-03 09:49:55.805 PMdebugAqara P1 motion #2 unknown tag=0C dataType 0x20 rawValue=1
dev:292023-05-03 09:49:55.803 PMdebugParent NWK is 974A
dev:292023-05-03 09:49:55.801 PMdebugAqara P1 motion #2 unknown tag=08 dataType 0x21 rawValue=262
dev:292023-05-03 09:49:55.799 PMdebugRSSI is 1 ? db
dev:292023-05-03 09:49:55.797 PMdebugAqara P1 motion #2 unknown tag=04 dataType 0x21 rawValue=0
dev:292023-05-03 09:49:55.779 PMinfoAqara P1 motion #2 Battery level is 100% (3.197 Volts)
dev:292023-05-03 09:49:55.771 PMdebugdecodeAqaraStruct len = 98 valueHex = 3001217D0C0328160421000005210100082106010A214A970C200113200014200064100065216A0069201E6A20026B2000
dev:292023-05-03 09:49:55.762 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC068F700413001217D0C0328160421000005210100082106010A214A970C200113200014200064100065216A0069201E6A20026B2000, dni:B822, endpoint:01, cluster:FCC0, size:68, attrId:00F7, encoding:41, command:0A, value:01217D0C0328160421000005210100082106010A214A970C200113200014200064100065216A0069201E6A20026B2000, clusterInt:64704, attrInt:247]
dev:292023-05-03 09:49:55.754 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC068F700413001217D0C0328160421000005210100082106010A214A970C200113200014200064100065216A0069201E6A20026B2000, dni: B822, endpoint: 01, cluster: FCC0, size: 68, attrId: 00F7, encoding: 41, command: 0A, value: 3001217D0C0328160421000005210100082106010A214A970C200113200014200064100065216A0069201E6A20026B2000
dev:292023-05-03 09:49:39.408 PMinfoAqara P1 motion #2 Detected motion
dev:292023-05-03 09:49:39.369 PMinfoAqara P1 motion #2 illuminance is 105 Lux
dev:292023-05-03 09:49:39.365 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E12012369000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:00010069, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:49:39.355 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E12012369000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 69000100
dev:292023-05-03 09:49:31.559 PMinfoAqara P1 motion #2 Motion reset to inactive after 60 s.
dev:292023-05-03 09:49:01.568 PMinfoAqara P1 motion #2 Motion is active 30s
dev:292023-05-03 09:49:01.522 PMinfoAqara P1 motion #2 illuminance is 106 Lux
dev:292023-05-03 09:49:01.518 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E1201236A000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:0001006A, clusterInt:64704, attrInt:274]
dev:292023-05-03 09:49:01.512 PMdebugAqara P1 motion #2 parse: description is read attr - raw: B82201FCC00E1201236A000100, dni: B822, endpoint: 01, cluster: FCC0, size: 0E, attrId: 0112, encoding: 23, command: 0A, value: 6A000100
dev:292023-05-03 09:48:31.855 PMinfoAqara P1 motion #2 Detected motion
dev:292023-05-03 09:48:31.804 PMinfoAqara P1 motion #2 illuminance is 106 Lux
dev:292023-05-03 09:48:31.791 PMdebugAqara P1 motion #2 parse: Desc Map: [raw:B82201FCC00E1201236A000100, dni:B822, endpoint:01, cluster:FCC0, size:0E, attrId:0112, encoding:23, command:0A, value:0001006A, clusterInt:64704, attrInt:274]
Any ideas?
Thanks
Hi @user5034 ,
Please update to HE platform version 2.3.5.135 and pair the P1 sensor again to your C-8 hub.
After re-pairing, you can search the device live logs for the text "Parent NWK is"
This is the short address of the Zigbee repeating device that P1 is using to connect to the hub. Due to security concerns it is not possible to obtain the device name from a user driver, but you can find what this repeater is by searching for the Parent NWK 4 digits ID. In your case :
Parent NWK is 974A
Go to HE Settings -> Zigbee details and search the web page for 974A.
This is the repeater used by P1 to reach the hub. Make sure this device is operational / online / not switched off.
What model/make is it?
Can't believe it, the P1 has gone offline for the first time on C8 2.3.5.146 (never happened on C7 hub).
dev:15352023-06-16 11:32:50.118 AMinfoAqara P1 ping...
dev:15352023-06-16 11:32:48.248 AMinfoAqara P1 configure...fullInit = false (driver version 1.4.2 2023/05/21 10:48 PM)
dev:15352023-06-16 11:11:48.227 AMinfoAqara P1 ping...
dev:15352023-06-16 10:03:53.878 AMwarnAqara P1 healthStatus changed to offline
dev:15352023-06-16 07:21:32.599 AMinfoAqara P1 Motion reset to inactive after 16 s.
dev:15352023-06-16 07:21:22.634 AMinfoAqara P1 Motion is active 6s
dev:15352023-06-16 07:21:22.571 AMinfoAqara P1 illuminance is 108 Lux
dev:15352023-06-16 07:21:20.698 AMinfoAqara P1 Motion is active 4s
dev:15352023-06-16 07:21:20.584 AMinfoAqara P1 illuminance is 109 Lux
dev:15352023-06-16 07:21:18.610 AMinfoAqara P1 Motion is active 2s
dev:15352023-06-16 07:21:18.558 AMinfoAqara P1 illuminance is 107 Lux
If you press the physical button on the device, will it bring it back to life?
Or you need to pair it again to HE?
I just paired it again.
I did notice that the LED was still blinking when motion was detected but not reflected on software.
As I remember, when just paired the LED will always blink when the motion is detected in the first 5-10 minutes, no matter how the LED option is set. This is the time frame in which the P1 sensor also accepts configuration commands without the need to press the device button at the same time.
If you look at the Zigbee map, is the sensor now connected directly to the hub or via a router?