Invalid Config popping up for xiaomi-aqara

Installation Home Assistant OS
1

Hi,

I just installed Hass.io on a RPI3 and it pops up "Invalid Config, the following components and platforms could not be set up: - xiaomi-aqara’ please check your config.

When I check the config file it says its fine.

Also - note: I have a Xiaomi gateway on the same network, but I had not added any custom configs to Hass. It’s not possible for Haas to pick up the gateway automatically yes?

Subsequently, I chose to add the config for xiaomi. It still says its the config is valid when checked, but when booted, the warning shows.

What’s going on?

Running latest Hass.io

Any help is appreciated!

2

it is my understanding that this component wasn’t part of the discovery, but let’s try.

do you have the discovery component active in your config?

3

Yes it’s on.

Commented it out and restarted, then the same error + ZWave also is now said to be invalid. Reverted to original state, still saying ZWave is also misconfigured.

Here’s my config file for ref:
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: 6.9319
longitude: 79.8478
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 8
# metric for Metric, imperial for Imperial
unit_system: metric
# Pick yours from here:
time_zone: Asia/Colombo
# Customization file
customize: !include customize.yaml

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

http:
  # Secrets are defined in the file secrets.yaml
  # api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Enables a map showing the location of tracked devices
map:

# Track the sun
sun:

# Weather prediction
sensor:
  - platform: yr

# Text to speech
tts:
  - platform: google

# Cloud
cloud:


zwave:
  usb_path: /dev/ttyACM0

#xiaomi
xiaomi_aqara:
  discovery_retry: 10
  gateways:
    - host: 192.168.55.137


group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
4

also the error logs.

Timer got out of sync. Resetting
11:53 PM core.py (ERROR)
Found malformed XML at http://192.168.55.112:9080: status=ok
11:52 PM ssdp.py (WARNING)
Setup failed for xiaomi_aqara: Component failed to initialize.
11:52 PM setup.py (ERROR)
No gateway discovered
11:52 PM components/xiaomi_aqara.py (ERROR)
Setup of xiaomi_aqara is taking over 10 seconds.
11:51 PM bootstrap.py (WARNING)
Error during setup of component zwave
11:51 PM components/zwave/__init__.py (ERROR)
Key is not provided for gateway None. Controlling the gateway will not be possible
11:51 PM components/xiaomi_aqara.py (WARNING)
5

You need to provide the key as well

6

yeah, @arsaboo is right, you need to provide the key.

check here: https://home-assistant.io/components/xiaomi_aqara/

7

Thank you everyone! that worked! :slight_smile:

8

I just updated to 0.86.4 and now I got the same message:
image
Also my automations with Xiaomi sensors are not working anymore.
Does someone know what I have to adjust?

9

Hi Hackmett,

I had the same issue after upgrading to V 0.86.4.

I created a new key for the gateway in the Mi Home app and deleted & re added the gateway as a device.

Restarted HA and it worked!

1 Like
10

Hi Thieme,
thanks. I was actually only too impatient. After another restart everything worked for me.

11

My system is working fine and also spitting out this error. I built it in a VM of Ubuntu and it’s definitely talking ok to my Xiami Aquara (?) home hub thing to turn on switches and door sensors etc, yet this minor error is still coming up from the wizard.