SOLVED: Airthings Wave does not communicate with HA after the initial setup

Configuration
1

Hi, I could use some help as I’m stuck setting up the Airthings Wave in HA.

I’ve repeated the setup process multiple times using the Airthings BLE plugin but got the same results. The dashboard only populates with a “dummy” default data and stays like that all day.

I’ve found that there is a security error in the log, but I’m unable to figure out what is causing the error.

Error 0x0E Host Rejected due to security reasons (The host at the remote side has rejected the connection because the remote host determined that the local host did not meet its security criteria.)

I’m running the latest HA in the VM on Windows 10 desktop. The bluetooth adapter is Plugable Bluetooth 4.0 and the Airthing Wave is less than 2m away.

Any help is appreciated.

airthings-ble
airthings-ble828×550 16.7 KB

AIRTHINGS BLE LOG FILE

[16:34:49] INFO: Internal MQTT service found, fetching configuration ...
[16:34:50] INFO: Starting python script...
[2023-01-13 16:34:50] INFO: Setting up Airthings sensors...
[2023-01-13 16:34:55] WARNING: Error getting hardware_rev
[2023-01-13 16:34:58] INFO: f0:f8:f2:4f:5a:61: Manufacturer: Airthings AS Model: 2900 Serial: Serial Number Device: AT#-----/-----Radon Firmware: COR9001B.1703301 Hardware Rev.: 
[2023-01-13 16:35:17] ERROR: Error getting sensor data for 'f0:f8:f2:4f:5a:61': [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Connection Rejected Due To Security Reasons)
Traceback (most recent call last):
  File "/src/airthings.py", line 316, in get_sensor_data
    data = await self._dev.read_gatt_char(characteristic.uuid)
  File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/client.py", line 572, in read_gatt_char
    assert_reply(reply)
  File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/utils.py", line 22, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.bluez.Error.Failed] Operation failed with ATT error: 0x0e (Connection Rejected Due To Security Reasons)
[2023-01-13 16:35:17] INFO: Sending HA mqtt discovery configuration messages...
[2023-01-13 16:35:17] INFO: Sending messages to mqtt broker...
[2023-01-13 16:35:17] INFO: Done sending messages to mqtt broker.
[2023-01-13 16:35:17] INFO: Done sending HA mqtt discovery configuration messages.
[2023-01-13 16:35:22] INFO: Collecting sensor value messages...
[2023-01-13 16:35:22] INFO: airthings/f0:f8:f2:4f:5a:61/illuminance = 0.0
[2023-01-13 16:35:22] INFO: airthings/f0:f8:f2:4f:5a:61/accelerometer = 0.0
[2023-01-13 16:35:22] INFO: airthings/f0:f8:f2:4f:5a:61/humidity = 178
[2023-01-13 16:35:22] INFO: airthings/f0:f8:f2:4f:5a:61/temperature = 46.6
[2023-01-13 16:35:22] INFO: airthings/f0:f8:f2:4f:5a:61/radon_longterm_avg = 0
[2023-01-13 16:35:22] INFO: airthings/f0:f8:f2:4f:5a:61/radon_1day_avg = 0
[2023-01-13 16:35:22] INFO: Sending messages to mqtt broker...
[2023-01-13 16:35:22] INFO: Done sending messages to mqtt broker.
[2023-01-13 16:35:22] INFO: Waiting 150 seconds.
2

Answering my question:

I noticed that my Airthings phone app had an issue connecting to the Airthings Wave. The data was not being received properly. When I tried the app on another phone, the Wave was found immediately and the data was accurate.

I was able to pinpoint the issue with my phone’s Bluetooth connection. After clearing the Bluetooth app cash/data my phone connected to the Wave and started receiving the data again. This solution also triggered the HA to start receiving data.

The Airthings BLE plugin requires at least one device to be connected to the Wave for the plugin to work. Because of my phone’s issues with Bluetooth, that connection was not established, thus the HA was showing a security error.

I hope this helps someone with a similar issue.

3 Likes
3

Hi, Sorry, I am a little confused. I am also experiencing this issue. Why does the Airthings need to be connected to the Phone in order for BLE to work between my HA instance and the Airthings unit? This was all working flawlessly until a month or so ago… any pointers (other than to connect the phone as this is bonkers) Thanks