Software Update breaking the P100

Aqara updated the way the P100 “provides” its sensors via Matter and HomeKit.

Recently, I updated my Aqara Hub M3 to the newest software (stable release).
Today, I wanted to give my P100 a new place to live and had to change the name and entities in Home Assistant for the new usage.

Every old entity in Home Assistant is now no longer available. Apple Home also doesn’t know something about the device. The old entities are gone and the new… Home Assistant adds them… Apple Home adds them as ‘brand-new’ sensors.

This also means, that your Automations may not work.
(Automations in Aqara Home will still work perfectly fine).

If you were using the P100 as Door/Window sensor, you get a new ‘Contact Sensor’/‘Door’ Entity.

  • the battery state, battery type, identify, …

The biggest change (for me):

If you were using the P100 with Object Monitoring (like Vibration or triple-tap detection,…), you now no longer need to deal with these ‘button’ Entities. They got replaced with classic sensors (in Home Assistant a classic ‘binary_sensor’ and in HomeKit a motion sensor).

Unfortunately, the ‘new’ sensors didn’t work and don’t show any changes. So for now, the P100 is useless in other Smart Home Systems then Aqara Home.
Hopefully, Aqara fixes it as soon as possible.

3 Likes

Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.

If other members have any suggestions or insights on this topic, feel free to share!

1 Like

Thanks for the heads-up! Good to know, II think I’ll just stick with MQTT for now, even though I actually wanted to switch over.

I haven’t actually tested the object mode myself yet, but according to the Zigbee2MQTT documentation (Aqara DWZTCGQ11LM control via MQTT | Zigbee2MQTT), it should work without any issues.

By the way, this is what it looks like in Home Assistant:

I hope your problems get fixed soon!

2 Likes

Switching from MQTT to ZHA? or am I understanding it wrong?

Hope Aqara fixes it soon…

I don’t use anything with MQTT so I don’t want to configure it just for one device. But the Automations for the object monitoring luckily run on the M3 Hub.
So it’s not a real problem currently.

And the door sensor works fine.

@JohnD Trotzdem danke dir immer für die Mühe :slight_smile:

2 Likes

No, I meant the switch to the Aqara Hub. Actually, I have all my Aqara devices paired to Aqara hubs via Zigbee and connected to Home Assistant via a Matter bridge. I think that is generally the best and most convenient way to do it. But the P100 wasn’t supported by the hubs I have right from the start, which is why I integrated it via MQTT. If I remember correctly, ZHA wasn’t an option due to a lack of support. And I really only bought the Zigbee/Z-Wave stick for Z-Wave Long Range, because I wanted to place a sensor in the basement. There has been a firmware update for the hubs in the meantime, but I’ve just been too lazy so far.

1 Like

Yep, me too. I also have it connected to Apple Home via HomeKit.

I used my Hub M3. It also worked during the beta test period. But if MQTT worked, directly after beta release, that’s great.

I use ZHA only for some old Thermostats from China and a “Fingerbot” from AliExpress to open my door. Probably not really secure, but its works (… most the time).

:joy::joy: Laziness is always good :wink: .

1 Like

The Aqara Team reached out to me and informed me that they are working on a new firmware version for the P100. However, it needs some time…

5 Likes