Closed eisenhowerj closed 4 years ago
Do you have a 2nd generation Wave? If so, then have a look at this issue https://github.com/Airthings/wave-reader/issues/6
Well damn, thats what it was (swapping the UUID). I did notice at one point something in the bluetooth saying that it was an Airthings Wave+ and I did try the waveplus-reader.
In the other thread you mentioned there is currently no support for Airthings Wave 2nd gen...should I return it and get an Airthings Wave 1st gen?
By "no support" I meant that we do not have a dedicated script to read values from Wave2, but you should be able to get the waveplus-reader script to work with your Wave2 by applying the changes discussed in issue #6. So no need to get a 1st gen Wave if you want to keep your 2nd gen 🙂
Ah ok, thanks for the reply
Hello, I bought the Airthings Wave specifically because of this project. Anyway, my unit seems to have a different set of UUIDs than the python script is looking for.
Error:
At first I thought something was wrong with UUID_DATETIME but after singling out each wave.read, none of them work. After picking around and trying to do my own bluetooth debugging, I think the UUIDs have changed.
I know I'm "talking" to the right device:
Let me know if other details are required. I simply turned on device, paired with phone (while I'm testing, bluetooth is turned off on phone) and it went through a firmware update then rebooted.