Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New device support]: Aqara A100 Pro Smart Door Lock #13087

Open
rafaelreis-r opened this issue Jul 9, 2022 · 51 comments
Open

[New device support]: Aqara A100 Pro Smart Door Lock #13087

rafaelreis-r opened this issue Jul 9, 2022 · 51 comments
Labels
dont-stale new device support New device support request stale Stale issues

Comments

@rafaelreis-r
Copy link

rafaelreis-r commented Jul 9, 2022

Link

https://www.aqara.com/en/product/smart-door-lock-a100-zigbee

Database entry

"definition":null,"friendly_name":"0x54ef4410004c5112","ieee_address":"0x54ef4410004c5112","status":"successful","supported":false},"type":"device_interview"

Comments

Hey all. I just got my hands on a Aqara A100 Pro smart lock. Although I'm a competent sysadmin, I've never worked with zigbee devices. Wondering if I could provide info / be guided to dump information in order to add support to this family of door locks.

Hardware I own:

  • Conbee II stick on the latest firmware
  • Pi4 running HASSIO / Zigbee2mqtt
  • Aqara G3 Camera Hub (unfortunately non rooted)

I'm willing to purchase a CC2531 sniffer if necessary.

What have I done so far:

  • read the guide
  • Checked out lumi.lock entries on Xiaomi.js
  • Figured out a Pairing process explained below.

Pairing Process

The A100 series do not have a physical Zigbee pairing button / process. You need a compatible Aqara Hub to trigger the pairing on the lock. I figured out a way to do it:

  1. Add the lock to the Aqara app (Bluetooth)
  2. Add your zigbee hub to the Aqara app (wifi)
  3. Permit Join All on Zigbee2mqtt
  4. Still in the Aqara app, go to the lock settings and follow the prompts to bind it to your Aqara Zigbee Hub (in my case the G3)
  5. As soon as you hear the audio / led prompt from the Aqara hub, cut it's power.
  6. If you get the timing right, (took me 3 attempts) the lock will complete pairing process to Zigbee2Mqtt

A100 Pro vs A100 Zigbee

I read that both have Zigbee functionality, Pro version lacking remote unlock and remote passcode setup as compared to the Zigbee version. I couldn't find the Zigbee version at the time of purchase. Details here

Logs I collected over the pairing procedure

