You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two 1st gen airthings wave units (Model 2900). When both are close to the HASSIO system with BLE radio, the addon works fine. When one is in the basement where it normally lives (in a problematic reception area that sometimes works and sometimes doesn't), the addon freezes with no log info that I can see. It will work on a restart until it can't connect. It doesn't seem to timeout and move on, it just freezes. I would not mind at all if it got no data then moved on. I can account for failures by scheduling it often enough.
Here are the last few lines of the current log (it's about 16:15 now, so it froze about 7 hours ago). On this restart, it successfully interviewed the problem unit twice before freezing up. I can replicate this very consistently.
[2022-08-22 09:08:07] INFO: Done sending messages to mqtt broker.
[2022-08-22 09:08:07] INFO: Waiting 600 seconds.
[2022-08-22 09:18:08] DEBUG: Getting sensor data...
[2022-08-22 09:18:08] DEBUG: Getting sensor data for 98:07:2d:4a:2a:01
[2022-08-22 09:18:08] DEBUG: Connecting to 98:07:2d:4a:2a:01
Home Assistant 2022.8.6
Supervisor 2022.08.3
Operating System 8.4
Running in a VM on top of xcp-ng
The text was updated successfully, but these errors were encountered:
Thank you for the bug report, and it definitely should not be working that way and should instead timeout and move on like you suggested. I will take a look to see if I can find the error. However, the best news that I may have for you is that someone is working on bringing support for Airthings devices to Home Assistant Core using the new bluetooth support. In my mind this is a better option than using my add-on, and if done will render this add-on obsolete. If you are interested you can go here to see the discussion.
I have two 1st gen airthings wave units (Model 2900). When both are close to the HASSIO system with BLE radio, the addon works fine. When one is in the basement where it normally lives (in a problematic reception area that sometimes works and sometimes doesn't), the addon freezes with no log info that I can see. It will work on a restart until it can't connect. It doesn't seem to timeout and move on, it just freezes. I would not mind at all if it got no data then moved on. I can account for failures by scheduling it often enough.
Here are the last few lines of the current log (it's about 16:15 now, so it froze about 7 hours ago). On this restart, it successfully interviewed the problem unit twice before freezing up. I can replicate this very consistently.
[2022-08-22 09:08:07] INFO: Done sending messages to mqtt broker.
[2022-08-22 09:08:07] INFO: Waiting 600 seconds.
[2022-08-22 09:18:08] DEBUG: Getting sensor data...
[2022-08-22 09:18:08] DEBUG: Getting sensor data for 98:07:2d:4a:2a:01
[2022-08-22 09:18:08] DEBUG: Connecting to 98:07:2d:4a:2a:01
Home Assistant 2022.8.6
Supervisor 2022.08.3
Operating System 8.4
Running in a VM on top of xcp-ng
The text was updated successfully, but these errors were encountered: