core
core copied to clipboard
Airthings BLE can not be set up Wave device: Unknown error "date_time"
The problem
When trying to add the new Airthings BLE addon for my Airthings Wave device, I receive error message "Unexpected error" in the UI, and the following error in the log:
2022-11-03 19:02:05.587 ERROR (MainThread) [homeassistant.components.airthings_ble.config_flow] Unknown error occurred from 98:07:2D:xx:xx:xx: 'date_time'
What version of Home Assistant Core has the issue?
core-2022.11.0
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
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?
2022-11-03 19:02:05.587 ERROR (MainThread) [homeassistant.components.airthings_ble.config_flow] Unknown error occurred from 98:07:2D:xx:xx:xx: 'date_time'
Additional information
- Have previously used Airthings plugin from HACS until that stopped working in a few months back.
- Have uninstalled the HACS addon and restarted before installing 2022.11.0.
- Upgraded from 2022.10.5 to 2022.11.0.
Hey there @vincegio, 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 close
Closes the issue. -
@home-assistant rename Awesome new title
Change the title of the issue. -
@home-assistant reopen
Reopen the issue. -
@home-assistant unassign airthings_ble
Removes the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
airthings_ble documentation airthings_ble source (message by IssueLinks)
Same error here. Adding the addon "Airthings BLE - Unexpected error" log show: Unknown error occurred from B0:91:22:XX:XX:XX: 'date_time'
Known issue since 30 aug --> https://github.com/custom-components/sensor.airthings_wave/issues/93#issuecomment-1232090555
I am seeing the same Unknown error occurred from B0:91:22:XX:XX:XX: 'date_time'
error in my HA Core logs. I have two Airthings Wave devices: one 1st generation, and one 2nd generation. The gen2 Wave was detected automatically by the new integration in HA 2022.11.0 and is working great. The error message I see in the log is for the gen1 Wave. There are significant differences in how the sensor data is fetched from a gen1 vs. a gen2 Wave, which I suspect may be a factor here.
@magfro @tgmos Which generation of Airthings Wave do you have? Serial numbers 2900xxxxxx are gen1, and 2950xxxxxx are gen2.
I concur with your assessment @bcochrane I have a 1st gen as well.
@bcochrane Yes, serial 2900* here as well, so Gen1 it is.
So are we saying that Gen1 is not supported?
Both of mine are gen1, serial 2900*
Same here. Two units both gen 1 model 2900.
Same issue, serial is 29300*, firmware BLE 2.1.0 / MSP 2.1.0 / SUB1 2.0.17
Getting the same error
S/N 2950* and 2900* with same issue.
I am also seeing this error for my 1st Gen Wave.
Logger: homeassistant.components.airthings_ble.config_flow Source: components/airthings_ble/config_flow.py:147 Integration: Airthings BLE (documentation, issues) First occurred: 4:38:32 PM (6 occurrences) Last logged: 9:03:11 PM
Unknown error occurred from 98:07:xxxxxx: 'date_time'
Works great in 2022.11.3 Thanks!!!
For me not. When try to install, get error "504 Gateway Time-out". All other bluetooth devices are working normally. At least it is different error than before.
As i am not physically in this place where Airthings is installed, cannot commit that issue is not caused by Airthings itself. It is not low battery -issue as i have separate powersource installed for Airthings to avoid batteries. Also no errors seen on Logfiles anymore.
Unfortunately i have to wait until new year to check that all is ok on Airthings side....and then I come back to this.
Works great in 2022.11.3 Thanks!!!
Me as well. Thanks!