core
core copied to clipboard
Readings become unavailable all the time (and then come back).
The problem
The logged readings are not continuous. This means the devices keep becoming unavailable and then come back. Can we please have an option that prevents logging when the device is unavailable? That would save spare and be more useful.
What version of Home Assistant Core has the issue?
core-2024.1.6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Airthings BLE
Link to integration documentation on our website
https://www.home-assistant.io/integrations/airthings_ble/
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
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!
Code owner commands
Code owners of airthings_ble can trigger bot actions by commenting:
@home-assistant closeCloses the issue.@home-assistant rename Awesome new titleRenames the issue.@home-assistant reopenReopen the issue.@home-assistant unassign airthings_bleRemoves the current integration label and assignees on the issue, add the integration domain after the command.@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue.@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
airthings_ble documentation airthings_ble source (message by IssueLinks)
I have this same issue. From beginning of February or so the integration started to be very unreliable and the sensor values update only by soft booting or sometimes not even then, and sometimes recovering randomly for a moment.
Core 2024.1.6 Supervisor 2023.12.1 Operating System 11.4 Frontend 20240104.0
Here is some sample data showing how the data is breaking. It was alright until end of Jan, but then it started this glitching.
Here is some sample data showing how the data is breaking. It was alright until end of Jan, but then it started this glitching.
The intermittent logging to the right is what I see. I don't get the long pauses, though.
To me it seems that the integration logs failed readings, which don't really makes sense to me.
Here is some sample data showing how the data is breaking. It was alright until end of Jan, but then it started this glitching.
The intermittent logging to the right is what I see. I don't get the long pauses, though.
To me it seems that the integration logs failed readings, which don't really makes sense to me.
Correct, the long pauses are not really relevant in this scope. The long pauses are caused by my attempts to reboot and solve the issue, but I had hard time to get the integration to provide any data for a while. Anyway the relevant samples are the beginning where the integration operated normally and the later part which is clearly very fragmented.
After updating to 2024.1.6 i'v got the same behaviour. Arting is randomly (not)available.
same for me as well. keep going unavailable way too many times.. I have three airthings wave plus.. and each of them goes of randomly unavailable...
Same issue here. I was really starting to worry about my setup haha.
i have been observing the same, running:
- core:
2024.1.6 - supervisor:
2024.01.1 - operating system:
11.5
here you can see how frequent my drops are over the past 24 hours...
i reviewed the home-assistant.log, but nothing jumps out to me here. no exceptions are logged that i can see.
Same for me here, keep dropping and sometime it come back for 30min or so then drop again, reboot will bring it back for a short time.
The same issue here. But noticed it some time ago already. Now running latest versions. By any chance, can this be somehow effected by other integrations? Matter? Zigbee? OR: update on AirThings side?
Everything is possible, but probably all of us started to have these problems after installing 2024.1.6, which had and airthing-ble update in it...
I ended up creating an automation that reloads the integration every 5 minutes..!! ( with condition if reading is unavailable)I would definitely like to avoid this unnecessary burden on my HA and Air things WaveBut so far it is good.. pretty much no missed valuesOn Feb 8, 2024, at 8:07 AM, Erik Stofira @.***> wrote: Everything is possible, but probably all of us started to have these problems after installing 2024.1.6, which had and airthing-ble update in it...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>
Have been having same issue for couple of weeks now as well. Entities go unavailable and back multiple times a day.
Now all my Wave+ data entries have gone unavailable. I hadn't done anything. The Aithing Wave+ is a nice device but the BT integration has been problematic for months ... complete garbage
This has been getting worse. After the first issue in 2024.1.6 I downgraded back to 2024.1.4 and it was all good. When a new core update shows up I give it a try and if it still doesn't work I go back to 2024.1.4. However, now 2024.1.4 no longer works. The device goes to unavailable and occasionally the integration has issues initializing and will fail.
Core - 2024.1.4 Supervisor - 2024.01.1 Operating System - 11.5 Frontend - 20240104.0
About every 15 minutes, my Wave+ disconnects for ~5 minutes. This is highly annoying, and breaks some automations that use the unavailable state (ex. to detect a dead battery).
It seems to me that the Airthings device updates less frequently than the timeout that makes the entity be marked as unknown. It would be nice if this timeout could be set longer for the Airthings Integration.
Same thing happened for me with 2024.1.6 update. No need to reload but sensor becomes "unavailable" frequently
following up that i am seeing the same unavailable behaviour described in my last comment after upgrading core to 2024.2.1 from 2024.1.6.
Have this exact issue as well.
I updated everything I could. Not only restarted HA, but power cycled my HA device. Took fresh batteries for the Airthings Wave+, placed it just next to each other. And it works just fine now!
I tried the same. Brand new batteries & power cycling ... problem still persists with dropouts multiple times per hour :(
I updated everything I could. Not only restarted HA, but power cycled my HA device. Took fresh batteries for the Airthings Wave+, placed it just next to each other. And it works just fine now!
I did the same but still have issues. The frequency of the drops seem to have reduced a bit with recent home assistant release but still happens.
Update on SW on the AirThings Wave side? Distance reduction? Just thinking out loud....
Update on SW on the AirThings Wave side? Distance reduction? Just thinking out loud....
No changes other than newer version of home assistant, not sure if any auto firmware updates happened in the background on the Airthings.
Update on SW on the AirThings Wave side? Distance reduction? Just thinking out loud....
No changes other than newer version of home assistant, not sure if any auto firmware updates happened in the background on the Airthings.
For BLE connected devices you will see a message in the Airthings app you need to click on. No messages in the app = newest version.
What? New version of what?
What? New version of what?
https://www.home-assistant.io/blog/2024/02/07/release-20242/
What? New version of what?
I answered on firmware updates ("Update on SW on the AirThings Wave side?" / "not sure if any auto firmware updates happened in the background on the Airthings."). Here you can find latest FW version for Wave Radon/Plus/Mini: https://help.airthings.com/en/articles/6951942-firmware-release-notes
You can compare it with what's listed in Home Assistant.
There hasn't been any FW for a while, so this has nothing to do with this topic, except maybe if you bought it years ago and never connected it to the Airthings app to update it.
