-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Airthings Wave (gen 1) #1467
Comments
Thanks for creating this issue, I bought two of them last week when there was a big sale. However, I am not able to connect wave or wave_mini using EP32. Kindly help add support to these devices too. Wave-mini, don't allow me to save and install not sure if there is any mistake in the spell of the example and the actual class please check. |
I’m having similar issues with my original wave device too. It looks like there are different repositories for each of the different models (for integration with raspberry pi) https://github.com/airthings |
There were two versions of the wave devices there seem to be some changes in the data structure according to the own Airthings sample code https://github.com/Airthings/wave-reader |
tagging @jeromelaban because esphome/esphome#1656 Any ideas of how to get Airthings Wave Gen 1 supported? These UUIDs that are known to work from https://github.com/sabeechen/AirthingsMQTT
Edit: based on Airthings/wave-reader
|
For gen 1 wave one can just create custom BLE client sensor:
|
@debsahu Thanks a lot for the tip, I tried it with my wave 1 and it kinda work, but it shows unknown most of the time, I guess that the device only sends data when there is a change on the value or sort of that. Anyway in HA the values are shown as unknown most of the time, I think that showing the latest reading would make it mostly usable. My biggest concern is that I'm used to Bq/m3 readings instead of pci/L, but I guess that some magic in the lambda part would make the deal. In my wave 2 (the one with battery indicator) the structure and the uuid are not the same and it doesn't work, I could paste my log output if it can help. |
I am trying to get my airthings wave gen 2 to work with ESPHOME. I tried with the airthingsplus code and the device is detected but then nothing more happens. Sensors are created but always "unknown".
Now got
|
I'll add another req for wave gen 1 support. Wave pro is expensive for radon only needs and mini is a simple device. Why support pro and mini but not the original device? |
I think that many of us have bought the cheaper Wave, just to be able to measure the radon levels. Would be very nice to be able to pull data from it, and have support via ESPHome :-) And unfortunately my programming skills are not good enough to make pull request and do it myself. |
I also want to support the idea of ESPHome to support the Airthings Wave (not plus). That would be nice. |
Same for Airthings Wave (not plus) v2. |
Maybe possible to re-use code from this HA custom component. |
I actually did my own custom component based on the esphome wave plus code (copy/pasted the code) and changed the uuid's to this
And then just ignore the things that the non-plus version do not support like CO2 level. |
Are you able/willing to provide a little more detail about how you did this for those of us that are just learning some of the nuances of home automation? Thanks for you contribution and time. Sorry for the idiot level question. |
This makes me think it would be simple for someone, who knows what they are doing, to fix the official ESPHome integration with an additional Wave non-plus type. |
In addition, Airthings has provided Python code for the Wave here |
So I do not have any development environment and wanted to use the easyness of ESPHome addon in HA to compile and deploy OTA. I copied the emitted code from having aithings_wave_plus specified in the yaml-file. It was placed here
I copied that folder and renamed it to some name, e.g. aithings_wave_plus_xx:
Make sure to also rename all names of files from airthings_wave_plus to airthings_wave_plus_xx. This includes namespace and TAG Then I replaced the UUIDs as specified in the .h file with the ones I mentioned. When this is done you should be able to change your yaml-file to include the reference to your own new custom component:
|
Was someone able to get this to work? |
Not me. I looked in the docs and there is still no plain Wave option, just there Wave Plus and Mini ones. I've been curious why the issue was closed when it wasn't actually resolved, especially since it seems too be an easy fix for someone who knows what they are doing. |
I tried the alternative offered but was unable to get it to work. Did anyone have any luck with the custom component? |
I agree. Fair enough that it was tagged with 'alternative-offered', but it is not resolved and I think the alternative is quite a laborious one. |
Well, I tried the alternative and I was not able to get it to work. I will make another attempt this week and will post my work here. Just curious if someone got the alternative working |
Describe the problem you have/What new integration you would like
Add support for the simple Wave device, gen 1.
Please describe your use case for this integration and alternatives you've tried:
This is another Radon measuring device, much simpler and cheaper. Only measures temperature, humidity, instantaneous radon decay, long term radon decay.
Additional context
100% Working implementation with ESP32:
BLEUUID: https://github.com/tiagofreire-pt/AirthingsMQTT/blob/master/AirthingsMQTTBridge.ino#L84
References: https://github.com/tiagofreire-pt/AirthingsMQTT/blob/master/AirthingsMQTTBridge.ino#L114
ESPHome:
Logs
Config:
The text was updated successfully, but these errors were encountered: