Quantcast
Channel: Configuration - Home Assistant Community
Viewing all articles
Browse latest Browse all 105567

Issues with Zigbee Automations Since Installing Aqara E1 Hub

$
0
0

I’m reaching out for some assistance with a problem I’ve encountered in my Home Assistant setup, specifically related to Zigbee automations not functioning as expected after the installation of an Aqara E1 hub.

Setup:

  • Home Assistant running with a bridge to HomeKit.
  • Conbee II stick and Aqara E1 hub used for Zigbee connectivity, operating on different channels.
  • Aqara blind motors recently added to the system via the E1 hub.

Issue: Since adding the Aqara E1 hub to my setup, I’ve noticed that my Zigbee-based automations, particularly those involving sensors triggering actions like turning on lights, have become unreliable. Although I can see the sensors being activated in the Home Assistant logs (via trace), the expected actions (e.g., lights turning on) are not consistently executed.

Troubleshooting Steps Taken:

  • Confirmed that both Zigbee networks (Conbee II and Aqara E1) are on different channels to avoid interference.
  • Reviewed and validated automation configurations in Home Assistant.
  • Performed network scans to identify any potential interference issues.
  • Rebooted Home Assistant, the Conbee II stick, and the Aqara E1 hub.

Despite these steps, the issue persists. I’m seeking insights on the following:

  • Could the Aqara E1 hub be causing interference or compatibility issues, even if on a different channel?
  • Are there any known issues with running two Zigbee coordinators in close proximity that could affect automations?
  • Any recommendations on additional troubleshooting steps or configuration changes to improve reliability?

I appreciate any advice or suggestions the community can offer. Thank you for your time and assistance.

1 post - 1 participant

Read full topic


Viewing all articles
Browse latest Browse all 105567

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>