Open slikone27 opened 3 months ago
Feel free to open a pull request to fix it if you think it is easy..
Hey there @vincegio, @lastrada, mind taking a look at this issue as it has been labeled with an integration (airthings_ble
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
airthings_ble documentation airthings_ble source (message by IssueLinks)
Feel free to open a pull request to fix it if you think it is easy..
I don't think its easy at all and def didn't say that... I just said it looks like someone fixed it by copying the old code and rolling back to a previous version... so its a code change between the older version and the newest that broke it. so why not just roll back at least if the new version is an issue still... And then the issues keep getting closed w/ no fix. that's all i was saying. sorry wasn't trying to put anyone down.
any updates on this?
Bumping for info regarding this. Seeing dropouts of the Airthings integration every 5-7 minutes, running a ESP32 bluetooth proxy on ESPHome 2024.8.3. I'm only seeing these dropouts on the Airthings BLE integration.
Seeing 12 Wave Plus devices drop out at once after working fine across a few Esp32 proxies is pretty frustrating. From a logging perspective, it just points out that the devices can no longer be found.
Made it three days with 17 devices before everything became unreachable.
Is there anything I can do to assist in trouble shooting this issue as I too have this issue. I Currently have an Airthings BLE that is connected from my home assistant over a USB Bluetooth adapter with no other Bluetooth devices connected to HA. Experience the same issue with the connectivity of the device.
I managed to get 5 hours with a cluster of six bluetooth proxies handling 17 Airthings Wave+ and a couple dozen Xiaomi MiFlora BLE sensors. The Xiaomi sensors never disconnect until the proxies are rebooted.
I have the same issue with Airthings Wave Radon. I'm very eager to get this to work again. Worked fine with older versions. I thought it was my bluetooth adapter on the server that was the issue so I tested with a esp32 bluetooth proxy, seems to be the same issue.
The hass log says this when it fails:
ERROR (MainThread) [homeassistant.components.airthings_ble] Error fetching airthings_ble data:
Unable to fetch data: Failed to connect after 9 attempt(s): No backend with an available connection
slot that can reach address F3:61:77:70:02:0A was found: The proxy/adapter is out of connection slots
or the device is no longer reachable; Add additional proxies (https://esphome.github.io/bluetooth-proxies/) near this
device
The problem
There seems to be issues opened here:
https://github.com/home-assistant/core/issues/100123
https://github.com/home-assistant/core/issues/109499
That were closed or pointed to other issues that have been closed or locked... but this is STILL an issue and is happening every 30 mins or so. There seems to be suggestions to roll back to an older Airthings BLE version that "fix" the issue. Can someone that can edit the integration fix it by implementing the changes?!?! and not just close the issue?
What version of Home Assistant Core has the issue?
2024.8.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response