info  2022-07-06 18:29:44: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef4410004c5112","ieee_address":"0x54ef4410004c5112"},"type":"device_joined"}'
info  2022-07-06 18:29:44: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":{"friendly_name":"0x54ef4410004c5112"},"type":"device_connected"}'
info  2022-07-06 18:29:44: Starting interview of '0x54ef4410004c5112'
info  2022-07-06 18:29:44: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0x54ef4410004c5112","ieee_address":"0x54ef4410004c5112","status":"started"},"type":"device_interview"}'
info  2022-07-06 18:29:44: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_started","meta":{"friendly_name":"0x54ef4410004c5112"},"type":"pairing"}'
error 2022-07-06 18:32:10: Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 genIdentify(["identifyTime"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'
info  2022-07-06 18:32:10: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 genIdentify([\"identifyTime\"], {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (no response received)'","meta":{"friendly_name":"0x54ef4410004c5112"},"type":"zigbee_publish_error"}'
error 2022-07-06 18:32:17: Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 genIdentify(["identifyTime","identifyCommissionState"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'
info  2022-07-06 18:32:17: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 genIdentify([\"identifyTime\",\"identifyCommissionState\"], {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (no response received)'","meta":{"friendly_name":"0x54ef4410004c5112"},"type":"zigbee_publish_error"}'
error 2022-07-06 18:32:23: Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 genGroups(["nameSupport"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'
info  2022-07-06 18:32:23: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 genGroups([\"nameSupport\"], {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":null,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (no response received)'","meta":{"friendly_name":"0x54ef4410004c5112"},"type":"zigbee_publish_error"}'
error 2022-07-06 18:32:49: Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 aqaraOpple(["mode"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4447,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'
info  2022-07-06 18:32:49: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 aqaraOpple([\"mode\"], {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":4447,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (no response received)'","meta":{"friendly_name":"0x54ef4410004c5112"},"type":"zigbee_publish_error"}'
error 2022-07-06 18:32:53: Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 aqaraOpple(["mode","illuminance"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4447,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received)'
info  2022-07-06 18:32:53: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'read' to '0x54ef4410004c5112' failed: 'Error: Read 0x54ef4410004c5112/1 aqaraOpple([\"mode\",\"illuminance\"], {\"sendWhen\":\"immediate\",\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":true,\"direction\":0,\"srcEndpoint\":null,\"reservedBits\":0,\"manufacturerCode\":4447,\"transactionSequenceNumber\":null,\"writeUndiv\":false}) failed (no response received)'","meta":{"friendly_name":"0x54ef4410004c5112"},"type":"zigbee_publish_error"}'
info  2022-07-06 18:41:04: Successfully interviewed '0x54ef4410004c5112', device has successfully been paired
warn  2022-07-06 18:41:04: Device '0x54ef4410004c5112' with Zigbee model 'undefined' and manufacturer name 'undefined' is NOT supported, please follow https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
info  2022-07-06 18:41:04: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":null,"friendly_name":"0x54ef4410004c5112","ieee_address":"0x54ef4410004c5112","status":"successful","supported":false},"type":"device_interview"}'
info  2022-07-06 18:41:04: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"friendly_name":"0x54ef4410004c5112","supported":false},"type":"pairing"}'
info  2022-07-07 14:56:39: Removing device '0x54ef4410004c5112' (block: false, force: true)
info  2022-07-07 14:56:39: MQTT publish: topic 'zigbee2mqtt/0x54ef4410004c5112', payload ''
info  2022-07-07 14:56:39: Successfully removed device '0x54ef4410004c5112' (block: false, force: true)
info  2022-07-07 14:56:39: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/remove', payload '{"data":{"block":false,"force":true,"id":"0x54ef4410004c5112"},"status":"ok","transaction":"tpf8h-1"}' 

External converter

No response

Supported color modes

No response

Color temperature range

No response

@rafaelreis-r rafaelreis-r added the new device support New device support request label Jul 9, 2022
@rafaelreis-r rafaelreis-r changed the title [New device support]: [New device support]: Aqara A100 Pro Smart Door Lock Jul 9, 2022
@idomp
Copy link

idomp commented Jul 31, 2022

Would really like to see support for this lock!

@kenchan97
Copy link

+1

@rafaelreis-r
Copy link
Author

I'm from Brazil and BRL to USD exchange rates are atrocious, but I'm able to provide a 40 USD bounty to get this working.

@Koenkk maybe you would be able to take a look at this or point me out on a direction?

@Koenkk
Copy link
Owner

Koenkk commented Aug 2, 2022

@rafaelreis-r could you make a sniff when pairing the device to the original hub? https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html#with-cc2531

@MaxD16
Copy link

MaxD16 commented Aug 3, 2022

+1

@rafaelreis-r
Copy link
Author

rafaelreis-r commented Aug 4, 2022

@rafaelreis-r could you make a sniff when pairing the device to the original hub? https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html#with-cc2531

Just received the CC2531 today. Flashed it and compiled whsniff. Files are attached below.
I've also added the pairing process to a known device (Aqara Mini Switch - WXKG12LM) for reference.

Attachements:

Notes:

  • Transport Key is in the Device Announcement packet in the capture.
  • I performed most of the basic actions with the door lock after pairing. That is also included in the capture. I figured it might help with the converter.
  • This was more challenging than I anticipated. But I suppose everything was sniffed properly.

@Koenkk
Copy link
Owner

Koenkk commented Aug 6, 2022

@rafaelreis-r

  • Could you also provide me a sniff when pairing it to z2m?
  • What command is send when the lock is locked/unlocked? (can you indicate the No. in wireshark?)

@rafaelreis-r
Copy link
Author

@Koenkk

Could you also provide me a sniff when pairing it to z2m?

I tried using a converter based on lumi.lock.acn02, since the A100 reports itself as lumi.lock.acn01, but didn't seem to work (I don't discard having screwed up somewhere).

I had to spin up a separate Z2M instance since my network is very busy atm, and I needed to be close to the lock.
All I had was a windows laptop, so the logs will reflect that.

What command is send when the lock is locked/unlocked? (can you indicate the No. in wireshark?)

This is the sequence of events reported in the door lock log. Note that it is from new to old, so reverse of what wireshark logged. "Me" refers to me. It reports the user which did the action. If it was my wife for instance, it would say her Name instead of "Me"

Unfortunately I'm unable to align No. with time. I could do a new dump paying attention to the No. if you need.

@Koenkk
Copy link
Owner

Koenkk commented Aug 8, 2022

So the first issue that needs to be tackled is that the device leaves almost immediately after pairing it to z2m (packet 71 in A100 Z2M Pairing.pcapng.gz). I've compared the z2m vs the xiaomi gateway sniff and everything is the same until the Node Descriptor Response (packet 117/67). In the z2m sniff the device leaves 2 seconds after this. In the Xiaomi sniff some encrypted commands are send after this (it seems Xiaomi uses a custom encryption key for this). My first suspicion is that the small differences in the node descriptor response may cause this but unfortunately I cannot change the adapter the node descriptor response because the Conbee firmware is not opensource. Do you also have access to a Texas Instruments based adapter?

@rafaelreis-r
Copy link
Author

@Koenkk

I only own the Conbee-II and the CC2531 flashed for sniffing. Electronics are highly tariffed and expensive in Brazil. I usually import them directly from China (which is what I did with the door lock) but it takes 45 to 60 days for customs clearance.

I could purchase another TI device. The only options I could find in stock atm are:

  • Another CC2531
  • SONOFF Zigbee 3.0 USB Dongle Plus (CC2652P)

What would you technically recommend?

@Koenkk
Copy link
Owner

Koenkk commented Aug 9, 2022

The SONOFF Zigbee 3.0 USB Dongle Plus (CC2652P)

@rafaelreis-r
Copy link
Author

Hey @Koenkk

Device arrived. It came preloaded with Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'

Let me know if it requires updating (I still have to learn the update process).

I took a sniff and debug logs from the pairing process to this device:

Interesting to note this time the lock looped trying to pair to the coordinator until it gave up after 4 or 5 attempts, as you will be able to see in the dump.

Let me know what else you need me to do!

@Koenkk
Copy link
Owner

Koenkk commented Aug 16, 2022

So it seems the device stays connected for a bit longer and z2m is able to retrieve some data from it. It is important to use the latest firmware on your adapter; otherwise the node descriptor returns an incorrect manufacturer code for Xiaomi devices. There are some instructions on how to flash the fw here: https://www.zigbee2mqtt.io/guide/adapters/#notes (on this page you can also find the correct coordinator firmware).

What worries me a bit is that the device now leaves after it doesn't receive a reply to the encrypted magic command. With the Xiaomi gateway you see the the gateway replies:

Screenshot 2022-08-16 at 20 33 23

With z2m it doesn't (which of course we cannot do since we cannot encrypt this message):

Screenshot 2022-08-16 at 20 37 00

I think this causes the device to leave. Seems Xiaomi doesn't want this to be device to be used with other gateways. If the coordinator firmware update doesn't solve the issue I'm quite certain this is the reason the device leaves. So in order to be able to continue we need the encryption key. I see 2 scenarios to obtain this:

  • Xiaomi provides us with the encryption key
  • We do a brute-force; however this doesn't seem to be a realistic option. The key is 128 bits which results in the following computation time (source):

Screenshot 2022-08-16 at 20 42 35

@rafaelreis-r
Copy link
Author

rafaelreis-r commented Aug 16, 2022

Hey @Koenkk,

Updated the firmware to Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"}' and redid the sniffs / logs. For some reason, z2m and zigbee-herdsman debug logs were very verbose this time.

It looks like the sniff is void of the bad FCS packets!

I hope we aren't locked out due to the encryption key. There is a 3rd way to get them, similar to what this engineer did recently with the embedded linux embedded os fw in his car. We might be able to find the key inside the source files / update files to Aqara's hubs.

It is a pretty interesting read, despite offtopic.

@Koenkk
Copy link
Owner

Koenkk commented Aug 17, 2022

Strangely enough I don't see the magic commands anymore in this sniff but the device still leaves. What I find interesting is that the Transport key message when paired with the Xiaomi gateway uses the non-standard TC link key (at least I guess this is the transport key because it comes right after the assocation response and there are not any other transport key messages).

Screenshot 2022-08-17 at 20 19 09

I guess that we need the Xiaomi encryption key to continue further with this.

@wifispray
Copy link

Would love to see support for this device

@rafaelreis-r
Copy link
Author

@Koenkk I was able to root my G3 hub after a bit of work, and dump some zigbee info from it. I'm working with the Aqara GW rooted HA integration devs on their rep. Thread is here

They have good knowledge of many Aqara hubs rootfs, and also stock and modified fw dumps for various hubs. They have coordinator fw for the Aqara hubs dumped there as well. I just asked them if they were able to extract a coordinator fw to any of those hubs. We might have luck finding something there.

@NdR91
Copy link

NdR91 commented Aug 28, 2022

Would love to use this device with z2m...

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Sep 28, 2022
@IamMattM
Copy link

IamMattM commented Oct 2, 2022

Would love to use this device with z2m...

Same for me.

@github-actions github-actions bot removed the stale Stale issues label Oct 3, 2022
@waterdrop01
Copy link

waterdrop01 commented Oct 3, 2022

I encourage anyone interested into solving this issue to report it on the Aqara support page => https://static-resource.aqara.com/html/feedback.html,

Asking them to share the encryption key. Here is a message example:

A100 z2m support

Dear Aqara team,

Looking at the comments in this youtube video (https://www.youtube.com/watch?v=LBAfbBE9-Bo), you can see that A LOT of people WILL NOT BUY the Aqara A100 because it is NOT SUPPORTED by zigbee2mqtt.

The issue is that Aqara A100 firmware is using en encryption key to communicate over zigbee (see details about the issue here => https://github.com/Koenkk/zigbee2mqtt/issues/13087) and WITHOUT this encryption key, it's nearly impossible to support the A100 into zigbee2mqtt.

Could you please consider working out a solution to add support for the A100 into zigbee2mqtt? (like sharing the key with z2m devs)

Having an open system will definitely boost your sales ;)

Thanks!

@NdR91
Copy link

NdR91 commented Oct 3, 2022

Thank you @waterdrop01, I just sent the ticket.

I have another questione for who already own the Aqara A100: what about the integration in Home Assistant over HomeKit Controller? Is that possible?

@rafaelreis-r
Copy link
Author

Thank you @waterdrop01, I just sent the ticket.

I have another questione for who already own the Aqara A100: what about the integration in Home Assistant over HomeKit Controller? Is that possible?

It is VERY limited in HomeKit. Not a viable solution. Best path so far has been AqaraGateway + rooted hub.

@NdR91
Copy link

NdR91 commented Oct 3, 2022

Thank you @waterdrop01, I just sent the ticket.

I have another questione for who already own the Aqara A100: what about the integration in Home Assistant over HomeKit Controller? Is that possible?

It is VERY limited in HomeKit. Not a viable solution. Best path so far has been AqaraGateway + rooted hub.

I'll probably go with that solution.

What's the benefits using the Rooted gateway instead of the stock one?

@github-actions github-actions bot added the stale Stale issues label Nov 4, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 12, 2022
@ChipWolf
Copy link

@Koenkk can we destale this?

@Koenkk Koenkk reopened this Dec 27, 2022
@Koenkk Koenkk removed the stale Stale issues label Dec 27, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Jan 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 3, 2023
@hobbit44
Copy link

hobbit44 commented Feb 8, 2023

Could this be reopened and pinned please?

@hobbit44
Copy link

@Koenkk

@Koenkk Koenkk reopened this May 22, 2023
@TerryRhodes
Copy link

I assume there's nothing to update on this yet, eh? :(

@rafaelreis-r
Copy link
Author

rafaelreis-r commented Aug 1, 2023

Zigbee Smart Energy is an entirely different standard as compared to standard Zigbee protocol. It would take:

  1. Adding support to ZSE in Z2M
  2. Find a workaround to obtain root certificates from manufacturer, be it shared by them or obtained by reverse engineering. Without those certificates, there is no way to derive the link key for the device.

Another way would be to have the community develop a custom firmware for the A100 (N100 and other locks in that family) that supports standard zigbee.

@TerryRhodes
Copy link

Zigbee Smart Energy is an entirely different standard as compared to standard Zigbee protocol. It would take:

  1. Adding support to ZSE in Z2M
  2. Find a workaround to obtain root certificates from manufacturer, be it shared by them or obtained by reverse engineering. Without those certificates, there is no way to derive the link key for the device.

Another way would be to have the community develop a custom firmware for the A100 (N100 and other locks in that family) that supports standard zigbee.

And I assume the custom firmware path is not currently being worked on by anyone? Shame if not.

@alectogeek
Copy link

The lack of support for HA stops me from buying their product, LOL.
Shame on you, Aqara!

@NdR91
Copy link

NdR91 commented Jan 11, 2024

The lack of support for HA stops me from buying their product, LOL.

Shame on you, Aqara!

At the end of all I went for a very classical electromechanical lock. I'll connect it to a Shelly 1 soon and to an UPS.
Afrer that with an ESP i will manage the fingerprint sensor.

All managed by HA.

Yes, this isn't the same prpduct but imho it will work even better.

@vantuyen3103
Copy link

Is there any update on this?

@rafaelreis-r
Copy link
Author

A100 Bluetooth integration on HA seems to be stable now. Requires Bluetooth range.

Pairing it to HomeKit controller also works.

Over zigbee the only way is through AqaraGateway on supported gateways.

@sulliwane
Copy link

sulliwane commented Apr 1, 2024

A100 Bluetooth integration on HA seems to be stable now. Requires Bluetooth range.

Pairing it to HomeKit controller also works.

Over zigbee the only way is through AqaraGateway on supported gateways.

May I ask what type of sensors do you get with Bluethooth connection? Here is what I have using Aqara Gateway:
image

Also, what does the pairing method look like when using bluetooth? (My HA supports bluetooth so it may be more reliable than the Aqara Gateway integration that sometimes does not start properly).

Thanks :)

@raarts
Copy link

raarts commented Apr 15, 2024

A100 Bluetooth integration on HA seems to be stable now. Requires Bluetooth range.

Does that mean I can now use the lock with all functionality on my HA? Any more info on how to set this up, or is it automatic?

@JustAnotherPU
Copy link

same question here guys, can we integrate the doorlock to HA now ? I have a D200I what about this one ?

@mainmind83
Copy link

@SemonCat
Copy link

SemonCat commented Nov 6, 2024

A100 Bluetooth integration on HA seems to be stable now. Requires Bluetooth range.

Pairing it to HomeKit controller also works.

Over zigbee the only way is through AqaraGateway on supported gateways.

which Bluetooth integration can integrate a100?

@kevin-olbrich
Copy link

A100 Bluetooth integration on HA seems to be stable now. Requires Bluetooth range.
Pairing it to HomeKit controller also works.
Over zigbee the only way is through AqaraGateway on supported gateways.

which Bluetooth integration can integrate a100?

https://esphome.io/components/bluetooth_proxy.html

@almirus
Copy link

almirus commented Nov 6, 2024

@GoshaGinzburg
Copy link

A100 Bluetooth integration on HA seems to be stable now. Requires Bluetooth range.

which Bluetooth integration can integrate a100?

https://esphome.io/components/bluetooth_proxy.html

Hi! Can you explain how to connect aqara A100 with esphome bluetooth proxy? Thanks.

@mainmind83
Copy link

mainmind83 commented Jan 1, 2025

@JustAnotherPU @mainmind83
https://github.com/niceboygithub/AqaraGateway
image

In mi case problems with IPv6, QNAP and HA (sorry U200 model)
https://www.mainmind.com/blog/ipv6-nas-qnap/

@sprint1849
Copy link

Hi, I have been following this thread.

I have successfuly set up Aqara A100 Pro with E1 Hub using niceboy's Aqara Gateway integration.

It's all fun and game until I block internet to the gateway and you restart the gateway or there is power interruption.

The setup is perfect for me, however, this is my only problem. I need my setup to be offline.

Is there any way how to do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dont-stale new device support New device support request stale Stale issues
Projects
None yet
Development

No branches or pull requests